Everything on the table,
everything under control

Connect any Model Context Protocol server — spawned locally or reached over HTTP, with authorization handled in-protocol. Its tools arrive as capabilities your agent can call.

• stdio & HTTP transports
• OAuth handled for you

The inverse of MCP: bring a whole coding agent — Claude Code, Gemini CLI — and KeepTalking drives it as the client. The peers you trust can put work to it without it ever leaving your machine.

• Agent Client Protocol
• Advisory containment · macOS

Package an instruction, a script, and the files it needs into one capability. Skills run inside a sandbox with a declared filesystem and network boundary — and nothing outside it.

• Sandboxed execution
• Declared inputs & outputs

The things only the device in front of you can do — run a Shortcut, read a calendar, open a link, ask you for a file. Small, scoped, and callable by a peer you have granted.

• Shortcuts · Calendar · Files
• Per-call scope, blocking prompts

Your contexts are the knowledge base. Threads are grouped and indexed as they happen, so an agent can go find what was decided instead of being told again.

• Auto-threaded contexts
• On-device embeddings

OpenRouter, OpenAI, or any OpenAI-compatible endpoint. Your key, your account, your bill — we never sit between you and the model you chose.

• OpenAI-compatible
• Configured per node

Point a node at a machine on your own network, or at the one under your desk. The conversation and everything it touches stays inside your perimeter.

• No egress required
• Same features either way

The active provider is a setting, not an install. Change it between turns, run different models on different devices, and keep the history you already have.

• Change without migrating
• Per-turn reasoning controls

Nodes negotiate a path with ICE and then talk straight to each other. When a direct route exists — and it usually does — nothing in the middle is in a position to read the traffic.

• ICE over libjuice + SwiftNIO
• Relayed only as a fallback

Action calls and their parameters are sealed to the caller and the callee. A capability invocation is legible to the two nodes involved and to no one else.

• Per-call sealed envelopes
• Keys never leave the device

Peers still have to find each other, and that introduction happens through a signalling host. It is the one central piece — so it is yours to run, on your own network, for your own fleet.

• Self-hosted signalling & relay
• Provisioned per deployment

A node is a keypair generated on the device. Nothing to sign up for, and no directory you have to appear in before two people can work together.

• Created on first launch
• Trust is peer to peer

Optional, and only about your own devices: sign in with a passkey and your Mac, iPhone, and iPad recognise each other as yours without you introducing them one by one.

• WebAuthn passkey · no password
• Self-hostable key-value host

Permission is granted per peer and per action, by you, in the moment. No inherited role quietly hands someone a capability you never considered.

• Per-action, per-peer
• Revocable at any time

Contexts, threads, embeddings, and grants live in a local database on hardware you own. Backups are yours to take, and deletions are real.

• Local database per node
• Semantic threads & retrieval