Watch a real session in two minutes.
A Team, Not a Solo Agent
Summon specialists by name — reviewer, tester, architect, writer. Assign each to Claude, Codex, or Gemini based on what they do best. They coordinate through messages and shared project knowledge. Watch any agent live, jump in to steer, or let them finish. Run crews across machines with files and messages flowing between hosts.
$ recalletta crew summon rivet --client codex Review the auth moduleEvery Persona Carries Its History
Each specialist has its own session archive. Summon someone weeks later — on a different provider, a different machine — and it picks up where it left off. The persona is portable. The memory follows.
Searchable History, Curated Knowledge
Search across all sessions and all agents. Write project rules into the Knowledge Base and they appear at the start of every future session. Entries are versioned — the current truth wins.
How It Works
- Install the CLI and enable hooks.
- Work normally in your editor and terminal.
- Recalletta saves each session and brings back the right context next time.
Get Started
Install the CLI. Run init. That’s it.
FAQ
Does it upload my source code?
Recalletta does not read, index, or upload your repository.
It uploads session transcripts — your conversation with the AI.
Any code in the conversation is part of the transcript.
Local code search stays on your machine.
You control capture with .norecalletta and .yesrecalletta.
What AI clients are supported?
Claude Code with hooks, Gemini with hooks, and Codex with background monitor. Hooks give automatic context at session start.
Where is my data stored?
Session transcripts and Knowledge Base entries are stored in the Recalletta API. Local artifacts like crew history, reports, and config stay on your machine.
Can I use it on multiple machines?
Yes. The crew bridge relays messages between hosts over HTTPS or encrypted P2P.