Your AI thinks locally. It acts through the Airlock.
A GitHub-first authorization gateway between your local AI agent and the outside world. Every protected action passes through risk-tiered policy, delegated Auth0 Token Vault exchange, and explicit human approval for high-risk operations.
The AI agent reasons locally and emits structured intent requests. The Airlock enforces risk policy, exchanges a delegated token from Auth0 Token Vault, executes one allowed action, and immediately clears the token from memory.
Local AI Agent
LangChain + OpenAI
Airlock Gateway
Risk engine + approval queue
GitHub API
One action, token cleared
Every agent action is classified into GREEN (auto-execute), AMBER (execute + notify), RED (block for approval), or BLOCKED (hard deny). Provider OAuth scope is the outer boundary; Airlock policy is the inner boundary.
| Action | Tier | Airlock behavior |
|---|---|---|
Read issues / PRs | GREEN | Auto-execute, token cleared after read |
Add labels | AMBER | Execute + notify dashboard |
Comment on PR | AMBER | Execute + notify dashboard |
Merge PR → main | RED | Block until Auth0 approval + Token Vault exchange |
Delete repo | BLOCKED | Permanently blocked, outside Airlock charter |
The AI agent never sees, stores, or transmits provider tokens. Auth0 Token Vault is the only credential store.
Live animated timeline of every token exchange lifecycle: born → active → used → cleared — visible in real time.
Radial visualization showing which actions are auto-approved (green), notify-only (amber), or gated for approval (red).
Protected-branch merges require explicit approval via an Auth0 re-authentication flow before any token is exchanged.
Every authorization decision, token event, and approval is logged in PostgreSQL. Filterable and exportable as JSON.
Delete, transfer, and admin actions are permanently blocked — no approval path, no override, no backdoor.
Tokens are never stored. They are requested on demand, used for a single action, and immediately cleared from Airlock memory. Every step is shown in the Token Pulse.
Connect your GitHub account through Auth0, point the Airlock at one allowlisted repository, and watch every intent flow through the dashboard in real time.
Connect GitHub via Auth0