wsp vs Solo

Solo runs agents on the computer you sit at and no other. wsp runs them there and on Linux computers you own.

Solowsp
Runs agents onThe computer you sit atComputers you own
Another computerNoYes, over ssh or dialing out
What that computer has when the agent startsOne computer, nothing to carryYour setup, agents signed in
Where your keys and sign-ins liveYour computer, never through SoloYour computers, none on ours
Which agents8 built in, any CLIClaude Code, Codex, OpenCode, Cursor
PlatformsmacOS, WindowsmacOS, Linux
PriceFree for 4 projects, then $99/yrFree
Source codeClosedAGPL-3.0

Which to pick.

What Solo does well

Solo runs the agent CLIs already on your computer, eight built in and any other, beside your project's dev processes. Your API keys never pass through Solo, and it works on macOS and Windows.

When wsp fits better

wsp fits when you already have another computer, a server you rent or an old laptop, and want your agents on it signed in, with your MCP servers, CLIs and skills. Solo "does not currently provide remote-host or headless session management".

What wsp does not do yet.

Windows
Solo runs on Windows. wsp runs on macOS and Linux.
More agents
Solo has 8 agents built in and runs any other CLI. wsp runs threads on four.
Sources, read 2026-10-09

Try it on a computer you own.

Something here wrong or out of date? Open an issue with the page that says so.

Download for Macor for Linux