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 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.

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. 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.
• 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.