Support
Start with the connector's own diagnosis.
Most Brief failures are target, freshness, package, auth, or cloud-sync problems. The fastest support request includes the safe diagnostic fields, not a connector secret or source archive.
Last updated July 19, 2026Diagnose locally
- Ask the agent to call
brief.install_statusand confirm the repo root, branch, connector version, server freshness, privacy mode, and cloud status. - If the server is stale, call
brief.restart_connectorand let the host agent relaunch it. - Rescan with
brief.scan_repo, then confirm the active repo in the Code map page. - Check free service readiness for hosted auth, data, and package status.
Contact support
Email support@runbrief.aiwith the coding surface, Brief version, operating system, safe install_status output, approximate time, and the failed step. Remove API keys, session cookies, raw source, and customer-sensitive logs before sending.
Current support scope
The free connector is available now. Hosted team workspaces are still being enabled in stages, and support is best effort without a contractual response-time SLA. Security reports belong on the private security channel, not in a general support message.