> ## Documentation Index
> Fetch the complete documentation index at: https://docs.murmur.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# murmur resume

> Move a running Murmur agent's session onto your laptop — reconstruct its workspace locally and continue the conversation interactively in Claude Code.

Brings an [agent's](/concepts/agents) session down from its VM to your machine and continues it in Claude Code. `murmur resume` rebuilds the agent's workspace under `~/.murmur/workspaces/` — every repo the agent had, checked out on the agent's working branch — downloads the agent's session, registers the [Murmur MCP server](/mcp-server/overview) for that workspace, and launches `claude` resumed into the session from the workspace root. You pick up exactly where the agent left off, with its full conversation and the same files in the same layout.

Claude Code must be installed (`npm install -g @anthropic-ai/claude-code`). Use [`murmur ssh`](/cli/ssh) instead when you want to work on the VM itself rather than locally.

## Synopsis

```bash theme={null}
murmur resume [flags] <slug>
murmur resume --clean [<slug>]
```

The first form resumes the agent locally. The second tears the local workspace down again — for one slug, or for every resumed workspace when no slug is given.

## Arguments

| Name          | Type   | Required               | Description                                                                                                                                                                                                                                                                                                                                |
| ------------- | ------ | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `slug`        | string | yes (unless `--clean`) | The [agent](/concepts/agents) to resume. Accepts the same relative and absolute slug forms as [`murmur status`](/cli/status), so `/w/<workspace>/<owner_provider>/<account>/<slug>` (e.g. `/w/backend/github_oauth/alice/fix-auth`) works for any agent. With `--clean`, the slug is optional — omit it to remove every resumed workspace. |
| `--clean`     | bool   | no                     | Tear down the slug's local workspace (all resumed workspaces when no slug is given) instead of resuming. Worktrees are removed through git, so the source clones keep no stale registrations; a checkout with uncommitted changes prompts before deletion. Default: `false`.                                                               |
| `--workspace` | string | no                     | [Workspace](/concepts/workspaces) name. Overrides the value in `murmur.yaml`.                                                                                                                                                                                                                                                              |

## What resume does

Resuming an agent runs these steps:

1. **Reconstructs the workspace** under `~/.murmur/workspaces/`, keyed by the agent's identity. Every repo in the agent's [workspace](/concepts/workspaces) is checked out on the agent's working branch — as a git worktree of a nearby local clone when one exists, or a fresh clone otherwise — and pulled.
2. **Downloads the agent's session**, refreshed from the live agent when it is reachable. The download runs in parallel with the repo checkouts.
3. **Registers the [Murmur MCP server](/mcp-server/overview)** for the workspace directory, so `murmur` CLI calls and MCP tools work from inside the resumed session.
4. **Launches `claude`** resumed into the session, from the workspace root — the same working directory the agent had on its VM, so paths in the session keep resolving. A short notice is injected as the session's next message telling the agent its environment moved.

Every step before the launch is best-effort and per repo: a single repo that fails to materialize is reported on stderr and resume continues. If the session cannot be downloaded, resume starts a fresh Claude Code session in the reconstructed workspace instead.

## Examples

### Resume an agent locally

```bash theme={null}
murmur resume fix-auth
```

```
Resolving workspace repos…
Downloading session…
Workspace: /home/you/.murmur/workspaces/github_oauth/acme-dev/w/default/fix-auth/
Launching claude in /home/you/.murmur/workspaces/github_oauth/acme-dev/w/default/fix-auth/
```

Claude Code opens with the agent's full conversation and its repos checked out on the agent's branch.

### Resume an agent in another account

```bash theme={null}
murmur resume /w/backend/github_oauth/acme-dev/fix-auth
```

### Tear down one resumed workspace

```bash theme={null}
murmur resume --clean fix-auth
```

Removes the local workspace for `fix-auth`. A checkout with uncommitted changes prompts before deletion.

### Tear down every resumed workspace

```bash theme={null}
murmur resume --clean
```

## Errors

| Code                    | Meaning                                      | What to do                                              |
| ----------------------- | -------------------------------------------- | ------------------------------------------------------- |
| `claude not found`      | Claude Code is not on your `PATH`.           | Install it: `npm install -g @anthropic-ai/claude-code`. |
| `get working directory` | The current directory could not be resolved. | Run the command from a valid directory.                 |

<Note>
  Run `murmur resume` from inside a directory where `murmur` is configured (a checkout with a `.murmur/murmur.yaml` above it, or with `MURMUR_CONFIG` set). Resume points the resumed session's `murmur` configuration back at that directory, so the CLI and MCP tools keep working. If no configuration is found, resume still rebuilds the workspace and launches Claude Code — but `murmur` calls in the session will not work until you run [`murmur setup`](/cli/setup) there.
</Note>

## Related

* [`murmur ssh`](/cli/ssh) — connect to an interactive agent's VM instead of resuming locally
* [`murmur session download`](/cli/session-download) — download just the session file
* [`murmur spawn`](/cli/spawn) — start a new agent
* [`murmur status`](/cli/status) — check an agent's current state
* [Agents](/concepts/agents) — what agents are and how they work
* [MCP server](/mcp-server/overview) — the Murmur tools registered into the resumed session