POSTMORTEM
Post-mortems
Every post-mortem here follows the same four parts: what broke, why the agent did it, how it was fixed and what guard now stops a repeat. No blame on the model. The cause is almost always a missing instruction, a missing check or two agents sharing something they should not.
- POSTMORTEMWhy Claude Code Got Slow: A Post-Mortem of Context, Tools, and RetriesExplains why Claude Code can feel slow when context, tool output, cache resets, or transient-error retries expand the work, with documented recovery commands.
- POSTMORTEMWhy Claude Code Stopped Working: A Post-Mortem of Permissions, MCP, and Stale StateClaude Code not working usually points to merged settings, permission precedence, MCP approval or paths, authentication, limits, context, or stale session state.
- POSTMORTEMWhy Multi-Agent LLM Systems Fail: Lost State, Broken Handoffs, and False CompletionA MAST analysis of 1642 annotated traces from 7 frameworks explains why multi-agent LLM systems fail across system design, inter-agent misalignment, and task verification.
The first guides in this track are being written and checked against the tools' own documentation.