Interface

CLI

The CLI supports interactive work, headless prompts, checkpoint management, and run history browsing.

Command Reference

Command	What it does
`quasar`	Starts the interactive CLI run flow.
`quasar "..."`	Runs a direct prompt in headless mode.
`quasar --resume`	Resumes from an active checkpoint and forces restart semantics.
`quasar --clear`	Clears the active checkpoint and current workspace state, but keeps archived runs.
`quasar --fresh`	Clears current workspace state and archived runs, while preserving downloaded docs and dotfiles.
`quasar --history`	Opens an interactive per-task checkpoint history browser.
`quasar --config`	Shows current configuration values.
`quasar --config validate`	Verifies required configuration such as `MODEL_API_KEY`.
`quasar --info`	Prints system and environment context such as workspace path and platform.
`quasar --no-rag "..."`	Runs without documentation retrieval for that specific prompt.
`quasar \execution-overview`	Prints the current or latest archived execution overview report.
`quasar \usage-report`	Prints the current or latest archived usage report.
`quasar \revert <task>`	Reverts the active checkpoint and workspace back to the start of a task.

Interactive Backslash Commands

Inside the interactive CLI, type \ at the start of the input box to show the command picker. Commands use a backslash prefix only; slash-prefixed commands are not supported.

Command	What it does
`\settings`	Opens the interactive system settings panel.
`\refresh`	Clears and redraws the CLI, then reloads checkpoint state.
`\execution-overview`	Displays `quasar_logs/execution_overview.md` from the current or latest archived run.
`\usage-report`	Displays `quasar_logs/usage_report.md` from the current or latest archived run.
`\revert <task>`	Prompts for confirmation, then restores the checkpoint and task folders to the start of that task.

\revert <task> is intended for active checkpoint runs. For example, \revert 2 restores the run to the start of Task 2, removes later checkpoints, deletes task folders from Task 2 onward, and then reloads the checkpoint view so you can resume from that point. The CLI refuses to revert while an execution is running.

Interactive run flow

After you submit a request and confirm settings, the Strategist produces an execution plan. Before the Operator starts, the CLI enters a plan confirmation step: you can approve the plan, decline it (the run stops in a controlled way), or revise it by sending feedback so the Strategist can adjust the plan. This human-in-the-loop gate applies to normal interactive runs.

Automatic follow-up runs driven by AUTO_IMPROVE_CYCLES confirm the plan without prompting. For unattended or scripted sessions where you still want the graph to proceed without blocking, set AUTO_CONFIRM_PLAN to true (see Configuration).