Show HN: Kontext CLI – Credential broker for AI coding agents in Go
AI agents are pasting API keys into chat. This startup just shipped the credential broker to stop it.
Why it matters
As AI coding agents move into production, credential management has become a critical security gap. Kontext CLI solves the immediate problem—short-lived, scoped credentials for agents—and creates the audit trail (who, what, when, why) that enterprises need to govern autonomous access at scale.
The key facts
8 to knowKontext CLI ships credential brokering for AI coding agents
Works with Claude Code; Codex support incoming
~5ms overhead per tool call (Go + ConnectRPC)
Holds upstream secrets server-side; CLI receives only short-lived scoped tokens
Captures full audit trail: agent action, result, policy decision, user attribution
Server-side policy enforcement (allow/deny on tool calls) in development
Credentials stored in system keyring; OAuth refresh tokens managed by backend
Targets current pain point: teams pasting long-lived API keys into .env or agent chat
Go to the source
Hacker Newsgithub.com
Publisher excerpt: 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…