git404hub

what is theharbinger fr?

n0tduck1e/theharbinger — explained in plain English

Analysis updated 2026-07-24

7GoAudience · ops devopsComplexity · 4/5Setup · hard

tl;dr

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.

vibe map

mindmap
  root((repo))
    What it does
      Secures non-human identities
      Transparent proxy gateway
      Policy checks per request
      Placeholder to real secret swap
    How it works
      No agent code changes needed
      Two question policy check
      Secret released at last moment
      Blocks secret exfiltration
    Components
      Admin server control plane
      Gateway server data plane
      CLI client for management
      Browser UI for admin
    Tech stack
      Go
      Gateway proxy
      Cryptographic identities
    Use cases
      Protect AI agent credentials
      Secure service accounts
      Prevent secret exfiltration
    Audience
      Security teams
      Ops engineers
      Agent developers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Point your AI agent's traffic at Harbinger to automatically protect its credentials without changing code.

VIBE 2

Stop a compromised agent from leaking secrets to attacker-controlled servers.

VIBE 3

Manage which agents can access which websites and credentials from a browser dashboard.

VIBE 4

Wrap an existing agent process so its traffic routes through the security gateway automatically.

what's the stack?

GoProxyBrowser UICLI

how it stacks up fr

n0tduck1e/theharbingerdemomanito/helperemersion/minilustre
Stars777
LanguageGoGoGo
Last pushed2023-03-072019-01-07
MaintenanceDormantDormant
Setup difficultyhardeasymoderate
Complexity4/51/54/5
Audienceops devopsgeneralresearcher

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · hard time til it works · 1h+

Requires deploying and connecting multiple components: an admin server, a gateway server, a database, and a vault for secrets.

The explanation does not mention a license, so it is unclear what permissions apply to using this software.

in plain english

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.

prompts (copy fr)

prompt 1
I have an AI agent that calls external APIs. How do I configure Harbinger as a transparent proxy so the agent uses placeholder credentials instead of real ones?
prompt 2
Help me write a policy in Harbinger that allows a specific agent to access a particular website but blocks it from using credentials on any other host.
prompt 3
Explain how to use the Harbinger wrapper daemon to route an existing agent's traffic through the gateway without modifying the agent's source code.
prompt 4
What are the steps to enroll a new AI agent in Harbinger and assign it a cryptographic identity using the CLI client?

Frequently asked questions

what is theharbinger fr?

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.

What language is theharbinger written in?

Mainly Go. The stack also includes Go, Proxy, Browser UI.

What license does theharbinger use?

The explanation does not mention a license, so it is unclear what permissions apply to using this software.

How hard is theharbinger to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is theharbinger for?

Mainly ops devops.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.