AI coding sessions from Claude Code and others store API keys in plaintext
10/31/2026 — 10/31, 22:18·1 sources (all)·1 reports (all)
Key takeaways
- A ReclaimLLM article notes that AI coding tools such as Claude Code, Codex, Cursor, and Copilot write each session to local JSONL files in p…
Background & analysis
On October 31, 2026, DEV Community's AI section carried a post sourced from ReclaimLLM, originally published at reclaimllm.com/blogs/ai-coding-transcripts-secret-store. Its central claim is that AI coding tools including Claude Code, Codex, Cursor, and Copilot write every session to local disk as a plaintext JSONL file, and that any API key pasted into a session is stored there as well. As a result, the article argues, the real leak surface is typically the transcript copy sitting on the laptop rather than the model provider itself.
The piece goes on to publish a per-tool path table showing where each tool leaves its transcripts on disk, along with a scan recipe for finding pasted secrets. For remediation it prescribes a fixed order of operations: rotate the exposed keys first, then purge the stored transcript files, and finally add guardrails to prevent a recurrence. The article also cites a 2026 GitGuardian analysis reporting a 3.2% leak rate in public commits tied to Claude Code, against an overall baseline of 1.5%.
As of this report, there is no mention of responses from the vendors involved, patches to the transcript-writing behavior, or any follow-up work. The matter therefore stands at the point where the plaintext storage practice and its associated exposure have been publicly described, with the proposed remedy resting on user-side key rotation and cleanup rather than any confirmed tool-side fix.
AI-generated from 1 reports · updated 2 hours ago
Related AI tools
- Heat index
- 94
- All sources
- 1
- All reports
- 1
- First seen
- 2 hours ago
Reports on this story headlines open the original
A ReclaimLLM post notes that Claude Code, Codex, Cursor, and Copilot write each session to a plaintext JSONL transcript on your machine, so any API key pasted during that session is stored there too. It lists per-tool paths and a rotate-purge-prevent fix order, citing GitGuardian's 2026 analysis that 3.2% of commits tied to Claude Code assistance leaked secrets versus a 1.5% baseline.
DEV Community · AIAI score 69
Other stories people are talking about
- Heat index 801RisingCursor removes tampered Claude Code extension, up to 5,000 developers affected14 sources
- Heat index 46Open-source mydash lets users view Claude Code and Codex outputs on mobile1 sources
- Heat index 67Developer uses Claude Code to turn playtest feedback into game levels1 sources
- Heat index 49cc-pair pairs Claude Code and Codex as coder and reviewer1 sources
- Heat index 39Configure Claude Code in GitHub Actions for controlled team use1 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion

