Coding agents on every computer you own.

Run Claude Code, Codex and more on your Mac, an old laptop or a server you rent, all from one window. They can start each other on any of them.

Download for Macor for Linux
The wsp app: a coordinator thread on a MacBook Pro has handed its tickets to Claude Code and Codex threads on five computers, with its board of the night's landings in the slate beside it.

Threads run on the agents you already pay for.

  • Claude Code
  • Codex
  • OpenCode
  • Cursor

Your agents hand work to each other.

A Claude Code thread can start a Codex thread to review its branch, on your Mac or another computer, and read what it found when it's done. Those agents have the same tools, so they start threads too. Every one of them is in your sidebar.
claudecodexopencodeclaudeclaudecodexcursorcodexclaudeopencodecursorclaudecodexon your Macon hetzneron thinkpadright here

Add a computer. Your setup comes with it.

Point wsp at a Linux computer you can reach over SSH. You pick what comes along, and it joins your sidebar ready to work.
Coding agents, signed in
Claude Code, Codex, OpenCode and Cursor. Copy your key over or sign in fresh.
MCP servers
The servers your agents call, along with their sign-ins.
Command line tools
One click picks the ones your agents ran on your Mac.
Skills and plugins
Copied from your Mac, so a skill does the same job on both.
GitHub sign-in
Your Mac's token, or a new sign-in on the other computer.
Your repos
Cloned there with the name, icon and colour you gave each one.
Git and shell settings
Your git name and email, your prompt, tmux and the rest.

A computer behind a firewall can dial out to you instead, so nothing on it has to be open.

A mini app inside every thread.

Chat fills up with status updates, and a separate file means another window. Slate is a panel beside the thread that the agent builds and keeps current: checklists, live numbers, charts, forms and buttons. You press, it reads what you pressed.

Checks as they finish. A failed one goes back to the agent in one press.

A slate for pull request #212: its checks, a failed e2e run with Send to agent beside it, and Auto-merge.
A slate walking through a Vercel deploy setup, with a password field for a token the agent never sees.
A slate for a cart rounding fix: progress, an editable checklist, the files changed and a button to go on.
A slate of live redirect traffic: six numbers and a line chart of requests a minute.
A slate with a diagram of how a short link becomes a redirect.
It reaches what the agent reaches.
Your files, your command line tools and your MCP servers, on the computer the thread runs on.
It asks before it runs.
Every command a slate runs waits for your yes the first time.
Any agent can make one.
Claude Code, Codex and the rest write it with the same few tools.

Everything around the thread.

The panes and pages that make a dozen agents on six computers feel like one desk.

Your terminal, your config.

The terminal pane reads your Ghostty config, so the font, colours and transparency are yours. On your other computers too.

A thread with its terminal open in the colours from the person's Ghostty config, showing git log for the branch.

Open it in your editor.

VS Code, Cursor or Zed open the thread's folder, even when it's on another computer, over SSH.

The Open menu on a Codex thread that runs on gpu-box, offering VS Code, Cursor and Zed.

The pull request, beside the thread.

Checks, review and merge without a browser tab. A failed check goes back to the agent in one press.

Pull request #1161 beside the thread that built it: approved, eight checks passed, ready to merge, with its description.

All your agents in one place.

See which agents are signed in on which computer, and sign one in from the same pane.

The Agents pane: Claude Code and Codex signed in, and Gemini CLI, OpenCode, Pi, Hermes, Crush and more in the catalog.

A browser for the dev server.

The page the thread is building, open next to the thread that's building it.

The browser pane showing the site the thread is serving on localhost:5420, beside the thread.

How wsp compares.

Side by side with the apps and clouds people ask about.

Questions

Do I need API keys?
Not for most agents. Claude Code, Codex and Cursor use the subscriptions you're already signed in to. OpenCode uses a key from the model provider you pick.
Which agents does it run?
Claude Code, Codex, OpenCode and Cursor today. A thread can use any of them, and one thread can start another on a different one.
Which computers?
Your Mac, and any Linux computer you can reach over ssh or that can dial out to you: a server you rent, an old laptop, a desktop under the desk.
Does my code go through your servers?
Only if you turn on the relay. Threads run on your computers, and the app reaches them over your own network or SSH. If you link the relay to reach a computer from anywhere, that connection runs through Cloudflare, which can read it on the way. Running your own relay takes us out of it, but it still goes through Cloudflare. To keep Cloudflare out too, skip the relay and stay on your own network.
What does it cost?
Nothing. wsp is free and open source.

Put your other computers to work.

Download for Macor for Linux