On 16 November I published an article about blocking the obvious ways a key reaches an AI coding agent. The first comment asked whether I had thought about putting blocked attempts on the conversation's timeline, with the agent's task and without the secret.

agentwhy already does that. The article gave it one sentence. So this is the start of a series: each week, one part of agentwhy, looked at closely. Part 1 is the view that answers that comment: what your AI and its helpers did, step by step.

All the screenshots are from the demo, a made-up project.

One conversation

You asked Claude Code: "Find out why the AI chat stopped answering." It worked for six minutes. The report's first screen answers in three lines.

The report's first screen in the agentwhy demo: it read 1 private file you let it read (business-plan.md, Track), it tried to open 2 private files and was stopped in time (customers.csv, .env), and it brought in 1 helper that read nothing private.
The first screen of the report: one file it was allowed to read, two it tried to open and was stopped, one helper.

It read one private file you let it read, business-plan.md, which you set to Track. It tried to open two private files, customers.csv and .env, and a rule stopped both. It brought in one helper, and the helper read nothing private. Nothing to fix.

Who asked whom for what

How it went opens on a diagram. You asked your AI. Your AI read business-plan.md and was stopped at customers.csv. It also gave work to Helper 1, with the task "Find where the chat gets its AI key", and the helper was stopped at .env.

The How it went diagram: You, Your AI, Helper 1 with the task Find where the chat gets its AI key, and three files: business-plan.md read, customers.csv and .env stopped in time.
Orange is a read, dashed green is a stop, grey is "gave work to". The helper's task is written on its box.

The helper's task matters most to me. In my own incident in September, the rule in AGENTS.md never reached the helper. The helper only had its task, and the task asked for the secret. Here you can see the task that was handed down, word for word.

Step by step

The Step by step tab is the same conversation as a list, in the order it happened. Each stretch starts with what your AI wrote, then one row per step: what it read, what it ran, what it changed. Your AI's model sits above the list, as Claude Code recorded it: claude-opus-5-5.

Step by step in the demo, with the model claude-opus-5-5 above the list: reads of assistant.ts, widget.tsx and package.json, then an MCP tool search_issues from the sentry server, whose files the record can't show.
Every step in order. The MCP step says plainly what the record can't show.

Two rows are worth a closer look.

The MCP tool. Your AI called search_issues on a Sentry MCP server. That server works outside the record, so agentwhy can't see which files it opened, and the row says so. It quotes the tool's own description, so you know what it was for.

The stopped attempt. "Tried to open customers.csv. A rule in your settings stopped it." In my setup a read refused by a deny rule fired no hook, so nothing in your hooks or logs would show it. It is still in the saved conversation, and that is where agentwhy reads it from.

Step by step continued: business-plan.md read and tracked, customers.csv stopped by a rule, then work given to Helper 1, its job quoted, its model changing from claude-haiku-5-5 to claude-sonnet-5-5.
A tracked read, a stopped attempt, and the handoff to Helper 1 with its task and model.

Then the handoff: "Gave work to Helper 1." The helper's row carries its job, in quotes, and its model. This one started on claude-haiku-5-5 and ended on claude-sonnet-5-5, so both are shown, with "The model changed while it worked."

Open the helper and you get its own steps, the same way.

Helper 1 opened in Step by step: it read assistant.ts, then tried to open .env and a rule in your settings stopped it.
Helper 1's own steps: it read assistant.ts, then tried .env and was stopped.

It read assistant.ts, then tried .env. A rule stopped it. So the helper did go for the key, as its task asked, and the block held. Without this view you would only know that .env was not read. With it you know who tried, and why.

Two switches help on a long conversation: Every step or Only private, to hide the rows that touched nothing private. And every row with a private file has What happened, which opens that file's own story.

Where it comes from

Claude Code saves every conversation as a file on your computer, and each helper's work in a file of its own. agentwhy reads those files, matches each helper's file to the task that started it, and puts them back in order. It runs on your computer, nothing leaves it, and any secret value is replaced before the page is built. It also works on conversations from before you installed it.

What it doesn't show

  • What the AI was thinking. Only what it wrote down and did. The page says so at the bottom.
  • The order between helpers that worked at the same time.
  • Which files an MCP tool opened.
  • A rule ID, or a label that tells probing from one accidental glob. Five tries at the same file show as five steps, and you read the pattern yourself.
  • The model, outside Claude Code. Codex and Copilot conversations get the steps, but Codex writes down less, and some of its steps leave no trace. The report says when it could not check fully.

Try it

npx @agentwhy/cli 

Run it in your project folder. It opens a page with your conversations from the last 7 days. Open one, then How it went, then Step by step. Or click through the demo first.

Next week, part 2: refusing the obvious reads, and which ones still get past.

What do you check first when you open a conversation your agent ran without you?