The tappass CLI is the operator interface to TapPass. Workspace commands (agents, audit, policy, approvals, connectors, …) run against your configured server — set it once with tappass config set server <url> or override per invocation with --server/-s. Host commands (up, db, backup) run on the machine where the TapPass server is installed. Pass -h/--help on any subcommand for inline reference, --version/-V for the version block (--output json for machine-readable).
So --org-id acme beats $TAPPASS_ORG_ID, which beats the org-id stored in the active context. Contexts live in ~/.tappass/config.toml (non-secret values only — the session JWT is stored separately at ~/.tappass/session).
Run a governed agentic loop as agent cli-try: it reasons over your connected MCP tools and every tool call is governed live (allow / block / approve / shape). --dry-run governs and shows decisions but executes nothing. Works from anywhere: remote runs stream every step and verdict live over SSE
tappass init [-s SERVER] [--defaults]
Set up your organization: connect, sign in, approve tools, set security level, store provider credentials
tappass status
Diagnose your environment and connection (tappass info is an alias)
tappass ask "<question>"
Ask Jorge — the governed assistant — about your workspace (“why was this session blocked?”); the answer streams live with every tool step and verdict visible
tappass login / logout / whoami
Root shortcuts for tappass auth login/logout/whoami (see tappass auth)
tappass test [SCENARIO.yaml] [-a AGENT] [-v]
Dry-run agent calls against live policies — no real API calls
tappass providers
List available providers and their operations
tappass up [--defaults]
Guided setup: storage, runtime, secrets, migrations, start the server
tappass down
Stop the tappass/tappass-pg containers (data preserved)
The unified credentials group — session verbs, personal access tokens, per-agent developer keys, and scripting/SDK credentials. The everyday session verbs are also registered at the root: tappass login, tappass logout, and tappass whoami are shortcuts for tappass auth login/logout/whoami.
Sign in. Default: Personal Access Token prompt (like gh auth login); --with-token reads a tp_pat_… token from stdin. --server is persisted to the active context
tappass auth logout
Sign out and clear the stored session
tappass auth whoami
Show the current identity
tappass auth session
Inspect the current session
tappass auth print-token
Print the current bearer token to stdout (nothing else) — the scripting escape hatch: curl -H "Bearer $(tappass auth print-token)" …
tappass auth application-default login
Write Application Default Credentials to ~/.tappass/application_default_credentials.json; the SDK picks them up automatically (no explicit key configuration)
tappass auth application-default revoke
Delete the Application Default Credentials file
tappass auth pat create <name> / list / revoke <id>
Register an agent and write its .env; --from-file batch-registers from YAML (--continue-on-error to skip failures). tappass agent onboard is a deprecated alias
tappass agent suspend <uuid> / activate <uuid>
Hard stop (gateway rejects all calls) / reactivate
Create a policy from a described purpose (→ smallest capability envelope), a JSON file of authored rules, or pre-filled from a template. -i reviews the derived rules interactively (adjust / drop / approve) before anything persists; --dry-run previews without persisting. The single “make a policy” verb (supersedes agents govern / pack apply)
tappass policy rules list / get <id> / instantiate <id> -p k=v
Compile a policy’s active version into its runtime config and install it at the runtime’s standard path (merged into whatever is already there); --stdout prints instead of installing
Curated multi-rule starter sets (OWASP agentic baseline, coding-agent safety, compliance frameworks, …) — the same catalog as Policies → Templates in the dashboard. Apply one via the dashboard or build on it with policy create
tappass capability list [--connected] [-c CAPABILITY] [-o table|json]
Read-only tree unfolding each capability into the servers and tools that fulfil it (each tool tagged → intent). --connected limits to your connected MCPs instead of the full catalog; -c drills into one capability
A connector is a capability-fulfiller — an MCP server plus its tools. This one group covers the catalog, connection lifecycle, grants, and per-tool controls.
tappass model list, register, test, set-price, update, archive — the org’s model registry. update edits in-place metadata (--enable/--disable, --display-name, --icon-url); set-price cuts a new price version (--cost-input/--cost-output, cost per 1k tokens).
BYOK provider keys nest under model as key: tappass model key list, get <provider>, set <provider> --key KEY (use --key @path or --key - for stdin — never leaks the raw key), rotate <provider>, delete <provider>.