Task Commands
Task commands list and manage the agent's work through its task namespace: background commands, subagents and schedules.
List its tasks
/task:list lists running and scheduled work through
the agent's task namespace. The command needs that namespace's grant
and [commands] tasks = true. It shares the same provider approvals
and combined results as task__list. /task:list --agents lists the
subagents alone, each with its conversation, task-<id>.
Words for the common cases
The task namespace's commands take their route's JSON, or words for the common cases, each read into the requests its providers already take. Each needs the namespace's grant.
Stop its work
/task:stop --all stops the agent's work in this chat: each background
command, subagent and schedule /task:list lists, and the answer being
written. /task:stop tasks, agents or schedules stops one kind. A
subagent already under way has its turn stopped too. It answers with
what stopped, and what didn't and why. /chat:stop, or /stop, ends
the answer alone.
Send a message every so often
/task:schedule 10m check the build sends the agent check the build
every ten minutes in this chat, and its answers come here. The interval
is minutes that divide an hour, hours that divide a day, or 1d for each
midnight, in the agent's time zone. Its alias is /loop, and its JSON
takes at, in or any cron.
Start a subagent
/task:agent {"task": "find three sources"} starts a subagent, as the
agent's task__agent does. It runs on the model the JSON names, a
model or an alias, else on this conversation's.