Everything runs where it works best.
The agent and your files stay on your Mac. The heavy work runs on your Dev Box. LoadShift handles everything in between, so neither side notices the other is somewhere else.
On your MacOn your Dev BoxBetween them
Your agent
Keep the agent you use, with your own subscription. LoadShift changes where its commands run, nothing else.
- Claude Code, Codex and OpenCodeOn your Mac
- Start any of them with
loadshift claude,loadshift codexorloadshift opencode, with the same arguments you'd normally pass. - Every command goes to the machineBetween them
- npm, cargo, go, pytest, make, Docker: anything the agent runs in its shell runs on your Dev Box. Output streams straight back.
- git and gh stay homeOn your Mac
- Commits, pushes and pull requests run on your Mac, in your real repository, with your own keys and GitHub login.
- Reads and edits at full speedOn your Mac
- The agent reads, edits and searches your files where they are. Only commands make the trip.
Your files
Your project stays on your Mac. The Dev Box gets a synced copy, kept up to date before every command.
- The same path on both sidesBetween them
- A project at
/Users/you/code/appis at the same path on the machine, so stack traces and error messages point at real files. - Never a stale fileBetween them
- Each command waits for the agent's latest edits to arrive, and files the command writes come back to your Mac.
- Dependencies stay on the machineOn your Dev Box
node_modules,.venv,targetand other build folders are built on the Dev Box and never fill up your Mac.- One project or manyOn your Dev Box
- Start your agent in any project and it's synced the first time.
loadshift forgetstops syncing one and deletes its copy.
Your apps
Run the whole stack on the machine and use it from your Mac as if it were local.
- Ports forward themselvesBetween them
- Start a dev server on port 3000 and
localhost:3000on your Mac reaches it within about two seconds. When it stops, the forward goes away. - Docker without Docker DesktopOn your Dev Box
- Containers, Compose files and databases run on your Dev Box, not in a VM eating your Mac's memory.
- Survives sleep and bad Wi-FiBetween them
- Close the lid or change networks and everything reconnects on its own. File access waits for the connection rather than failing.
Your Dev Box
A real Linux machine that's made, sized and looked after for you.
- Made for you the first timeOn your Dev Box
- The first
loadshift claudecreates your Dev Box and connects to it. No images, regions or instance sizes to choose. - Up to 32 vCPUs and 64 GBOn your Dev Box
- Every core and all the memory are there whenever a command needs them. Idle cores and memory go back to the server, so you only pay for use.
- Ubuntu 24.04, ready to workOn your Dev Box
- git, Docker, build tools and ripgrep are already installed, on a 200 GB NVMe disk. Install anything else with apt, like any server.
- Sleeps when you leaveOn your Dev Box
- Disconnect and your Dev Box goes to sleep with everything in place: processes, files, containers. Your next command wakes it.
- Plain SSH when you want itBetween them
loadshift sshopens a shell, and the machine is in your SSH config for VS Code Remote-SSH or any other tool.
Security
Designed so the machine holds as little of yours as possible.
- Your Claude account never passes through usOn your Mac
- The agent talks to its provider directly from your Mac. The Dev Box only receives the commands it runs.
- No history, no credentialsOn your Dev Box
.gitis never copied, so the machine has no repository history and none of your keys or tokens.- A VM of its ownOn your Dev Box
- Each Dev Box is a full virtual machine with its own kernel and limits, on an isolated network that can't reach other machines.
- Only your keys, nothing exposedBetween them
- SSH accepts only your keys, with host keys pinned. Sync and forwarded ports travel inside that connection; nothing else is open to the internet.
Teams and automation
Bring the team, and script anything the dashboard does.
- Shared workspacesBetween them
- Invite people, give them admin or member roles, and see usage for every machine. Machines stay personal: only the owner can log in.
- API and TypeScript SDKBetween them
- Everything the dashboard and CLI do goes through a small HTTP API, with tokens you create in the dashboard.
Want the details? How it works explains each piece, and Security covers isolation, access and what we can see.
Read the quickstartTry it on your own project.
Install, sign in and run
loadshift claude. Your Dev Box is ready in a minute or two.$20 a month. Cancel any time.