# Your AI Agent Remembers Your Secrets > Source: > Published: 2026-06-21 04:42:13+00:00 The practice of keeping sensitive keys in a `.env` file is a fundamental rule of modern development. It is the first line of defense that every developer learns. However, the rise of AI coding agents has introduced a subtle complication: keys are shared in agent chats and the agent might still end up creating a permanent record of those secrets elsewhere. Even when a developer is careful to use a `.env` file, the moment a key is mentioned in a chat or read by the agent to debug a connection, it is recorded. We found thousands of lines of session data tucked away in hidden folders. Within these logs, API keys and access tokens were sitting in plain text, completely unencrypted and accessible to anyone who knows where to look. You might wonder why these tools keep such detailed records. It comes down to a feature called conversation lookup. To provide helpful follow-up answers, Claude needs to remember what happened earlier in your session. By saving this history locally, the tool ensures that it does not lose its train of thought if you restart your terminal. The problem is that these records are typically stored in files like `session.jsonl` inside the `~/.claude/projects` directory. Because AI agents transmit full conversation transcripts and tool outputs to their providers on every turn, any secret that enters the agent context becomes part of a long-lived on-disk artifact. To fix this, we investigated using the internal hook system of the agent to create a transparent redaction layer. The goal is to allow the agent to use a secret locally while ensuring the real value never reaches the transcript or the API provider. The real secret is resident only inside the PreToolUse process and the local subprocess; the model, the JSONL transcript, and the upstream API see only the placeholder. The implementation works by teaching the model to use placeholders like `@@SECRET:name@@` . When the model tries to run a command, a series of invisible steps occur: **Substitution:** A hook called`PreToolUse` intercepts the command, looks up the real secret on your disk, and swaps the placeholder for the real value just before execution.**The sed-wrap Trick:** To prevent the secret from leaking if the command prints it out, the hook wraps the entire command in a`sed` filter. This filter automatically scrubs the real secret out of the output and replaces it with the placeholder again before the model or the logs ever see it.**Success Rates:** In testing, this "happy path" produced zero leaks across multiple bash calls, as the real value only existed temporarily in the local process. Even with these hooks, secrets can still slip through if an operator types them manually into a prompt or narration. To build a complete defense, we developed a multi-layered approach: **Install Hooks:** Set up`PreToolUse` and`PostToolUse` scripts to handle real-time tokenization and scrubbing.**Use a Sweep Utility:** Integrate a tool like`prismor warden sweep` , which acts as a post-hoc cleanup layer. It scans your agent caches for any residue that may have slipped through the hooks.**Automate Cleanup:** You can configure the agent to run a cleanup sweep automatically every time a session ends by using the`Stop` hook.**Operational Discipline:** The most important step is to ensure that secret material is loaded into its designated directory outside of the agent session. If you never show the real secret to the model, the model can never accidentally repeat it. By combining real-time prevention with regular cleanup, you can cover about 95% of the risk surface and keep your development environment safe from accidental exposure. Our tool is free and open-source to avoid this scenario: [immunity-agent](https://github.com/PrismorSec/immunity-agent)