SwarmVault
Your AI agents don't synchronise. SwarmVault does.
One shared memory for Claude Code, Codex, and any other CLI agent.
Real software engineering: requirements → design → tickets → review.
14 skills, the best of everything combined.
The right model on the right task.
Zero dependencies. Plain markdown. MIT.
What you get
A memory that survives sessions. Say "continue project X" in a fresh session, on any platform. It picks up where the last agent stopped. Progress is saved as the work happens, so even a crashed session resumes.
Parallel agents, no collisions. A ticket belongs to whoever claims it first; the filesystem referees. Dead sessions lose their tickets automatically.
Software engineering, not vibes.
- A requirements interview that ends in a real, testable spec
- Design docs with the decisions written down
- Tickets in dependency order, tests included
- Every milestone audited by a strong model, against the spec
The right model on the right task. Design work goes to strong models with usage headroom. Boilerplate goes to cheap ones. You never pick models or worker counts; the optional orchestrator matches fit and budget for you.
The plan before the burn. Before dispatch, a terminal board shows every ticket, model, reasoning effort, routing reason, ETA, token/window estimate, dependency, and expected usage impact. The same table stays live, prints again at finish/block/checkpoint boundaries, and expands any ticket on demand.
Writing that sounds like you. One voice profile in the vault, used by every agent: README, posts, UI text, release notes. Any language, written natively, never translated.
It outlives your usage limit. Near quota, it asks. Say yes and it resumes by itself when the limit resets.
Private by default. No network calls. No telemetry. Files on your disk.