Practical guide

Keep Claude Code working when your Mac is closed.

Start Claude Code in a Murmello cloud workspace before you leave. The task runs on a remote computer, so laptop sleep does not interrupt it. This does not move an already-running local task.

Updated September 28, 2026 · By Tomas Godoy Pastore

Before you start

You need an Apple silicon Mac with macOS 14 or later, Murmello, a signed-in Murmello account with cloud time, and your own Claude Code access. Check pricing and storage retention before leaving a long task.

1. Open Claude Code remotely

In a local Murmello terminal, run:

murmello cloud --claude

Or select Cloud → New pod → Claude Code. Wait for the workspace to connect, then follow the agent’s sign-in instructions. This is a separate Linux environment; Mac-only tools and paths will need alternatives.

2. Give it the project and a bounded task

From another local tab in your repository, run murmello ls and then murmello push <id>, using the ID of the workspace you just created. Push needs at least one commit and refuses a destination that already has repository branches. Alternatively, clone your repository inside the workspace.

Give Claude Code a clear task and a verification command. For example:

Fix the failing parser tests. Run the parser test suite, explain the changes, and leave the result for my review.

Resolve any sign-in or permission prompts before leaving. A remote agent can still pause when it needs your answer.

3. Leave it running

Close your laptop, or use Return in Murmello’s Cloud panel to detach. If you are at a shell prompt inside the workspace, murmello return also detaches. Do not use Stop when you want computation to continue.

The workspace consumes cloud time while it runs. Idle workspaces stop after 30 minutes, and credit exhaustion, execution time limits or service interruptions can also stop work. A closed laptop is not a promise of unlimited runtime.

4. Reconnect and review

Back in a local terminal, replace <id> with your workspace ID:

murmello resume <id>

If it is still running, reconnect to the task. If it stopped, restart claude in the project directory and use its saved conversation history as needed. Files persist within your retention window; running process state does not survive Stop.

5. Bring the result home

Review and commit the intended changes inside the workspace. From the local repository on your Mac, run murmello fetch <id>. Review the fetched commits and run your project’s tests before accepting the changes.

When finished, run murmello stop <id> from your Mac to stop compute. Keep your own copy of important commits before the workspace’s retention deadline.

Preview of the Murmello product tour — Watch the thirty-second product tour.

Next: the full setup and transfer guide · where your code and credentials live.