Show HN: Replay an AI Coding Session and Inspect Its Requests
Experiments How Agent Harnesses Work, With a Replay of a Real Session How do Claude Code, Codex, and other tools interact with the model? We can replay a session and break it down request by request. Isham Faizal Sep 21, 2026 • 2 min read If you ever used an agent harness like Claude Code, Codex, OpenCode, or Pi, there are some things that are unintuitive.
- ▪Experiments How Agent Harnesses Work, With a Replay of a Real Session How do Claude Code, Codex, and other tools interact with the model?
- ▪We can replay a session and break it down request by request.
- ▪Isham Faizal Sep 21, 2026 • 2 min read If you ever used an agent harness like Claude Code, Codex, OpenCode, or Pi, there are some things that are unintuitive.
Hacker News (AI / LLM) files mainly under ai. We currently carry 5,890 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | ishamf.dev |
| Canonical URL | https://ishamf.dev/p/agent-harness-replay/ |
| Publication time | Mon, 21 Sep 2026 15:46:36 +0000 |
| Retrieval time | 2026-09-21T15:48:49.022Z |
| Last seen | 2026-09-21T15:48:49.022Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | YZIPRjxeYyAB · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Experiments How Agent Harnesses Work, With a Replay of a Real Session How do Claude Code, Codex, and other tools interact with the model? We can replay a session and break it down request by request. Isham Faizal Sep 21, 2026 • 2 min read If you ever used an agent harness like Claude Code, Codex, OpenCode, or Pi, there are some things that are unintuitive. Why does your first request already consume thousands of tokens? What are these millions of "cached tokens" consumed in just a few minutes? Why does it feel like a session gets more expensive the longer it runs?I think these can be explained by looking at what the agent is doing behind the scenes. Each request represents an API call to the model provider. You can click on the requests to see the inputs and outputs. Loading...
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at ishamf.dev.