Analysis updated 2026-07-24
Point your AI agent's traffic at Harbinger to automatically protect its credentials without changing code.
Stop a compromised agent from leaking secrets to attacker-controlled servers.
Manage which agents can access which websites and credentials from a browser dashboard.
Wrap an existing agent process so its traffic routes through the security gateway automatically.
| n0tduck1e/theharbinger | demomanito/helper | emersion/minilustre | |
|---|---|---|---|
| Stars | 7 | 7 | 7 |
| Language | Go | Go | Go |
| Last pushed | — | 2023-03-07 | 2019-01-07 |
| Maintenance | — | Dormant | Dormant |
| Setup difficulty | hard | easy | moderate |
| Complexity | 4/5 | 1/5 | 4/5 |
| Audience | ops devops | general | researcher |
Figures from each repo's GitHub metadata at analysis time.
Requires deploying and connecting multiple components: an admin server, a gateway server, a database, and a vault for secrets.
Harbinger is a security platform for non-human identities: AI agents, bots, and service accounts. It gives every agent a cryptographic identity, checks each request it makes against a policy before allowing it through, and pulls real secrets from your own vault only at the last moment. The agent itself never holds a standing credential. The project frames itself around non-human identity security in general, with AI agents as the sharpest example. Most current agent security tools either require rewriting your agent against an SDK, show you a dashboard of what credentials exist without changing how they work, or just move responsibility from one API key to another. Harbinger takes a different approach. It is a transparent proxy, so you point your agent's traffic at the gateway and it is covered. No code changes are needed, and third-party agent frameworks you do not control work too. Every request with credentials gets checked against two questions: is the agent allowed to access this website, and is the agent allowed to use this credential against this website? Only when both are true does the agent get to use the credential. Agents receive a placeholder instead of a real secret. The gateway swaps in the real value only after policy authorizes that agent for that target and confirms the request is actually headed to the registered destination. This stops a compromised agent from exfiltrating a secret to an attacker-controlled host. The system has several components. An admin server acts as the control plane, owning the database, policy storage, and enrollment review. A gateway server is the data plane that all agent traffic passes through. A command-line client handles setup and management. A browser UI covers everything except cryptographic operations. An optional wrapper daemon runs an existing agent as a child process and routes its traffic through the gateway automatically. The full README is longer than what was shown.
Harbinger is a security proxy for AI agents and bots. It checks every request against a policy, swaps placeholders for real secrets only at the last moment, and works without changing your agent's code.
Mainly Go. The stack also includes Go, Proxy, Browser UI.
The explanation does not mention a license, so it is unclear what permissions apply to using this software.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.