What you can do with a recorded session.
Capacitor records every coding-agent session as an immutable stream. Continue it after a crash, hand it to another agent, review the PR it produced, score the run, or ask what it cost — from the dashboard, the CLI, or inside the agent.
Share the session, then work together.
Multi-player is not another status update. It is a teammate opening the same agent session, the same spec in progress, or the same hosted agent and moving the work forward.
Switch coding agents without starting over.
One coding agent gets stuck. The next one reads the recap, sees what was tried, and continues from there — not from turn one.
Review PRs with the reasoning, not just the diff.
Your agent already reads the code. Now it can read what your teammate tried before they wrote it.
Stop teaching agents the same repo rules twice.
Capacitor scores sessions against your rubric and turns durable lessons into repo guidance loaded before the next agent starts.
Launch a coding agent from any browser.
A daemon on your machine spawns your coding agent in an isolated worktree. You start the work from the dashboard — phone, laptop, anywhere — and a teammate can join the same prompt.
Ask your agent: have we worked on this before?
Capacitor gives the agent five MCP tools — search past sessions, summarise one, walk it turn by turn, drill into the exact turn — so prior decisions show up in this conversation instead of getting re-litigated.
Don’t let one agent grade its own homework.
The agent that wrote the code has the same blind spots when it reviews the code. A review flow hands your spec or diff to a separate reviewer — and loops until the findings are gone.
What did your agents cost last month?
Token spend scatters across providers, repos, and developers. Ask in plain English — the analytics agent answers with a number you can audit, not a guess.
Start with a session you already have.
Create a workspace in the browser. Import your history when you install the CLI — searchable in minutes, not an empty tool.
Fix flaky auth-token refresh test
Tried mocking the clock first — abandoned after the race persisted. Root cause: token cache TTL rounding. Patched in auth/cache.ts, added regression test. Two approaches rejected, one shipped.