Approval Workflows

Status: Available.

When a policy rule returns escalate, msh local blocks the AI agent's HTTP connection and waits for a human operator to approve or deny. Approvals are handled by an in-process IPC broker inside the daemon.

How approvals work

01. ESCALATE

The daemon's policy engine returns escalate. The proxy goroutine submits the request to the approval broker and blocks the AI agent's connection.

02. NOTIFY

The broker mints an approval ID and publishes an approval_requested IPC event. The desktop app shows a banner; the CLI can list pending approvals.

03. DECIDE

The operator approves or denies via the desktop app or the msh local approvalCLI commands.

04. RESUME

The broker receives the verdict and unblocks the proxy goroutine. The AI agent's connection is either forwarded to the upstream or returned a 403 — no retry or polling needed by the AI agent.

The default timeout is 30 seconds. If no decision is made within the timeout window, the request is automatically denied.

Desktop app

When the desktop app is running it shows a banner for each pending escalation. Click Allow or Deny to resolve it. The AI agent's blocked connection is released immediately.

CLI commands

# List pending approvals
msh local approval list

# Approve a specific request
msh local approval allow <id>

# Deny a specific request
msh local approval deny <id>

# Emit pending approvals as JSON (useful for scripts)
msh local approval list --json

# Include an operator-supplied reason in the audit record
msh local approval allow <id> --reason "scheduled maintenance window"
msh local approval deny <id> --reason "not expected at this time"

The <id> value is the approval ID shown by msh local approval list(format: appr_<8 hex chars>).

Watching for approvals

# Watch pending approvals and answer prompts
msh local approval watch

msh local approval watch subscribes to pending approval prompts and lets you answer them interactively in the terminal.

There is one approval broker per daemon process. All approvals share the same 30-second timeout window. Multiple pending approvals can be queued simultaneously — each is independently resolvable.

There are no webhook, Slack, PagerDuty, or HMAC callback approval modes in the current release. All approvals go through the desktop app or the msh local approval CLI. External integrations are on the roadmap.

Time-boxed access escalation

A local approval releases one held request; it does not grant a time-boxed role or SSH resource. For elevated access, use Mezite Access Requests through msh request. The access grant expires at the end of its TTL; local gateway policy continues to apply.

msh request create --roles=admin --duration=1h --reason="Scheduled maintenance"
msh request ls