Temporary Access (Capability Tokens)

Capability Tokens is an experimental authority broker. A token binds permission to a specific run, step, tool, expiry, use count, and optional resource constraints.

Raw credentials are never placed in token claims, ledger payloads, or normal CLI output.

Enable capability enforcement

odinn experimental enable capabilities --confirm-impact

Enabling this feature changes direct CLI execution: ordinary tool runs require a matching scoped token while enforcement is active. Prepare the token before returning to a manual workflow.

Issue a token

odinn experimental capabilities issue \
  --run <run-id> \
  --step <step-id> \
  --tool <tool>

The raw token is hidden by default. Use --show-token only when the immediate caller needs it, and never place it in logs or screenshots.

Inspect and revoke

odinn experimental capabilities list <run-id>
odinn experimental capabilities revoke <capability-id>

The broker validates signature, expiration, run and tool binding, resource constraints, revocation state, and replay count before recording a use.

Advanced: consume a token

odinn experimental capabilities use \
  --token <token> \
  --run <run-id> \
  --tool <tool>

Use the narrowest scope, shortest practical expiry, and one use unless a documented workflow requires more.

Limits

A capability token authorizes invocation; it is not credential isolation or an operating-system sandbox. The invoked tool still runs within its documented adapter and host authority. Revocation stops future use but cannot reverse an external action that already completed.