Documentation
Feedback and support
Send a useful problem report without sending secrets or a full browsing history.
Use “Send feedback” in the app to send an idea, problem, question or praise. The feedback form has a title, message and optional email. A title is limited to 120 characters and the message to 4,000.
Choose what to send
Diagnostics and a screenshot are optional. Review each before you include it. Diagnostics contain the app and OS versions, browser mode, agent and space counts, and bounded generic error entries. They do not include raw error text or page URLs. A screenshot can still contain personal information; leave it off for sensitive pages.
Your message is sent to the account service. A signed-in report may be associated with your account. Failed sends can remain in a local owner-only queue; the queue holds at most 20 messages. Use the retry control when the connection returns. Do not submit repeatedly to bypass a full queue.
What helps
Include the app version, browser mode, MCP client, the steps that failed, what you expected and what happened. Give a public test page or a small reproduction when possible. Remove tokens, cookies, passwords, private URLs and personal data.
CLI commands in these docs require the separate CLI, not the app’s bridge executable. The CLI is not part of the Mac download yet.
For support contact details, see Support. For a vulnerability, use responsible disclosure rather than a public issue or an ordinary screenshot.