open source · MIT
Everett
Many sessions. One mind.
One layer above your AI coding agents: Claude Code, Codex, Grok, Pi, Hermes and OMP. Everett sees every session on the machine, routes new work to the one it belongs to, and delivers it there.
What it does
Every session keeps a card
A short note of what the session is on and what is next. Routing reads the card, not the raw transcript.
Work goes to the right session
Hand Everett a request and it picks the session that request continues, then delivers it there.
Agents message agents
One agent can hand work to a parallel session, even one that is mid-task. The message lands at its next turn or tool call.
Message from anywhere
Agents in the cloud, on your laptop, or on another machine can hand each other work. Pick a conversation. The messages are made up for the demo. The path each one takes is how Everett actually delivers it.
- pick a conversation
OpenAI dots and Grok Bot connect through registered MCP inboxes on the Everett gateway, over HTTPS. Your own machines on the same account trust each other and talk through an encrypted relay. Inside one machine, routing is by Jev, with a local matcher as the fallback, and it asks instead of guessing when the choice is unclear.
Teach one. They all know.
Parallel sessions drift apart. The shared core is the part they keep in common: any session learns a fact once, and every new session starts from it. Secrets are filtered out before anything is stored.
Sees sessions from
- Claude Code
- Codex
- Grok
- Pi
- Hermes
- OMP
MCP built in
- Claude Code
- Codex
- Grok
- OMP
Everett ships a stdio MCP server, so agents get it as native tools. Humans get the same commands in the terminal.
Install
- Homebrewbrew install raitoxlol/tap/everett
- Then
A guided terminal setup.
everett onboard
Read the source
Everett is open under MIT. Named after Hugh Everett: every session branches from one origin but keeps its own history.