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.
The next agent starts at turn one again.
codex › ran out of room in the context windowcodex › /new
You switch to Claude Code. It has none of the prior reasoning.
Here’s the failing test again. Please try another fix for the race in flush().
I’ll start by checking whether the lock-free swap is losing writes under contention.
Without the session, switching tools means repeating old work.
The handoff keeps the failed hypotheses failed.
Claude Code reads the Codex recap. The four hypotheses Codex already ruled out stay ruled out.
Continue from the Codex session. Keep the same failing test open.
Codex ruled out the lock-free swap, the channel rewrite, the timer reset, and the retry loop. I’ll try the staged-commit approach next.
With the session, changing agents does not erase the investigation.
Every session is tagged with its vendor and serialized to the same event stream. The next agent starts a new session, pulls the prior recap through the same MCP tool, and continues from there — regardless of who wrote the original. See Recap and Session recall.
Bring your agents into one stream.
Capacitor is vendor-neutral by design. Start free and we’ll hook up the agents your team already runs.
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.