BriefSign in

Support

Diagnose the connection before sharing the code.

Brief can report its target, version, freshness, privacy mode, and cloud status without exposing a connector secret or source archive.

Reviewed July 27, 2026Current product controls

Diagnose locally

  1. Ask the agent to call brief.install_status and confirm the repo root, branch, connector version, server freshness, privacy mode, and cloud status.
  2. If the server is stale, call brief.restart_connectorand let the host agent relaunch it.
  3. Rescan with brief.scan_repo, then confirm the active repo in the Code map page.
  4. Check free service readiness for hosted auth, data, and package status.

Contact support

Use the private support form and include 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 local connector and Founding Team Access are available now. Support is currently best effort without a contractual response-time SLA. Security reports belong on the private security channel, not in a general support message.