Tasks
Tasks are durable structured records for work you want Anyy to track. They are separate from chat messages, persistent memory, and scheduled automations.
Create a Task
Ask naturally and include the fields that matter:
Create a high-priority task to renew the test certificate by 2026-11-20T10:00:00+08:00. Label it infrastructure.
A task requires a title. It can also have a description, priority, due time, labels, and metadata.
| Field | Values or limits |
|---|---|
| Priority | low, normal, high, urgent |
| Status | pending, in_progress, blocked, completed, cancelled |
| Due time | RFC 3339 date-time with an explicit timezone |
| Title | Up to 240 characters |
| Description | Up to 4,000 characters |
| Labels | Up to 20 labels; each up to 48 characters |
List and Search
Examples:
Show my urgent open tasks due before Friday.
Find tasks labeled travel that mention passport, including completed tasks.
Anyy can filter by status, priority, due-before/due-after time, text query, and labels. The default list includes pending, in_progress, and blocked tasks. Ask to include completed tasks when needed; cancelled tasks require an explicit cancelled status filter. The default result limit is 20 and the maximum is 50. Labels are normalized to lowercase and duplicates are removed.
Update a Task
Use the task title when it is unambiguous, or include the task ID returned by Anyy:
Mark task TASK_ID as blocked and change its priority to urgent.
Updates can change title, description, status, priority, due time, labels, and metadata. Anyy requires at least one patch field. Ask to clear the due time or replace the label list when removing those values.
Complete a Task
Complete task TASK_ID with the note: renewed and verified in staging.
Completion stores a completed status and can include a short note. Ask Anyy to list completed tasks when you need the history.
Tasks, executions, and jobs
A task is a saved obligation, identified by a task ID. It does not start an agent run, schedule a reminder, or complete itself at its due time. A foreground execution is work Anyy is doing now; a background job is work running separately; a Cron job is a saved schedule with individual run records. Their IDs and statuses are separate.
Tasks vs. Automations
A task records an obligation. A Scheduled Automation causes Anyy to run at a time. If you need both, create the task for tracking and a separate schedule for the reminder or action.
“Renew staging certificate” is easier to scan and search than “Certificate.” Put supporting detail in the description.
Safety and Scope
Task mutations are audited. Tasks are resolved within the current runtime scope, so a Role or Workspace context can affect which records are visible and editable.