Skip to content

Approval Model

SuperDev separates read tools from write tools. Read tools can run directly. Write tools should also be called directly; if approval is required, the MCP server creates the pending approval, waits for the desktop decision, and retries with the one-time token.

  • Do not preflight every write by manually calling list_operation_approvals or get_operation_approval.
  • Call write tools without approval_token; use the default wait behavior.
  • Use approval_wait_seconds=0 only when you intentionally want a manual token flow.
  • Config changes still require preview_config_change before apply_config_change.
  • Avoid direct upsert_* tools unless the user explicitly asks to bypass preview/apply.

When approving an operation, the user can grant a project-level grace window. During that window, later writes in the same project pass without another prompt. The default window is 15 minutes.

This keeps batch setup work smooth while preserving the user’s explicit approval boundary.