task Power

Manage personal todos, agent work, inbox items, and schedules

task captures work, runs agents, and schedules recurring occurrences in one task model. TaskPower owns domain behavior without a renderer. The Desktop app provides native Inbox, Todo, and Calendar; agents can create and handle the same tasks from chat.

Task identity

Each task has a stable task_id. Titles are editable and may repeat. create returns the ID; list includes IDs and workflow properties. Prefer IDs for subsequent operations.

Existing actions use a selector named title. Pass a stable task ID or a unique title. Ambiguous titles fail explicitly.

Actions

Action	Purpose
`create`	Create personal, agent, or script work.
`list`	List the current agent's execution tasks and personal todos.
`update`	Edit the title, instructions, or schedule.
`run`	Start agent/script execution; optionally retry a recurring `occurrence_id`.
`history` / `run_detail`	Read execution records and deliverables.
`inbox`	Read unorganized work and unresolved items without resolving them.
`work`	Organize, start, complete, reopen, accept, request changes, or handle a specific item.
`status` / `enable` / `disable`	Control scheduling independently of work completion.
`delete`	Delete work and its history; active executions prevent deletion.

Create a personal todo:

{ "title": "Prepare Friday's demo", "kind": "self" }

Create scheduled agent work:

{
  "title": "Daily report",
  "kind": "agent",
  "when": "0 9 * * *",
  "description": "Summarize daily progress",
  "body": "Read project records and deliver progress, blockers, and next steps. The final reply must be the report body itself."
}

Accept a result using the task and original Inbox item IDs:

{ "task_id": "task_example", "command": "accept", "item_id": "review:example" }

Accept only after explicit user confirmation. Agents should not approve their own deliverables.

Work and execution

Personal work (kind=self) needs no Agent or Workspace. Scheduled personal work creates a reminder. Agent/script work uses its configured execution targets. One-time agent work awaits human acceptance; recurring work completes each successful occurrence by default, with optional per-occurrence acceptance in task details.

when supports @manual, time:<ISO datetime with timezone>, and Cron. Due dates do not trigger execution. Each recurring occurrence has an independent completion record.

Automatic scheduling requires a running City. Missed one-time plans appear in Inbox; missed offline recurring triggers are not replayed. Approvals and follow-up questions remain in their original execution Sessions. Active tasks cannot yet be edited or cancelled.

Agent work created in chat can return results to its original Session. Changing execution targets does not change that delivery destination. Tasks created without a Session retain results in execution history. Explicitly instruct the executing agent to use Messenger when external delivery is required.

Read Task Power for workspace and scheduling guidance.