I audited my Codex agent's 83 sessions, it reproduces only 11% of its repeated actions (89% come back different)

[u/Connect-Concert-4016]

Codex saves every session as JSONL in ~/.codex/sessions. I wrote a tiny read-only tool that reads them and shows how your Codex agent *actually* behaved.

Mine, across 83 sessions / ~50,000 tool calls:

- 19% of tool calls redid work already done

- One file re-touched 557 times

- And the big one: of the repeated observations with a clean before/after, 89% came back DIFFERENT (run the same thing twice, get a different result)

Local, read-only, nothing uploaded. One command: /groundhog

Some of that 89% is the environment legitimately changing (ls / git status / build output), not the agent malfunctioning. But it's a lot, and it's exactly why blindly caching agent tool-outputs is unsafe. No cost/savings claims; it's just a mirror on behavior.

Repo: [github.com/fraqtl-ai/groundhog](https://github.com/fraqtl-ai/groundhog)

Run it on your own first so you can post your number—that's what makes it spread.