See which private files your coding agents touched and why
Claude Code and Codex save every conversation on disk, each subagent in its own file. agentwhy reads them locally and shows which private files an agent reached, the task behind it, and which key to change, without ever displaying the secret.
Source
@KozerKarol on X · 2026-10-18
Written in our own words. Credit to the original author. Link checked 2026-10-18.
What they did
Claude Code and Codex save every conversation on disk, each subagent in its own file. agentwhy reads them locally and shows which private files an agent reached, the task behind it, and which key to change, without ever displaying the secret.
Result (as claimed)
Runs locally.
Tools they used
Cost: Claude Code: from $17/mo; OpenAI Codex: free plan, paid from $8/mo.
Set it up
Pick a contained repo or task
Start on a branch or side project where mistakes are cheap.
Install and configure
Set up Claude Code, OpenAI Codex. Read what it can run on your machine and limit permissions where possible.
Run it on a real task
Give it a well-scoped issue and let it work. Review the diff like any pull request.
Add guardrails
Keep tests and CI in the loop, and never let an agent push to main or touch production secrets unattended.
Copy the full setup prompt
Paste into your agent and it will walk you through the setup, asking before anything that sends, posts or spends.
You are helping me set up this AI use case end to end in Claude Code. Goal: See which private files your coding agents touched and why What the original author did: Claude Code and Codex save every conversation on disk, each subagent in its own file. agentwhy reads them locally and shows which private files an agent reached, the task behind it, and which key to change, without ever displaying the secret. Reported result (as claimed by the author): Runs locally. Source: https://x.com/KozerKarol/status/2111804948929298600 Tools they used: Claude Code, OpenAI Codex Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Codex. Goal: See which private files your coding agents touched and why What the original author did: Claude Code and Codex save every conversation on disk, each subagent in its own file. agentwhy reads them locally and shows which private files an agent reached, the task behind it, and which key to change, without ever displaying the secret. Reported result (as claimed by the author): Runs locally. Source: https://x.com/KozerKarol/status/2111804948929298600 Tools they used: Claude Code, OpenAI Codex Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Grok Bot. Goal: See which private files your coding agents touched and why What the original author did: Claude Code and Codex save every conversation on disk, each subagent in its own file. agentwhy reads them locally and shows which private files an agent reached, the task behind it, and which key to change, without ever displaying the secret. Reported result (as claimed by the author): Runs locally. Source: https://x.com/KozerKarol/status/2111804948929298600 Tools they used: Claude Code, OpenAI Codex Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
The Daily 5
Get five new use cases tomorrow morning
Free. Real sources. Unsubscribe any time.
Guides for this use case
How to vibe code an app with Claude Code · How to build AI agents for SEO and ads · How to run multiple coding agents together · How to secure vibe-coded apps and agents
Related use cases
See which coding agent chat is waiting on you from one local board
DHI Orbit is one local board for Claude Code, Codex, Cursor, Gemini CLI and Antigravity that shows what needs you, what is working, your usage limits and a reply box.
See all your running coding agents as a live team call
Agent Standup is a local visualizer that shows Claude Code, Codex and Mistral Vibe sessions as a live team call and session board, so you can spot the agent that is waiting on you.
See what your coding agent sessions really cost
Frugal Tokens reads your coding agent sessions and shows overall usage, estimated working time, overlapping sessions and where spend comes from across models and cache misses.
Browse, back up and move your local AI coding chats between CLIs
An open-source app that shows all your locally saved AI chats across accounts for Claude Code, Codex, Cursor, Gemini CLI, OpenCode and Cline. You can view, back up, export or copy chats, or continue a chat in another CLI.