Local desktop workspace that supervises project processes and CLI coding agents, with scratchpads, todos and agent spawning exposed over MCP, HTTP and CLI.
Keeping project processes and CLI agents together in a local desktop workspace.
Core features
- Sandboxed runsNo
The site says "Solo manages local processes rather than containers.". Docs and changelog show no agent sandbox.
Source - Diff reviewNo
All docs pages and the changelog were searched for diff and changes. Diffs appear only in prompts for agents to review, and no diff view is documented.
- Agent coordination YesSource
- Scheduled tasks Partial
Agents can set repeating timers through MCP once Timers is turned on, but only into an existing agent process. There is no cron or user-facing schedule that launches a new agent.
Source - Event triggersNo
All docs pages and the changelog were searched for webhook, issue, pull request, Slack and mention. Only timers and idle watches exist, and nothing outside Solo can start an agent by itself.
- Team collaborationNo
The docs say "Team licensing is centralized billing plus claim-link distribution.". Each teammate gets a normal license, and no shared sessions or workspaces are documented.
Source - API / CLI control YesSource
Pricing
Free forever with every feature, limited to 4 projects and 20 managed processes. Pro is $99/year (3 devices). Team seats from $99 down to $69 each by volume.
Platforms
Native Tauri desktop app for macOS, Windows and Linux; Solo CLI, MCP server and local HTTP API; WSL execution profiles on Windows.
Research notes
own_subscription rests on the site line 'Your binaries, credentials, and subscriptions stay yours.' Keys and sign-ins stay inside each harness; Solo has no key setting of its own. Solo says it has no remote-host or headless session management, so deployment is local only. The soloterm GitHub org hosts related packages (including a separate Laravel solo command) and a Nix flake, but no app source; the terms forbid reverse engineering, so github is null.