How we can help
How we handle security
-
End-to-end encryption
Every time the phone and PC connect, they derive a new session key from ephemeral X25519 keys. The relay server only passes ciphertext along; it doesn't store or log messages. Adding a new device takes both the one-time secret in the QR code and matching 6-digit numbers on both screens.
-
Key storage
API keys are encrypted in OS-backed storage: Windows DPAPI, macOS Keychain, or Linux Secret Service. Codex, Claude Code, and Pi settings files get a helper command instead of the key, and OAuth tokens stay with each CLI.
-
No open ports, only verified updates
Your PC opens no ports; it only makes outbound connections to the relay server. Automatic updates install only files that pass Ed25519 signature and SHA-512 checks.
Frequently asked questions
Can we run the relay server ourselves?
Yes. Both the phone relay server and the update server can run on your own servers. Point the desktop app at your update server with the AGENT_SWITCHBOARD_UPDATE_URL environment variable. Get in touch and we'll walk you through the setup.
Can the relay server operator see chat content?
No. The relay server doesn't have the session key, so all it can do is pass ciphertext along. It doesn't store or keep messages either.
Where are API keys stored?
They're encrypted with each PC's OS secure storage. Keys never go into Codex, Claude Code, or Pi settings files; when a tool runs, a helper fetches the key and hands it over.
Can we use an in-house AI gateway?
If your gateway speaks a protocol the tool supports (OpenAI Responses, Anthropic Messages, or OpenAI-compatible Chat), you can add it as a connection. Each project can use a different gateway and model.
How is it licensed?
Under the MIT License.