Show HN: Kontext CLI – Credential broker for AI coding agents in Go
We built the Kontext CLI because AI coding agents need access to GitHub, Stripe, databases, and dozens of other services — and right now most teams handle this by copy-pasting long-lived API keys into .env files, or the actual chat interface, whilst hoping for the best. The problem isn't just secret sprawl. It's that there's no lineage of access. You don't know which developer launched which agent, what it accessed, or whether it should have been allowed to. The moment you hand raw credentials to a process, you've lost the ability to enforce policy, audit access, or rotate without pain. The credential is the authorization, and that's fundamentally broken when autonomous agents are making hundreds of API calls per session. Kontext takes a different approach. You declare what credentials a project needs in a .env.kontext file: GITHUB_TOKEN={{kontext:github}} S
Why it failed
We built the Kontext CLI because AI coding agents need access to GitHub, Stripe, databases, and dozens of other services — and right now most teams handle this by copy-pasting long-lived API keys into .env files, or the actual chat interface, whilst hoping for the best. The probl
- Kind
- startup
- Status
- Shut down
- Inventor
- mc-serious
- Ended
- 2026
- Source
- hackernews