Show HN: Keyhole – Share secrets with your AI agents

[maferland]

I had the idea for Keyhole while bootstrapping a bunch of small services and apps. I'm trying to prototype fast, and sometimes these need a variety of secrets. I use Doppler to remove myself from the loop, but once in a while I still need to provide a secret. AI agents will suggest you rotate a secret once it's been shared in a chat. I thought it would be a cool experience to let your agent ask for secrets without having them dumped in the context. The agent runs a command, a form pops up in my browser, and I paste the key.

Env vars work. But anything that allows me to stay focused is a win. This isn't perfect, but it solves something for me, and hopefully others will find it useful too.

There's nothing crazy cool technically here, as one might expect; I vibe-coded the whole thing. But I think it's a great UX/DX.

https://github.com/maferland/keyhole claude plugin add github:maferland/keyhole

[perryraskin]

Nice. Obviously this is a huge issue many are trying to solve. Providing agents with a keychain is one thing, but how does this solve the issue of using these keys in projects? Does the agent decrypt it and set it in a .env? Is the CLI required to be used in the build process?

[maferland]

I didn't build Keyhole to solve secret management, there are tools like Doppler for that. It lets the agent handle a secret without having it in context. It can put it where it's needed (e.g. a .env) without ever reading the value.

> Does the agent decrypt it and set it in a .env?

The CLI does it, and the .env can be chmod 600.

> Is the CLI required to be used in the build process?

That's not what I built it for, I'd reach for other tools on the market for that.