CLI

The local boss CLI

The boss command controls and inspects the desktop application from a shell. The website cli.risaboss.com is a separate service for finding and viewing live sessions; see Live sessions and window sharing.

Set up the command

Install BossConsole, then use Toolbox → Tools → Install BOSS CLI if the command is missing from your PATH. On Windows, the packaged shims include boss.bat and boss.ps1.

Open things in the desktop

boss https://github.com
boss folder ~/projects/my-app
boss file src/main.kt
boss terminal

Inspect the running app

boss status
boss status --json
boss doctor
boss doctor --json

The status/doctor agent-harness commands inspect an already running application; they do not start the desktop when it is closed. boss doctor reports health problems and suggested next steps. Its exit status is 0 when healthy, 2 when degraded, and 1 when the application is not running.

Discover and use tools

boss mcp list
boss mcp describe <tool_name>
boss mcp invoke <tool_name> --args '<json_arguments>'

Replace the placeholders with a tool name and valid JSON matching its schema. Discover them first. The CLI lists tools in the host plugin registry; built-in terminal MCP server tools are a separate surface. Tool availability depends on installed plugins, disabled tools, and account permissions. Invocation is subject to the same governance controls as other governed MCP calls.

For the operation history:

boss mcp ledger tail
boss mcp ledger verify

Ledger verification checks the retained hash chain; it is not a guarantee that every recorded operation was safe.

Plugin development

boss plugin init my-tools
boss plugin validate ./my-tools
boss plugin link ./my-tools

Build before linking. See Plugins for the complete starter workflow.

Source: full CLI reference, including arguments, JSON output, authentication, timeouts, completion, and plugin packs.

---

Continue: Home · ← Live sessions and window sharing · Development and contributing →