Feature tour

Once installed, soloco opens the local UI in your browser. The left rail holds the main entries: Canvas, Employees, Results, Assets, with Dashboard and Settings at the bottom.

Some controls depend on the selected agent runtime. The runtime matrix lists the current differences.

Canvas

The organization canvas is the main view: the CEO and every employee is a card, showing live who is doing what and what they produced.

• Give a goal — describe it in plain language in the composer; you can pick the runtime, set a working directory, and attach files. Claude Code and Codex expose supported model controls; DSH follows its runtime default.
• Steer mid-run — no need to wait for a run to finish; add instructions to a running goal at any time, and the CEO acknowledges with a delivery receipt.
• Ask (AMA) — on supported runtimes, ask a running goal "how is it going?" read-only, without interrupting execution. DSH does not currently support AMA.
• Progress since you last looked — come back after time away and the canvas summarizes what happened while you were away.

Results

Deliverables live in the results view: aggregated per goal, with an inspector panel that previews code, images, and documents in place — no folder digging.

Assets & connections

The assets page manages the external capabilities agents can use — each one under your control:

• MCP connections — import the MCP (Model Context Protocol) tools already configured in your local CLIs in one step.
• Email — connect your own mailbox. Agents can only draft; every draft goes out only after you approve it.
• GitHub — connect via device-code authorization; the access token is stored encrypted on your machine and can be revoked in one click at any time.
• Browser — Chrome capability has a master switch, is granted per mission, and can be revoked in one click at any time.
• Credentials — credentials that tasks need are stored centrally and provided to a task only when it actually uses them.

Browser, MCP, and Skills delivery depend on runtime support and are not currently available to DSH runs. See Agent runtimes.

Dashboard & settings

The dashboard is your command brief: autonomous progress, decisions waiting on you, and the state of standing missions. Settings covers runtime health, supported model preferences, interface language, notifications, and the data & statistics switches. DSH must be selected explicitly for a mission and is never used as an automatic default or fallback.

Command line

Beyond the browser UI, the common commands:

soloco            # start (opens the local UI)
soloco doctor     # diagnose your environment
soloco update     # self-update
soloco runtimes   # list the agent runtimes detected on this machine
soloco goal start / steer / resume    # script goals and mid-run steering

When something goes wrong, besides soloco doctor you can generate a context-rich problem report from the local UI and paste it straight to your AI assistant.