Task Power

Task Power brings personal todos, agent work, and recurring tasks into one workspace. Capture a thought first, then organize it, schedule it, complete it yourself, or delegate it to an agent.

Three entry points

• Inbox collects unorganized work, reminders, failed runs, missed one-time plans, and results awaiting acceptance. Opening an item does not resolve it.
• Todo shows unfinished work, unresolved recurring occurrences, and completed or cancelled history.
• Calendar shows plans and due dates in week and month views. Drag a one-time plan to change its date.

All entry points open the same task details. Titles are editable and may repeat; renaming a task preserves its execution history.

Capture and organize

Quick capture only requires a title and defaults to personal work. Adding from Inbox leaves the task unorganized; adding from Todo organizes it immediately. Add a goal, description, planned time, and due date when needed.

Selecting an agent or script reveals execution targets and instructions. Personal todos require no Agent or Workspace and do not produce agent runs.

Time and recurrence

Planned time and due date are separate. A due date never starts execution. An automatic trigger creates an Inbox reminder for personal work or starts execution for agent/script work.

Choose daily, weekly, monthly, or advanced Cron recurrence and an explicit timezone. Nonexistent monthly dates are skipped. Calendar expands fixed-time daily, weekly, and monthly rules; advanced Cron remains visible as a rule without a predicted calendar expansion.

Each recurring occurrence has its own completion record. Completing one occurrence does not end the recurring task. Pause future triggers, skip an occurrence, or end recurrence. Retrying a failed occurrence preserves its original identity.

Automatic triggers require the City to remain running. One-time plans missed by more than a minute appear in Inbox for immediate handling or rescheduling. Recurring triggers missed while offline are not replayed in a burst.

Execution and acceptance

Work status is Pending, In progress, Awaiting acceptance, Completed, or Cancelled. Schedule enabled/paused status is independent.

Successful one-time agent work awaits human acceptance. Review the output, accept it, or request changes. Requesting changes does not start another execution automatically: update the instructions, then explicitly run again.

Recurring agent work completes each successful occurrence when validation passes or is not configured. Enable per-occurrence acceptance to review every result in Inbox.

Execution failures and invalid results never complete work. Task details retain each run's input, output, status, and errors. Notification read state and Inbox resolution state are separate.

Current boundaries

Wait for an active execution to finish before editing, cancelling, or deleting its task. Approvals and follow-up questions remain in the original execution Session; they are not yet aggregated into Inbox. Skipping a recurring occurrence is supported; rescheduling an individual occurrence is not yet available.

TaskPower provides no UI. Tasks is a fixed Desktop app entry; its Inbox, Todo, Calendar, and details are native Desktop pages connected through dedicated task IPC. TaskPower stores definitions and execution history once at City scope. Damaged definitions appear as errors and stop scheduling; they can be deleted without blocking valid tasks.

Agent tasks created from chat can deliver their results back to the original Session. Changing execution targets does not move that delivery destination. Tasks created without a Session keep results in history. Explicitly ask the executing agent to use Messenger when external delivery is required.

Continue with Messenger Power and Agent Powers Docs.