murmur ssh

Opens an SSH connection to a running agent’s VM. Use it to inspect the filesystem, watch logs, or attach directly to the agent’s live coding session.

Synopsis

murmur ssh [flags] <slug> [-- <command...>]

Everything after -- is executed as a command on the VM instead of opening an interactive shell. The command’s exit code becomes murmur ssh’s exit code. The connection goes through the murmur SSH proxy with the private key matching one of the ssh_public_keys recorded by murmur setup.

Arguments

Name	Type	Required	Description
`slug`	string	yes	The agent’s slug.
`--attach`	bool	no	Attach to the agent’s `claude` tmux session. Default: `false`.
`-v`	bool	no	Show SSH debug output. Default: `false`.
`--workspace`	string	no	Workspace name. Overrides the value from `murmur.yaml`.

Examples

Open an interactive shell

murmur ssh fix-auth

Opens a terminal on the agent’s VM. You land in a standard shell and can browse the cloned repo, read logs, or run commands.

Attach to the agent’s coding session

murmur ssh fix-auth --attach

Attaches to the claude tmux session where the agent is working. You see its live terminal output in real time. Detach with Ctrl-b d.

Run a single command

murmur ssh fix-auth -- git log --oneline -5

a1b2c3d Fix JWT expiry check
d4e5f6a Add token refresh test
7890abc Refactor auth middleware
bcd1234 Update go.mod
ef56789 Initial scaffold

Runs the command on the VM and exits. No interactive shell is opened.

Verbose output for debugging

murmur ssh fix-auth -v

Prints SSH connection diagnostics to stderr. Useful when a connection is hanging or failing.

Errors

Code	Meaning	What to do
`NOT_FOUND`	No agent with that slug exists, or it has no VM (`no VM found for <id>`).	Check the slug. Use `murmur ls` to list running agents.
`UNAUTHENTICATED`	Identity token is missing or expired.	Run `murmur login`.
`FAILED_PRECONDITION` (`SSH proxy is not configured`)	The server has no SSH proxy configured.	Contact your murmur administrator.
`SSH proxy rejected connection: <reason>`	The proxy refused the connection. `no tunnel for this agent` means the proxy has no connection to the agent’s VM.	If the agent is sleeping, run `murmur wake` first.
`ssh is not supported on VMs`	You ran `murmur ssh` from inside an agent VM.	Run this command from your laptop, not from a VM.
`no ssh_public_keys in local config — run 'murmur setup' to configure`	No SSH keys are recorded in `murmur.local.yaml`.	Run `murmur setup` to register your SSH public keys.
`no SSH key pairs found in ~/.ssh`	`~/.ssh` has no `.pub` file with a matching private key.	Generate one with `ssh-keygen -t ed25519` and re-run `murmur setup`.
`no local SSH key matches the VM's authorized keys`	None of your key pairs in `~/.ssh` matches a key recorded by `murmur setup`.	Run `murmur setup` to re-register your keys.

Agents: concept overview
murmur status: check an agent’s phase and progress
murmur port-forward: tunnel local ports to the agent’s VM
murmur ls: list running agents
murmur wake: restart a sleeping agent’s VM

Getting Started

Core Concepts

Guides

Synopsis

Arguments

Examples

Open an interactive shell

Attach to the agent’s coding session

Run a single command

Verbose output for debugging

Errors

​Synopsis

​Arguments

​Examples

​Open an interactive shell

​Attach to the agent’s coding session

​Run a single command

​Verbose output for debugging

​Errors

​Related

Synopsis

Arguments

Examples

Open an interactive shell

Attach to the agent’s coding session

Run a single command

Verbose output for debugging

Errors

Related