# Log chats that go badly for later analysis

Published: 2026-08-07T00:00:00.000Z
Canonical: https://wow.pjh.is/journal/log-chats-that-go-badly

I use [/retro](https://github.com/HartreeWorks/skill--retro) to save agent sessions for later analysis.

I use this when a session goes badly, or otherwise leaves me with a sense of "hmm, we could improve this".

The affordance is great because:

1. Fixing an issue immediately can easily derail a work session.
2. Sometimes you need several example sessions to make the pattern—and the fix—easy to see.[^1]
3. Punting with `/retro` means I know I'll get to it later, if it matters. When I review the retro inbox, I rank the list, address the most important, and delete the rest.

My `/week-review` skill includes a "check the retro pile" step.

[^1]: A recent example: Codex with GPT-5.6 Sol kept doing a wildly disproportionate amount of testing. A couple of /retro sessions made it much easier to identify and resolve the issue.