Keep raw keys out of camp
Permanent credentials never enter the prompt, transcript, shell history, or project files. The model sees a handle—not the secret.
Agent-safe secret brokering
Keep your secretsholstered.
Secure passage through the Wild West of AI development.
Env Holster pulls permanent credentials out of plaintext .env files and gives AI coding agents short-lived, scoped access instead. No raw keys in prompts. No long-lived secrets in chat history.
- No plaintext .env
- No permanent agent keys
- No secrets in transcripts
Env Holster access grantIssued
AgentCodex
ScopeStaging deploy
Expires in 04:59
eh_live_7K4••••••R9Master credential remains sealed
The frontier changedYour .env file didn't
Permanent secrets leave permanent tracks
One innocent file read can expose the keys to your whole operation.
Plaintext secrets were already easy to leak. Agentic tools multiply the places a credential can land: context windows, shared chats, tool output, logs, and copied commands.
.env.local
DATABASE_URL=postgres://prod...STRIPE_KEY=sk_live_...OPENAI_KEY=sk-proj-...One read
Agent context Tool output Chat history
One permanent key. Three new places to lose track of it.
A smaller blast radius
The safest secret is the one your model never sees.
Give agents enough access to finish the job without handing over credentials that outlive the conversation.
Make every credential temporary
Issue access for minutes instead of months. If a temporary key wanders, its useful life is already counting down.
Limit where access can roam
Scope each grant to the provider, task, environment, and agent that requested it. Revoke one without rotating the whole herd.
A safer handoff
Long-lived in.
Five-minute access out.
Env Holster sits between the agent and the service. It turns intent into a temporary capability, then makes that access disappear automatically.
Raw secret
never crosses
never crosses
Holster the permanent secret
Move the credentials scattered across .env files into one encrypted, local-first vault.
Let the agent request a job
Your LLM asks for a named capability with a clear purpose—not a copy of your master key.
Exchange it at the boundary
Env Holster generates or brokers scoped, short-lived access and injects it only where the command runs.
One boundary for the whole stack
Protect the credentials developers reach for every day.
Database credentials
Provider API keys
Cloud & CI tokens
SSH deploy keys
Rides with the tools already in your terminal: Codex, Claude Code, Cursor, and your existing CLIs.
Private beta
Your AI should borrow access—not keep the keys.
Join the design partner list for early builds, architecture notes, and a voice in the workflows Env Holster protects first.
Small, hands-on beta. No spam. Product notes and early access only.