One chat.
Many voices.
Every voice responds to you, and to each other.
Everything you need to orchestrate AI
Designed for engineers, researchers, and curious minds who want more than one perspective.
Multiple voices, one conversation
Add any combination of Claude, GPT-4, Gemini, or local CLI tools. Every voice sees the full history.
Compositions
Save a named set of voices as a composition, then launch new sessions from it instantly.
Reusable configuration
Save tone presets and system prompt templates. Attach them to any voice in any composition — update once, applies to every new session that uses it.
Broadcast & conductor modes
Broadcast to all voices at once, or direct your message to a specific voice.
File system tools
API voices get host-brokered file tools — read, write, list — with optional sandboxing to the session working directory. CLI voices run as autonomous agents in the same directory.
Full text search
Search every message across all sessions instantly. Global search finds anything; per-session Cmd+F highlights matches inline.
MCP Server
Use Polyphon as a tool inside your agent workflows. Claude Code, Cursor, Codex CLI, and GitHub Copilot can list compositions, create sessions, and broadcast questions to your full ensemble — synchronously, over stdio.
API server & poly CLI
Enable the built-in TCP API server to control Polyphon programmatically. The poly CLI lets you create sessions, run prompts, stream responses, and export transcripts — all from the terminal or a CI pipeline.
Local-first, no telemetry
Conversations and API keys stay on your machine. No account, no cloud sync.
Works with the models you already use
API keys, CLI tools, and custom endpoints — all treated equally inside a session.
- Anthropic Claude
- OpenAI GPT
- Google Gemini
- Claude Code
- Codex
- GitHub Copilot
- Ollama
- LM Studio
- Any OpenAI-compatible
Designed with you in mind
The decisions we made before writing the first line of code.
- Local-first
- No telemetry
- Bring your own key
- Provider-agnostic
- Multi-voice
- Scriptable
- No lock-in
- Project-aware
- Sandboxed tools
- Encrypted at rest
The source is open.
Check it yourself.
If we say there's no telemetry, you should be able to verify that. Local-first software that touches your real work should be inspectable — not just trusted.
- Encrypted at rest AES-256 whole-database encryption via SQLCipher. Every byte on disk is ciphertext — not just selected fields. VERIFIED
-
Deny-by-default CSP
Renderer makes zero network calls. No
unsafe-inlineorunsafe-evalin production. VERIFIED - Keys isolated to main process API keys resolve in main only — never sent over IPC in plaintext. Renderer sees a masked status. VERIFIED
- Zero telemetry No usage data, no analytics, no crash reports. Polyphon is silent on the network. VERIFIED
-
Sanitized log output
All diagnostic output is sanitized before writing to disk. API keys and sensitive values are replaced with
[REDACTED]. VERIFIED - Password key wrapping Optionally wrap the encryption key with AES-256-GCM + scrypt (N=65536). Your key, your password. VERIFIED
Built like it matters.
Your data is encrypted at rest, your keys never leave the process that holds them, and nothing phones home. These aren't promises — they're verifiable properties of the code.
Ready to conduct your ensemble?
Install Polyphon, add your voices, and start your first session in minutes.
macOS
Apple Silicon Signed & Notarized
poly CLI
npm @polyphon-ai/poly