Skip to content
Select themeSelect language

Web terminal commands

The web terminal at /cli accepts the following commands.

The web terminal at /cli running SupaCloud control commands.The web terminal at /cli running SupaCloud control commands.
Command Description
status [--all] Active tasks (--all includes completed).
task <id> Task details with cost, duration, last activity.
issues <project> List a project’s open issues with copyable ids.
backlog <project> [status|scan [--apply]] Show a project’s backlog; scan proposes items and --apply dispatches them (ADR 0039).
run <project> <agent> [--issue <id>] [--model <id>] [--exec-mode <normal|workflow>] [--effort <level>] <prompt> Launch a task and enter live mode. --exec-mode sets the execution mode (the word mode is reserved for the harness build|plan mode command); --effort (minimal|low|medium|high|max) is a per-task override (ADR 0045).
follow <id> / f <id> Enter live mode for a running task.
logs <id> [--follow] Show the last events, optionally stream live. Takes a task id or — new — a run id from runs (short ids work for both): a workflow run’s log is its recorded step timeline, each step named by its display title. Run ids resolve against the recent runs runs lists.
intervene <id> <msg> Send a message to a running task.
cancel <id> Cancel a task.
approvals [--filter=tool|workflow] List pending human decision gates; without a filter both sources are shown (ADR 0045). Decide with approve/reject <run-id> (workflow gates) or approve-tool/reject-tool <id> [note] (interactive tool/question/visual gates).
workflows List all workflows across projects.
workflow <name|id> Workflow details. Accepts the workflow’s exact name, its id, or the short id workflows prints (a unique prefix resolves; a tie lists nothing rather than guessing).
workflow <name|id> trigger Manually start a run of the workflow. The older workflow trigger <id> form still works.
runs [--status=X] List recent runs.
runners List runners with status.
resources List resources (SMTP, Telegram, Webhook).
repo-sync status|push|pull Repo sync operations.
workspace / ws Show the active workspace.
workspace switch <name> Switch workspace.
workspace config autonomy-level [<0-100>] Show the resolved workspace autonomy (level, plan ceiling, onboarding cap, policy) or set the stored level. Setting is admin/owner-gated server-side (ADR 0045).
workspace config approval-mode <project> [<none|pr_draft|human_gate>] Show or set a project’s PR-review approval mode. Setting is admin/owner-gated server-side.
workspaces List all workspaces.
usage Show the per-provider subscription-saturation windows for the active workspace (admin/owner-gated).
budget Show the $-budget status (cap, month spend, remaining, alerts).
skills proposals [approve|reject <id>] List induced-skill proposals, or decide one by its id prefix. Deciding is workspace-admin only server-side (ADR 0045).
schedules List schedules.
schedule add|pause|resume|delete Manage schedules.
projects List projects.
debug on|off Toggle debug mode for your current live/follow session to reveal internal operations in the feed (#583). Available only while a workspace admin has opened the debug ceiling.
density reduced|chatty Set the persistent live-feed verbosity (reduced = lean, chatty = full thinking and tool detail).
language de|en Set the language.
clear Clear the terminal.
help List the available commands.

Every id the terminal prints is a link — the full UUID on a detail line and the 8-character short id a listing shows. Click an id to copy the full id to the clipboard (the terminal confirms with Copied …); Ctrl/Cmd-click to open the task, run or workflow it names. A short id is resolved against your tasks, runs and workflows; when more than one item starts with it the terminal says so rather than guessing. Commands that take an id (task, logs, follow, cancel, intervene, …) accept the same short id you see in a listing.

After run or follow, the terminal enters live mode: press Enter to send input as an intervention (no command prefix needed), and Ctrl+C to exit.

debug on turns on debug mode for your current live/follow session only, revealing internal operations in the feed — MCP tool calls, scope resolution, gate auto-resolves and danger escalations. debug off turns it back off.

Debug output is gated by an allow-debug ceiling that a workspace admin opens (it is off by default). With the ceiling closed, debug on has no effect. The setting is per session and ephemeral: it covers only the session you are in, is never persisted, and is enforced server-side. Start a new live/follow session and you start with debug off again.