Practical guide

Give Codex a workspace you can return to.

Murmello runs Codex in a cloud workspace with its own project disk. Stop compute when you finish and return to the retained files later, within your plan’s retention window.

Updated September 28, 2026 · By Tomas Godoy Pastore

What you need

Install Murmello on an Apple silicon Mac running macOS 14 or later. Sign in to Murmello and have your own Codex access ready. Murmello’s cloud allowance and your agent provider’s usage limits are separate.

1. Start a Codex workspace

murmello cloud --codex

Run this in a local Murmello terminal, or choose Codex from Cloud → New pod. The workspace sets up the agent on first use. Complete sign-in inside the workspace; your account’s agent setup is shared with your other workspaces.

2. Add your code

Clone your Git repository in the cloud, or send a local repository from a second local tab using murmello push <id>. Find the ID with murmello ls. Push requires an existing commit and branch, carries uncommitted edits and asks which extra files to send.

The project opens under ~/pods/<name>. Keep project files there for workspace-specific storage. Files elsewhere in your home are shared across your account’s workspaces.

3. Run a task and check the result

Ask Codex for a specific change with an explicit test or build command. Review the result and commit the work you want to keep. Use the cloud terminal to inspect Git status and test output.

4. Choose whether to detach or stop

Still working?

Use Return in the Cloud panel to detach. The workspace keeps running and consuming cloud time, subject to credits, idle stopping and execution limits.

Finished for now?

From a local terminal, run murmello stop <id>. This ends processes and keeps the project disk for your plan’s resume window.

5. Resume in the same project

murmello resume <id>

If the workspace stopped, this starts it again. Run codex from the project directory and use the agent’s saved history if you want to continue a conversation. Resuming storage does not resume an in-memory process.

After the resume window, a workspace is archived, then eventually deleted. Check murmello ls <id> for its dates and the pricing page for plan limits. Restore before deletion; keep a separate copy of important work.

6. Fetch commits back to your Mac

While the workspace is running, use murmello fetch <id> from your local repository. It fetches committed work and offers a fast-forward when possible. Uncommitted cloud files are not included.

When this setup fits

Use it when you want a Linux coding environment that is independent of laptop sleep and retains project files between sessions. Tasks that need macOS frameworks, Xcode or direct access to your Mac’s hardware still need a suitable Mac environment.

Next: setup and command reference · the Claude Code workflow.