Skip to main content
Brings an agent’s 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 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 instead when you want to work on the VM itself rather than locally.

​
Synopsis

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

NameTypeRequiredDescription
slugstringyes (unless --clean)The agent to resume. Accepts the same relative and absolute slug forms as murmur status, so /w/<workspace>/u/<account>/<slug> works for any agent. With --clean, the slug is optional — omit it to remove every resumed workspace.
--cleanboolnoTear 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.
--workspacestringnoWorkspace 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 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 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

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

murmur resume /w/backend/u/acme-dev/fix-auth

​
Tear down one resumed workspace

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

murmur resume --clean

​
Errors

CodeMeaningWhat to do
claude not foundClaude Code is not on your PATH.Install it: npm install -g @anthropic-ai/claude-code.
get working directoryThe current directory could not be resolved.Run the command from a valid directory.
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 there.