Local runtimes

Local runtimes are an advanced execution destination. They run on a member's computer, keep their Task workdir there, and appear under Settings → Computers. The Cloud sandbox remains the default destination. Switching a Task to a local runtime is explicit: pick the computer in the Run on menu next to the CLI menu, then pick one of the CLIs installed on it; an offline computer does not cause a Run to move to Cloud.

Connect a computer

1. Install the Melso CLI and sign in with melso login on the computer that will run Tasks.
2. Run melso worker local setup. It installs pinned Codex, Claude, and Pi packages and Pi MCP support under your Melso profile. Node.js and npm are required. Run setup again after updating the Melso CLI to bring the local packages to the pins shipped with that release.
3. Run melso worker local start in a terminal or your own process supervisor. Leave it running while you want the computer to accept Runs.

The worker installs new Melso releases by itself. It waits until no Run is active, updates, and restarts with the same arguments; a running Run is never interrupted. Pass --no-auto-update or set MELSO_NO_AUTO_UPDATE=1 to update manually with melso update instead.

The start command verifies the supported CLIs, registers each available harness, and reports heartbeats. It uses your saved Melso CLI login for the control connection. The Task's child process receives a Run-scoped mrt_ Melso credential, the selected provider credential, and configured Task environment values. The login token is not copied into the Task workdir.

Accounts and credits

A local Run uses the same AI access as a Cloud Run: the executing member's connected Codex or Claude account from Settings → AI providers, their API key, or Melso credits. Pi always uses Melso credits. The credential is delivered for that Run only and removed when it ends. The computer's own codex, claude, or pi logins (~/.codex, ~/.claude, ~/.pi) are never used, so you do not need to sign in to those CLIs on the computer. If no connected account or credit route can run the Task, the Run fails before it starts and names the setting to change.

Share with a teammate

In Settings → Computers, the computer owner can grant or remove access for each workspace member. Granting access allows that teammate's Task code to execute on the owner's computer. Their provider account and repository access are selected under their own Run authority, so a teammate's Runs spend the teammate's accounts or credits, not the owner's. The owner can inspect the computer's local files and processes, so only share with members you trust. Removing access prevents new claims; a Run already in progress may finish.

Only online, approved computers appear in the Run on menu. The owner can always select their own computer. The Settings list still shows offline computers so the owner can identify what needs restarting.

Troubleshooting

• Computer offline: Restart melso worker local start. Check that the CLI login is still valid and the network can reach Melso.
• Approval needed: Ask the computer owner to grant access in Settings.
• No connected account: Connect a Codex or Claude account, or turn on Melso credits, in Settings → AI providers, then retry. Signing in to the CLI on the computer does not help.
• CLI missing or outdated: Run melso worker local setup again. The worker does not install packages during a Run.
• Task stays queued: Keep the selected computer online; a local Task is never moved to Cloud automatically. Choose Sandbox or another computer for the next Run if needed.