murmur task create in the CLI.
Parameters
Conditional activation
Whenactivate_when is set, the task starts in a dormant state and is automatically activated when the condition is met. The only supported condition is files_modified: the task activates once a push in the current run changes a file matching pattern. It is evaluated against the branch’s net changes against its base branch. Files brought in by merging or syncing the base branch don’t count, and neither does what CI runs. While dormant, the task does not block the agent from finishing. Once activated, the agent must resolve it.
files_modified is run-scoped. A completed task resets to pending at the start of each new run and must be completed again if that run again modifies matching files.
This is useful for attaching review or testing tasks that only make sense after specific files change. For example, a task to “run integration tests” that activates when **/*_test.go files are modified.
Response
Returns a JSON object with the created task’s ID.Examples
Create a simple task
Create a task on another agent
Create a conditionally activated task
Errors
Related
murmur task create: equivalent CLI commandtask_update: update a task’s status or dependenciestask_list: list all taskstask_get: get a single taskspawn: create an agent with initial tasks via thetasksparameter