FAQ

Do I need C3Sync to use C3 Mobile?

No. You need the c3sync CLI on the hub machine — it provisions and runs the hub — but you never have to enroll a sync device or enable a project. The two products share the hub in isolated accounts and are useful together: Sync moves your sessions between machines, Mobile steers them from your pocket.

C3 Desktop can guide the hub setup on Linux, but it still orchestrates the same separately installed c3sync CLI.

Do I need Herdr?

Yes, on every controlled host. Herdr is the terminal workspace manager your agents run inside; the bridge adapts it rather than reimplementing terminal management. Herdr 0.7.5+ is installed separately (it's a separate project with its own AGPL/commercial licensing) and is never bundled with C3.

Which coding agents work?

Any CLI agent that runs in a terminal — Claude Code, Codex, and friends. C3 Mobile operates the terminal and workspace layer, so it has no agent-specific integration to go stale. Agent-aware niceties (the attention queue, session status) come from Herdr's view of the pane.

Does anything go through C3's servers?

There are no C3 servers. Phone and bridges connect only to your hub; push notifications go through Apple/Google but carry no content. If your hub is down, nothing can connect — that's the design.

Can the hub operator read my prompts or terminals?

No — payloads are end-to-end encrypted between phone and bridge; the hub routes ciphertext and sees only subjects, sizes, and timing. The honest caveats (endpoint compromise, traffic analysis, the beta's pending independent review) are in the security model.

Can I use multiple phones? Multiple hubs?

Multiple phones: yes — enroll each and pair it with the bridges it should control; every pair is independent. Multiple hubs: an app install enrolls with one hub at a time (Settings → Remove hub switches).

Is C3 Desktop only a setup tool?

No. It guides hub, bridge, phone, device, and service setup, then enrolls as a full control client with Signal, a session cockpit, prompt controls, and local or remote terminal tabs. See the C3 Desktop docs.

What happens when my phone loses signal?

Nothing dangerous. The app refuses to send while disconnected, and in-flight commands expire in seconds rather than executing late. Agents keep running on your machines; notifications resume reaching you when connectivity returns; reopening the app re-syncs state from the bridges.

Why isn't the app in Expo Go / why a native build?

Certificate pinning happens in a native module on both platforms. Expo Go can't load it, so it's intentionally unsupported.

Where do I report issues?

The C3 repositories on GitHub — the footer links to the project. c3bridge doctor output (it's redacted by design) and the app's Settings screen state are the most useful things to include.