Outsider Stage 0.5
Replay and verify a real, sealed Outsider Stage 0.5 intervention chain.
Translation pending
Keep secrets out of AI coding agents. They see names, never values.
Translation pending
SecurityRust · ShellGitHub @dip497OnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Keep secrets out of AI coding agents: agents see names, never values
Translation pending
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
Keep secrets out of your AI coding agent. It sees names, never values.
I kept handing secrets to my coding agent. Paste the API key into the prompt, or just say "read it from my .env".
It works — and now that key sits with the model provider, in the session log on disk, and in whatever output the agent prints next.
hivelock holds that message back before it's sent. The secret goes into a local encrypted vault, and you resend it by name:Read the full README ↗I kept handing secrets to my coding agent. Paste the API key into the prompt, or just say "read it from my
.env".It works — and now that key sits with the model provider, in the session log on disk, and in whatever output the agent prints next.
hivelock holds that message back before it's sent. The secret goes into a local encrypted vault, and you resend it by name:
- STRIPE_SECRET_KEY=sk_live_…the real key you just pasted…
+ STRIPE_SECRET_KEY={{lock:STRIPE_SECRET_KEY}}
The agent only ever works with {{lock:STRIPE_SECRET_KEY}}. When it runs a command, hivelock fills in the real value at the last moment and masks it again in the output:
$ curl -H "Authorization: Bearer {{lock:GITHUB_TOKEN}}" api.github.com/user
[lock:GITHUB_TOKEN] ← what the agent gets back
curl -fsSL https://raw.githubusercontent.com/dip497/hivelock/main/install.sh | sh
Windows PowerShell or cmd:
powershell -NoProfile -ExecutionPolicy Bypass -Command "irm https://raw.githubusercontent.com/dip497/hivelock/main/install.ps1 | iex"
Picks the right binary for your machine, checks it, and asks which agents to protect. Or take one from Releases.
hivelock import .env # move the secrets you already have into the vault
hivelock doctor # check that it's working
hivelock # the manager: list, add, lock, stats
Then work as usual. hivelock help lists every command.
| Paste a secret in chat | held back before it's sent, and handed back to you as {{lock:NAME}} |
| Agent runs a command | real value injected at run time, masked in the output |
| Agent reads a file with secrets | masked before the model sees it, and locked away |
| Old sessions on disk | scrubbed in place |
hivelock lock NAME | human-only: passphrase, agents can't touch it |
hivelock ask NAME | the agent must ask you every single time |
Works with Claude Code · Codex · Copilot CLI · Gemini CLI · Cursor · Qwen Code on Linux, macOS and Windows.
It is not a sandbox. Read what it does and doesn't protect — then usage and agents.
MIT