Your Code Deserves Better Security
Claude Code Channels routes your sessions through Telegram and Discord. Dispatch sends them through Anthropic's servers. Styrby encrypts end-to-end. We never see your code.
E2E Encrypted
XSalsa20-Poly1305 encryption via TweetNaCl. Per-session keys derived with HMAC-SHA512. We never see your code.
Zero Knowledge
Session content is encrypted before it leaves your machine. Styrby servers relay ciphertext, never plaintext.
No Third Parties
Your data never touches Telegram, Discord, or any third-party messaging platform. Direct relay only.
Audit Trail
Every security-relevant action is logged: logins, pairings, permission approvals, key operations.
Resilient Connection
Commands queue offline and sync when reconnected. Your laptop can sleep. Styrby remembers.
5 Agents, 1 App
Claude, Codex, Gemini, OpenCode, Aider. All from one secure mobile app. No vendor lock-in.
Feature-by-Feature Comparison
See exactly how Styrby compares to Anthropic's built-in solutions.
| Feature | Styrby | Claude CodeChannels | ClaudeDispatch |
|---|---|---|---|
| Encryption & Privacy | |||
| End-to-end encryption | |||
| Zero-knowledge architecture | |||
| Messages readable by provider | Never | Telegram/Discord can read | Anthropic can read |
| Per-session encryption keys | |||
| Key derivation (HMAC-SHA512) | |||
| Your code stays on your machine | |||
| Agent Support | |||
| Claude Code | |||
| OpenAI Codex | |||
| Google Gemini CLI | |||
| OpenCode | |||
| Aider | |||
| Switch agents mid-session | |||
| Reliability & Connectivity | |||
| Works when laptop sleeps | Queues commands | ||
| Offline command queue | |||
| Auto-reconnect with session resume | |||
| Push notifications on completion | Via Telegram/Discord | ||
| Quiet hours / Do Not Disturb | Via Telegram/Discord | ||
| Smart notification priority scoring | |||
| Cost & Budget Management | |||
| Real-time cost tracking | |||
| Cross-agent cost comparison | |||
| Budget alerts with auto-actions | |||
| Daily cost aggregation dashboard | |||
| Team cost attribution | |||
| Experience & Integration | |||
| Purpose-built mobile app | Claude app only | ||
| QR code pairing | |||
| Session history & bookmarks | |||
| Permission approval from phone | |||
| Prompt templates | |||
| Third-party dependency | None | Telegram or Discord | Claude Desktop |
| Requires account with | Styrby | Telegram/Discord + Claude | Claude |
How Styrby Encryption Works
Your code never leaves your machine unencrypted.
Key Generation
Each session generates a unique keypair using TweetNaCl.box.keyPair(). Keys are derived via HMAC-SHA512 from user + machine + session ID.
Message Encryption
Every message is encrypted with XSalsa20-Poly1305 before leaving your machine. A random nonce ensures no two ciphertexts are identical.
Relay (Zero Knowledge)
Styrby's relay server forwards ciphertext only. It cannot decrypt your messages. Only your paired devices hold the private keys.
Mobile Decryption
Your phone decrypts messages locally using the shared secret established during QR code pairing. Code is visible only on your devices.
Claude Code Channels
Your session messages are sent as plaintext through Telegram or Discord servers. These third-party platforms can read, log, and index your code. Your prompts, file paths, and agent responses traverse infrastructure you don't control.
Styrby
Messages are encrypted on your machine before transmission. Styrby's relay sees only ciphertext. No third-party messaging platforms are involved. Only your paired devices can decrypt session content.
Control Your AI Agents Without Compromising Security
E2E encrypted. Multi-agent. Purpose-built for developers.