FAQ

Questions, answered.

The questions we hear most. Each one points back at the architecture choice that drove the answer. If the answer you need isn't here, open an issue.

Does OpenBurnBar send my data anywhere?

By default, no. Local usage tracking runs entirely on your Mac and writes to a local SQLite database. No telemetry, no analytics, no crash reports leave the device unless you explicitly enable an opt-in feature.

The opt-in features are: Firebase sync (metadata only by default), iCloud session-log mirroring (separate from Firebase, uses your Apple ID), Sentry crash diagnostics (off by default), and hosted quota sync (paid). Each one is a separate toggle, each one is described in the Privacy & Trust page.

Do I need an account?

No account is needed for the core product. OpenBurnBar reads logs your agents already drop on disk and works fully offline.

You'll only sign in (Apple or Google, via Firebase Auth) if you want optional cloud sync, multi-device chat resume, or the paid Hosted Quota Sync subscription.

Does OpenBurnBar read my API keys?

Not by default. Local usage tracking reads usage logs, not credentials. If you choose to enable provider routing or quota polling, you may provide an API key for that specific provider — stored in the macOS Keychain with device-local accessibility.

If you enable Hosted Quota Sync, credential material you explicitly hand over is stored in Google Cloud Secret Manager; Firestore only holds a redacted label.

How accurate are the costs?

Every provider row is tagged with one of three confidence labels:

Exact — the vendor's own API or local logs return token counts and we apply current public pricing.

Estimated — token counts come from an on-disk approximation (e.g. Copilot uses an 85/15 input/output heuristic).

Unavailable — the vendor doesn't expose data. We mark it instead of pretending.

Only OpenRouter returns dollar costs directly. For everyone else we compute from a pricing table — accurate for trends, not for tax audits.

Which providers are exact vs estimated?

Exact today: Claude Code, Codex, Cursor, Factory, MiniMax, Z.ai, Warp, Kimi, OpenRouter, Ollama (local), Aider.

Estimated: OpenAI (cost computed), Anthropic Console (cost computed, daily lag), GitHub Copilot (token volume heuristic).

Detection-only (no usage data exposed by vendor): Gemini CLI, Cline, Roo Code, Kilo Code, Augment, Windsurf, Goose, OpenClaw.

The full matrix is on the Providers page.

What is Hosted Quota Sync?

Hosted Quota Sync is the paid tier. It adds four capabilities to the free local product:

1. Hosted Codex quota refresh from any signed-in device, with OpenBurnBar running the runner. Rate-limited to 30/day and 300/month per account.

2. Conversation backup and resume — chat titles, previews, and message bodies, encrypted in transit, restored across iPhone, iPad, and Mac.

3. Full session-log sync — complete agent runs mirrored to cloud and searchable across devices.

4. Hermes Remote Relay — reach the Mac's local Hermes from anywhere over a verified WebSocket, with App Check attestation and Apple JWS end-to-end.

Product id com.openburnbar.hostedQuotaSync.monthly. Intended price $4.99/month via the App Store. Apple handles billing.

Why is Claude Code self-hosted only?

Two reasons. First, Claude Code's real data sources live in your local filesystem — the statusline hook in ~/.claude/settings.json and the per-session JSONL files in ~/.claude/projects/. A cloud function has no lawful way to read those without an agent running on your Mac.

Second, Anthropic's current Claude Code policy disallows third-party developers from offering Claude.ai login or routing Free, Pro, or Max credentials on behalf of users. We agree with that boundary. Claude Code always stays on your machine.

Can I delete my data?

Yes — at any time, from several angles.

Local: delete the app and its support files at ~/Library/Application Support/OpenBurnBar/.

Cloud: sign out and choose Delete my data in Settings → Account.

Hosted credentials: remove the provider account from OpenBurnBar.

iCloud mirror: delete files from the iCloud.com.openburnbar.app container in your iCloud Drive.

What happens offline?

The whole product works offline. Dashboard, menu bar, log parsing, session viewing, settings, Hermes (with local backends), CLI, editor extension, controller workbench — none of them require a network.

Cloud sync simply pauses and resumes when you come back online. Disabling sync entirely does not affect local data.

Is this for teams or solo developers?

Both — but the product is sharpest for solo developers and small teams who run multiple agents in parallel and are tired of finding out about the bill on the first of the month.

For solo: zero accounts, all local, on your Mac. For small teams: optional Firebase sync lets each developer see their own burn while a shared workspace surface stays consistent. There is no admin console or seat-billing today — that's roadmap, not present.

How does the Cursor / VS Code extension work?

The extension is an activity-bar panel that talks to OpenBurnBar's local daemon over the same UNIX socket the menu bar app uses. It shows the burn for your active workspace, the quota state for your active agent, and exposes the routed-provider gateway when you have it on.

It's source-only today — no public marketplace listing, no signed VSIX. Build from extensions/openburnbar and load unpacked. Marketplace publication is on the roadmap.