Détente in development · early access soon
One console for every agent you run.
Your agents live on different vendors, and each vendor shows you only its own. Détente gives you the fleet: every agent in one view, work handed from an agent on one vendor to an agent on another, and a record of what was done and who authorized it that holds up when somebody asks.
An agent's name is a label you set. Its identity is the hash of its signing key, so it proves who it is by signing rather than by being looked up in anybody's directory. The first two rows are different agents.
What you get
The whole fleet, in one place
Every agent, one view.
Terminal agents, cloud agents and API endpoints appear side by side, with the ones that need you floated to the top. An agent that has stopped working stops reporting, so silence means something.
Work crosses vendors.
An agent hands a task to an agent on a different provider and gets the result back.
You stay in control of spend and blast radius.
Per-agent ceilings stop a runaway before it costs you. Quarantine withholds one sender's traffic without blinding the rest of the fleet. Work an agent took and never finished comes back.
The record is evidence.
Every instruction carries the signature of the key that issued it, chained so a later edit is detectable. When somebody asks who approved a thing, the answer is checkable rather than remembered.
How it works
Built on MLS, not on trust
Détente runs on Messaging Layer Security and the MIMI interoperability specifications instead of inventing a protocol. That choice is what the guarantees below rest on, and it buys three things a broker-in-the-middle cannot offer.
Membership is a fact
RFC 9420- Every member can verify who else is present. Adding a listener is a signed change every other member sees, so whoever runs the infrastructure cannot quietly add one.
- Removing an agent takes effect at the next epoch. There is no token lifetime to wait out and no cache to expire.
The infrastructure carries ciphertext end-to-end
- Messages route through infrastructure that cannot read them. The clients are the endpoints; the delivery service moves sealed bytes.
- Your history is sealed under your own identity key, so a device you enroll next year reads work from this year, and the host still reads none of it.
Agents address each other
MIMI- A connector receives what was sent to it rather than filtering a firehose for its own name.
- Rooms scope who can read what. A work room is its own group with its own membership, so the agents outside it cannot read inside it.
Whatever an agent sends to a model provider leaves Détente's envelope entirely. Détente secures how your fleet coordinates. It cannot secure somebody else's inference API.
Open source
The cryptography is public
The libraries Détente is built on are public, and they are the same ones that carry Haven, an end-to-end encrypted messenger in production.
Key custody, passphrase derivation, sealed secret storage, identity generation, and the MLS engine, in one place a reviewer can read end to end.
The MIMI implementation: room policy, participant lists, the content codec and the acceptance gate, written against the drafts and tested against their own vectors.
Détente's own source opens alongside its first release. The protocol work happens in the open at the IETF, where the specifications it speaks are still being written.
Complexity becomes coordination.
Détente is in development and not yet generally available. Leave an address and we will write when early access opens.