How to run coding agents on your own computer and in the cloud

Capy runs a thread either in a folder on your own computer, through the desktop app, or on an isolated cloud machine. You pick the place under Machine when you start the thread. A local thread uses your tools and credentials and has no machine-time charge. A cloud thread keeps working when your laptop sleeps. A thread moves between the two with its branch and uncommitted changes.
When to use each
| On your computer | On a cloud machine | |
|---|---|---|
| Where it works | A folder on your computer, in a new worktree, an existing one, or your current checkout | An isolated Linux VM with your repositories cloned |
| Tools and credentials | The ones you already have there, including local git credentials | What the project's environment and secrets provide |
| When your laptop sleeps | The thread waits, for up to 24 hours | The thread keeps working |
| Machine time | No charge | Bills Capy credits while the machine is awake |
| Model usage | Same as in the cloud | Same as on your computer |
Use your computer when the work needs something only it has: a local service, a signed-in tool, a large dataset, hardware. Use the cloud for long runs, for work in parallel, and for anything that should finish while you're away.
Run your first thread on your computer
- Install the desktop app from the download page and sign in with your capy.ai account. Your computer pairs with Capy as a device.
- Link your repository folder. Scan a folder finds clones that match the project's git remotes, so nothing is cloned again. You can change the links later in Project folders.
- Start a thread and open Machine. Pick This Mac, This PC or This computer.
- Pick the checkout. New worktree, the default, starts from the latest base branch on your remote and leaves your own branch alone. Existing worktree reuses one. Current checkout works in your folder as it is, with your current branch and changes.
- Send the message.
The agent works in that folder, and its edits land on your disk as it makes them. New worktrees live under ~/.capy/worktrees, and they need 1 GB of free disk space.
Follow it from anywhere
While the app runs and the computer is online, you can start, follow and reply to its threads from any browser, your phone's included. Linked Slack replies reach the computer too. Notification settings control alerts when a thread finishes or needs you.
To keep a thread running overnight on the computer, turn on Keep awake while agents are running for the device in Settings → Devices. On macOS, closing the window keeps the device online. On Windows it stays online only while Show in system tray is on, and on Linux while Show in menu bar is on.
Move a thread to the cloud and back
- Open the machine chip on the thread and choose Move to cloud or Move to another device. You can also ask: "move this to my MacBook".
- The current turn ends, and the agent continues on the new machine with a note about what moved. The conversation, subagents and pull requests stay with the thread.
These move with the thread: your branch and commits, including unpushed ones; staged, unstaged and untracked changes; and files in the workspace folder outside the repositories. These stay behind: files your .gitignore ignores, such as .env and node_modules; untracked files larger than 2 MB; anything outside the workspace folder; and running processes such as dev servers. A move never pushes to GitHub.
A move to the cloud needs the Capy GitHub App on each repository and credits for machine time. A move to a computer needs it online, with a linked folder for at least one of the thread's repositories. A repository it has no folder for is dropped, so that repository must have no uncommitted or unpushed work.
If something goes wrong
- The thread on your computer stopped when you closed the lid. It waits while the computer sleeps or is offline, for up to 24 hours, and continues when the computer reconnects. Capy keeps a cloud checkpoint of your uncommitted work, so the agent can move an offline thread to the cloud when that unblocks it. Device settings turn the checkpoint and the automatic move on or off.
- The move was refused. A repository is in the middle of a merge, rebase, cherry-pick, revert or bisect. Finish or abort it, then move again. A move off a cloud machine is also refused while other threads are working on that machine.
- The cloud machine can't build the project. Something on your computer isn't in the project's setup. Add it to the environment, and use secrets for values your
.envheld. - The move to your computer asks for a folder. The computer has no linked folder for the thread's repositories. Link one you have, or clone it from the dialog.
Limits
- A thread on your computer doesn't run while the computer sleeps, unless it moves to the cloud.
- Running processes don't move. Start the dev server again after a move.
- The desktop app needs a desktop session. To run threads on a server without one, use the Dock CLI.
- Moves between two computers go through the cloud.
For what keeps a cloud thread going with nobody watching, see Keeping coding agents working after you close your laptop. The desktop docs cover installation on each operating system.
Follow-up questions
Which operating systems does the desktop app support?
macOS on Apple Silicon and Intel, Windows on x64, and Linux on x64 and arm64. Threads on Windows need Git for Windows, and a thread offers to install it.
Can a teammate run threads on my computer?
Only if you let them. The device's Access in Settings → Devices sets who can run threads on it.
Can a Captain run on my computer?
Yes. Choose the computer under Machine in the New Captain dialog. The Captain's Crew runs on setting then decides whether its crew threads run in the cloud or on one paired device.
Does a thread on my computer cost anything?
It has no machine-time charge. Model usage costs the same as in the cloud, unless the model runs on a subscription or key you connected.




