Send feedback
Tell us when 0bridge gets something wrong, or what you'd like it to do: from the dashboard, the terminal, or the AI tool you're working in. Reports go to the 0bridge team.
Last updated
From the dashboard#
Feedback at the top right (on a phone, in the account menu) opens a short form: a problem, an idea or something else, and your message. Include page and browser info is on by default and adds the page you're on (without its query), your browser's user agent and the dashboard's version.
From the terminal#
0b feedback "0b sync stops after the update"Without a message, 0b feedback opens your $EDITOR, or asks for one. It shows the whole report and asks before sending.
--kind problem|idea|other(problem by default).--include-logsadds the last lines of 0b's own logs on this machine (background sync, the session worker, the clipboard and agent services), with your vault's values and key-shaped text masked, and shows them to you before anything is sent.--yessends without asking. It's for an agent after you've read the report and said yes, not for skipping the look. Run by an agent without--yes(no terminal to ask in), it prints the report and sends nothing, so the agent can show it to you first.
From your AI tools#
Connected agents and chat apps have bridge__feedback. When 0bridge itself fails in a way that looks like a bug (a 0b command, a bridge__ tool, a connection), they can offer to send a report: what you were doing, the commands, the error, what you expected, and the versions. They're told to show it to you and send it only after you say yes, and to leave out secret values, tokens, file contents and personal details.
Every app and token can send one, including a read-only app token. Each account can send 10 reports an hour, from all three places together.
What a report contains#
- What you wrote: the kind, a one-line summary and the details; an agent's report can add steps, what it expected and what happened, the commands and the error messages.
- Versions you include: the CLI, the AI tool, the OS; from the dashboard, the page, browser and version if you leave that on; from
--include-logs, the log lines you were shown. - Where it came from (the dashboard, the CLI or an AI tool, with the device's or app's name), your account, and the time.
Text shaped like keys and tokens is masked again on the server before the report is stored, and the team gets an email with it. Reports are kept with your account and deleted with it. See Security.
Need an answer, or something private? Use the contact form.