murmur agent get - Murmur

Reads the persisted agent record through the dedicated GetAgent RPC. Use murmur agent status for live workflow state.

Synopsis

murmur agent get [--workspace name] [agent]

Arguments

Name	Type	Required	Description
`agent`	string	on laptop	Relative slug or absolute `/w/{workspace}/{owner_provider}/{account}/{slug}` path. On a VM, omission means self and a relative slug names a child.
`--workspace`	string	no	Workspace name. Overrides the configured workspace for relative targets.

Both login paths such as /w/backend/github_oauth/alice/fix-auth and subject paths such as /w/backend/github/7/fix-auth resolve to the agent’s exact recorded key. The server reads and authorizes its stored record and ancestors. Do not derive a catalog storage name from the reference.

Examples

murmur agent get /w/backend/github/7/fix-auth
# On a VM: read your own record.
murmur agent get
# On a VM: read a child you are authorized to access.
murmur agent get tests

Output is always JSON; there is no --json flag. The response has an agent document and a generation (a JSON string for the protobuf int64). The returned agent.agentId may use a historical workflow spelling, even when the request uses the owner’s current login or subject.

Errors

Code	Meaning	What to do
`NOT_FOUND`	The exact agent key or its stored record is missing.	Verify the target; a missing key does not trigger an alternate-address lookup.
`PERMISSION_DENIED`	The caller cannot read the selected agent or workspace.	Use an authorized identity or request access.
`INVALID_ARGUMENT`	The agent reference is malformed or incomplete.	Check the workspace and agent path.

agent_get: equivalent MCP tool
murmur agent status: live status
murmur agent session download: download a current or historical session
murmur tag add: edit tags through the dedicated agent operation