Orchestrate coding agents across computers and clouds.
Get started · Documentation · Cloud providers · Architecture · Releases
Run Claude Code, Codex, OpenCode and Cursor with the tools and subscriptions you already use. Give each part of the work its own thread, on your computer, another computer or the cloud. Follow it from the first message to the reviewed result.
## Get started
```sh
curl -fsSL https://usewsp.com/install | sh
```
Open WSP, add a project, and start a thread with an agent you're signed in to.
**[Setup guide](https://usewsp.com/docs) · [Download the desktop app](https://github.com/wsp-labs/wsp/releases)**
### Cloud providers
Cloud execution currently requires a cloud-enabled build.
When work needs its own compute, launch a cloud child from your setup image. It starts from your pushed code on an independent branch. WSP manages capacity, spending limits and cleanup; the report and result come back for review.
![]() Boat Available now |
![]() Instabox Coming soon |
![]() Daytona Coming soon |
![]() Celesto Coming soon |
![]() Freestyle Coming soon |
![]() E2B Coming soon |
![]() Superserve Coming soon |
![]() Maritime Coming soon |
The daemon shares one process sampler between subscribers. It starts when needed, stops after the last subscriber leaves, and sends changes after the initial snapshot. Linux thread cgroups keep builds and dev servers attributed to their work after the original shell exits.
Closing a client, ending an agent turn and releasing cloud compute are separate events. The host keeps the record of the work across them.