Stop Telling Claude to Read Your .env File
The advice spreading across AI communities — 'just create a .env file and have Claude read it' — is wrong, and here's why it matters.
Read post →From the vault
Credential leaks, MCP security, zero-knowledge architecture — written for engineers building with AI coding agents.
The advice spreading across AI communities — 'just create a .env file and have Claude read it' — is wrong, and here's why it matters.
Read post →Claude Code reads your project files, including .env. Here's the right way to handle API keys so they never enter the model's context window.
Read post →The standard .env approach exposes your API keys to Claude's context window. Here's the correct way to store and use secrets with Claude Code.
Read post →OpaqueVault is the only MCP-native secret manager built for AI coding agents. Here's how it works, why the architecture matters, and how to set it up in five minutes.
Read post →How to manage credentials across MCP servers without exposing them to the AI. Architecture, patterns, and a reference implementation with OpaqueVault.
Read post →A zero-knowledge secret manager means the server cannot decrypt your secrets. Here's why that architecture matters — especially when AI coding agents are in the loop.
Read post →Researchers found 24,008 live API keys and credentials inside Claude Desktop MCP configuration files. Here's what went wrong and how zero-knowledge vaults change the equation.
Read post →HashiCorp confirmed HCP Vault Secrets reaches end-of-life on July 1, 2026. If you're using it today, here's what you need to know and where to move your secrets.
Read post →Claude Code, Cursor, and GitHub Copilot dramatically accelerate development — and, if misconfigured, dramatically accelerate credential exposure. Here's the structural problem and how to fix it.
Read post →