Start here
What is Mike Trace?
The investigation and evidence layer for developers and AI coding agents.
Mike Trace is an investigation and observability platform for software failures. It helps developers and AI coding agents investigate bugs using structured evidence instead of starting every debugging session from scratch.
What it is
- A durable case for every problem: one persistent record of the investigation, with its own
reference such as
MT-0009. - A shared record that humans and agents read from and write to.
- A consistent workflow: TRACK, TRACE, TARGET, TACKLE.
- A way to keep evidence separate from claims and conclusions, so the answer is backed by more than confidence.
Why it matters
Debugging time isn’t only spent finding defects. Much of it goes into reproducing failures, rebuilding context, retracing code paths, repeating approaches that already failed, and handing investigations between people and agents. Mike Trace preserves evidence and investigation state so each debugging cycle can build on the last.
The goal isn’t to make debugging disappear. It’s to stop paying for the same investigation twice.
What it is not
Mike Trace is not a coding assistant. It doesn’t replace Claude Code, Codex, Cursor, ChatGPT or any other agent you use. Those tools reason about and change your code. Mike Trace is the investigation layer they work through: it remembers what was observed, tried, ruled out and verified.
Who it’s for
- Individual developers who want their debugging sessions to build on each other.
- Developers working with several AI agents who need clean handoffs between them.
- Teams and organizations that want a reviewable record of how production issues were investigated and resolved.
Ready to try it? Continue to Getting started.