Sidecat
AAuth operator console
Credential grants
Approve real work without handing agents raw authority.
This demo shows how a human operator can define mission language, admit bounded credentials into sidecatd custody, and review an AAuth interaction before a credential-backed effect is spent.
Operator
Authenticated local operator session
Signed in as
operator:demo:alex
The live console authenticates the human before any agent request can be approved.
Authority boundary
The browser session can approve or deny interactions. It does not make the agent the operator.
Credential catalogue
Browse provider profiles
Each profile describes one real service Sidecat could hold under operator-defined bounds. The catalogue, mission builder, and admit form are generated from the same provider records.
Mission guidance
Give the agent language it can cite
Mission and credential are separate. A mission says what kind of work is in scope. A credential grant says what secret sidecatd may hold and spend under limits.
Mission guidance JSON for agents
Admit credentials
Choose one credential to place in sidecatd custody
Demo v1 simulates admission. A live Person Server sends the secret once to sidecatd connector custody and does not retain the secret.
Manage grants
Review, suspend, and audit admitted grants
| Credential | Provider | Purpose | Bounds | Status | Action |
|---|
AAuth interaction
Review a pending credential-backed effect
- Agent
- aauth:codex@sidecat.local
- Description
- Authorize package-mediated sidecatd effect
- Interaction code
- DEMO-V1
Mission binding
AAuth live GitLab push demo.
Mission fit
The requested provider, effect, target, and evidence expectation are checked against operator guidance.
External effect
Git push through Sidecat. This is a credentialed external write and is not automatically reversible.
Credential boundary
No credential secret is sent to the agent. sidecatd spends only an admitted grant for the declared provider and purpose.