murmur task update

Modifies an existing task on an agent’s checklist. Changes the task’s status, subject, description, or dependency edges. On success, prints the task ID.

Synopsis

murmur task update [flags] [slug] <task-id>

On a VM, omit the slug: the command always targets the current agent’s own checklist, and a slug is rejected as an extra positional argument. At least one change flag is required.

Arguments

Name	Type	Required	Description
`slug`	string	on laptop	The agent’s slug. Omit on VMs (always self).
`task-id`	string	yes	ID of the task to update.
`-s`	string	no	New status. One of: `pending`, `in_progress`, `completed`, `not_applicable`, `deleted`.
`--subject`	string	no	New subject line. Passing `--subject ""` clears it.
`-d`	string	no	New description. Passing `-d ""` clears it.
`--not-applicable-reason`	string	no	Why the task does not apply. Use with `-s not_applicable`.
`--blocks`	string	no	Comma-separated task IDs that this task blocks. Appended to existing edges.
`--blocked-by`	string	no	Comma-separated task IDs that block this task. Appended to existing edges.
`--workspace`	string	no	Workspace name. Overrides the value from `murmur.yaml`.

Task statuses

Status	Meaning
`pending`	Not yet started.
`in_progress`	Work is underway.
`completed`	Finished.
`not_applicable`	Does not apply. Record why with `--not-applicable-reason`.
`deleted`	Removed from the checklist.

Examples

Mark a task as completed

murmur task update fix-auth -s completed 1

Change a task’s subject

murmur task update fix-auth --subject "Add rate limiting to all auth endpoints" 1

Add dependency edges

Mark that 2 cannot start until 1 finishes:

murmur task update fix-auth --blocked-by 1 2

You can also express this from the other direction: mark that 1 blocks 2:

murmur task update fix-auth --blocks 2 1

Mark a task as not applicable

murmur task update fix-auth -s not_applicable --not-applicable-reason "Endpoint was removed" 1

Update multiple fields at once

murmur task update fix-auth -s in_progress -d "Started implementing IP-based throttle" 1

Self-update on a VM

When running on an agent VM, omit the slug:

murmur task update -s completed 1

Errors

Code	Meaning	What to do
`NOT_FOUND`	No agent with that slug exists, or the task ID is invalid.	Check the slug and task ID. Use `murmur task ls` to see existing tasks.
`UNAUTHENTICATED`	Identity token is missing or expired.	Run `murmur login` or check your `murmur.local.yaml` configuration.
none	`unknown task status "<value>"`	The `-s` value is not recognized. Use one of: `pending`, `in_progress`, `completed`, `not_applicable`, `deleted`.
none	`murmur task update names no change to task <id> — say what to change with ...`	No change flag was passed. Pass at least one of `-s`, `--subject`, `-d`, `--not-applicable-reason`, `--blocks`, or `--blocked-by`.

Agents: concept overview
murmur task create: add a task to an agent’s checklist
murmur task ls: list all tasks on an agent’s checklist
murmur task get: retrieve details for a single task
murmur status: query agent status

Getting Started

Core Concepts

Guides

murmur task update

Synopsis

Arguments

Task statuses

Examples

Mark a task as completed

Change a task’s subject

Add dependency edges

Mark a task as not applicable

Update multiple fields at once

Self-update on a VM

Errors

​Synopsis

​Arguments

​Task statuses

​Examples

​Mark a task as completed

​Change a task’s subject

​Add dependency edges

​Mark a task as not applicable

​Update multiple fields at once

​Self-update on a VM

​Errors

​Related

Synopsis

Arguments

Task statuses

Examples

Mark a task as completed

Change a task’s subject

Add dependency edges

Mark a task as not applicable

Update multiple fields at once

Self-update on a VM

Errors

Related