Claude on your laptop.Compute from the cloud.
LoadShift runs every command Claude Code starts on your Dev Box, an elastic Linux machine: builds, tests, Docker, dev servers. Your login, your editor and localhost work exactly as before.
$curl -fsSL https://app.loadshift.ai/install.sh | bash
Free during the beta. Needs Claude Code on a Mac.
~/code/shop $ loadshift claude> run the test suite and fix what fails● Bash(npm test) ⎿ running on Dev Box… ⎿ 1,284 passed in 41.2s
RUN v3.2.1 /Users/you/code/shop ✓ src/cart.test.ts (212) ✓ src/checkout.test.ts (388) ✓ src/search.test.ts (684) Tests 1,284 passed Time 41.2s
Save your battery.
Compiling, testing and running containers is where a laptop's power goes. All of it happens on your Dev Box, so your Mac only runs Claude and your editor.
Silence your fans.
Your Mac sits near idle while the whole test suite runs on your Dev Box. It stays cool and quiet on your lap, in a meeting or on a call.
Scale your impact.
Your Dev Box peaks at 64 vCPUs and 128 GB of memory when the work needs it, so Claude can run the suite, the database and the dev server at once while you keep working.
Claude stays put. The work moves.
One SSH connection carries everything between your Mac and your Dev Box. Here's what's on each side, and what travels.
On your Mac
Claude Code and your login
Your own subscription. Nothing about your Claude account touches our servers.
Your project and your editor
Files stay on your Mac, so Claude's edits and any editor work at full speed.
localhost in your browser
Open the port and the app is there, within about two seconds of its server starting.
git, gh and your credentials
Commits and pushes use your own keys and GitHub login, in your real repository.
On your Dev Box
Every command Claude runs
npm, cargo, go, pytest, make: anything that goes through Bash. Output streams straight back.
A synced copy at the same path
Same absolute path, so stack traces line up. Each command waits for Claude's latest edits.
Dev servers, Docker, databases
Containers run on your Dev Box, not in a VM on your Mac.
No history, no secrets
Your Dev Box never gets .git, so it holds no repository history and no credentials.
Big when the tests run. Nearly nothing in between.
Your Dev Box always sees all of its cores and memory. While Claude is thinking, they sit idle and the memory goes back to the server. When the suite starts, it gets everything up to its ceiling, on large dedicated servers where every Dev Box gets a fair share.
- Used this half hour
- 2.25CPU hours
- An always-on 64 vCPU VM
- 32CPU hours
In between, while you read and Claude thinks, the Dev Box idles at about 0.1 vCPU and 2 GB of memory.
Set up in about two minutes
Run these in Terminal on your Mac. You'll need Claude Code installed and signed in already.
The quickstart covers the same steps in more detail.
Install the loadshift command
A few small shell scripts in ~/.loadshift. No admin rights needed.
$curl -fsSL https://app.loadshift.ai/install.sh | bashSign in from the terminal
Your browser opens with a code to confirm.
$loadshift loginStart your agent in a project
The first time, LoadShift sets up your machine and connects to it: nothing to create, no password. Then it syncs the project and starts the agent.
$cd ~/code/your-app$loadshift claude
Does this change my Claude subscription?
What does Claude notice?
Does my repository go to the Dev Box?
.git is never copied, so your Dev Box has no repository history and no credentials. git and gh run on your Mac with your own login.What happens to node_modules?
node_modules, .venv and target are built on your Dev Box and stay there. They never fill up your Mac.What if my Wi-Fi drops?
Who can reach my Dev Box?
Free while we're in beta.
One Dev Box per person, peaking at 64 vCPUs and 128 GB of memory. See pricing for what comes after.
$curl -fsSL https://app.loadshift.ai/install.sh | bash