Your coding agent
Reasons, writes and changes code
Explores the codebase, proposes fixes, runs commands and ships changes. You keep using the agents you already like.
For AI coding agents
Claude Code, Codex, Cursor and other agents are great at reading and writing code. Mike Trace gives them somewhere durable to investigate: a shared case file that survives sessions, tools and handoffs, so switching agents doesn't mean starting over.
Positioning
Your coding agent
Explores the codebase, proposes fixes, runs commands and ships changes. You keep using the agents you already like.
Mike Trace
Preserves what was observed, tried, ruled out and verified, so each connected agent and every teammate builds on the same record.
Investigation continuity
When work moves between connected coding agents, Mike Trace is designed to keep the investigation with the case, so the next investigator doesn't have to begin from zero. Only one agent actively drives an investigation at a time, and each new one starts from a clear handoff.
Why it matters
Without a shared record, a new agent re-reads the code, re-runs the reproduction and re-tries approaches that already failed. With one, it starts from what is already known and spends its effort on what is still open.
Continuity applies to agents connected to Mike Trace over MCP, such as the clients listed below.
Supported clients
Mike Trace connects over the Model Context Protocol (MCP), the open standard many agents already support.
Boundaries
Agents connect with scoped, expiring access that you approve. They get what they need to investigate and nothing more.