All activity
Local-first proxy that keeps API keys out of AI agent context. Your agent sends requests to localhost — Aegis injects real credentials on the outbound HTTPS request. The agent never sees the raw key.
Encrypted vault, domain allowlists, full audit trail, per-agent scoping, YAML policy engine, and native MCP server for Claude Desktop, Cursor, VS Code, Windsurf, and Cline.
No SDK. No cloud. No code changes. Open source (Apache 2.0).

AegisYour AI agent's API keys, locked down and audited
Samleft a comment
Hey 👋 I'm Sam, the maker. I built Aegis because AI agents need to call real APIs — Slack, GitHub, Stripe — and the standard way to give them access is handing over the raw API key. Drop it in an env var, paste it into a config file, and hope for the best. The problem is that agents process untrusted input: user prompts, tool outputs, web content. A prompt injection can instruct the agent to...

AegisYour AI agent's API keys, locked down and audited
