Dunzo - Task Assistant

Archive a task to hide it from default task views.

When to use:

• User wants to hide a completed project they no longer need to see
• User wants to archive an old grocery/shopping list
• User says "archive this", "hide this list", "I don't need this anymore"
• Cleaning up old tasks without deleting them

Works on ALL task types:

• FINITE tasks: Archive completed or abandoned tasks
• PROJECT tasks: Archive completed projects
• ONGOING_LIST tasks: Archive lists no longer in use (e.g., old "Groceries" list)

Unlike mark_complete:

• Works on ONGOING_LIST tasks (lists cannot be "completed", only archived)
• Semantic: "archive" = hide from view, "complete" = finished

Archived tasks can be restored later (unarchive feature coming soon).

This is a GATED action - only call after explicit user confirmation.

IMPORTANT: The result is displayed in a visual widget. Do NOT repeat the task name in your text response - just give a brief acknowledgment like "Archived!" or "Done."

Add subtasks to an existing task. Call this AFTER create_task when breaking down work.

Use for:

• Breaking down a PROJECT into actionable steps ("Plan vacation" → "Book flights", "Reserve hotel", "Make itinerary")
• Adding items to an ONGOING_LIST ("Groceries" → "Milk", "Eggs", "Bread")

Rules:

• All subtasks are FINITE type (they can be completed individually)
• Cannot add subtasks to a subtask (only one level of nesting)
• Cannot add subtasks to a completed task (except ONGOING_LIST)

IMPORTANT: The added items are displayed in a visual widget above your response. Do NOT list the items in your text response - just confirm briefly like "Added!" or "Got it, I've added those items."

Create a new task. Use this for any user request to track, remember, or do something.

Task types:

• FINITE (default): One-time tasks with clear completion ("buy milk", "send email to John")
• PROJECT: Multi-step tasks needing planning ("plan vacation", "write quarterly report")
• ONGOING_LIST: Never-ending lists that persist ("groceries", "movies to watch", "gift ideas")

For simple capture ("remind me to X", "add X to my list"), just provide the title. All other fields have sensible defaults.

IMPORTANT: The created task is displayed in a visual widget above your response. Do NOT repeat the task details in your text response - just confirm briefly like "Created!" or "Got it, I've added that."

Get a single task by ID with its subtasks and summary.

Use this to:

• Get full details of a specific task
• See subtasks of a project or list
• Check current status before making updates

Returns the task with its subtasks (if any) and summary (if PROJECT).

IMPORTANT: Task details are displayed in a visual widget above your response. Do NOT repeat the task title, subtasks, or details in your text response - the user can already see them. Just acknowledge briefly.

Mark a task as completed (finished/done).

When to use:

• User says "done", "finished", "completed that", etc.
• The work is actually finished - semantic meaning is "I accomplished this"
• For FINITE tasks: can complete directly from PLANNED or IN_PROGRESS
• For PROJECT tasks: typically complete from IN_PROGRESS or READY_FOR_REVIEW

Complete vs Archive (important distinction):

• mark_complete: The task is DONE, work is finished (e.g., "I finished the report")
• archive_task: Hide from view, may not be done (e.g., "I don't need this list anymore")
• ONGOING_LIST tasks can ONLY be archived (they're never "done" - use archive_task instead)

Preconditions:

• Task must be FINITE or PROJECT (not ONGOING_LIST)
• Task must be in a status that allows completion

This is a GATED action - only call after explicit user confirmation for important tasks.

IMPORTANT: The completion result is displayed in a visual widget. Do NOT repeat the task name or details in your text response - just give a brief acknowledgment like "Done!" or "Marked as complete."

Reopen a completed task, setting its status back to IN_PROGRESS.

When to use:

• User wants to undo a completion ("actually, that's not done yet")
• User clicked on a completed checkbox to uncomplete it
• The work was marked done prematurely

This reverses a mark_complete action.

IMPORTANT: The reopened task is displayed in a visual widget. Do NOT repeat the task name in your text response - just give a brief acknowledgment like "Reopened!" or "Got it, marked as in progress again."

Show the user's tasks. This is the ONLY tool for viewing tasks.

REQUIRED: If the user mentions a specific list/project name, you MUST pass query with that name:

• "show my grocery list" → show_tasks({ query: "grocery" })
• "what's on my doco project" → show_tasks({ query: "doco" })
• "my movies to watch" → show_tasks({ query: "movies" })

Only omit query when showing ALL tasks:

• "show my tasks" → show_tasks({})
• "all my projects" → show_tasks({ taskType: "PROJECT" })

Other filters:

• "tasks due today" → show_tasks({ dueBefore: "2024-01-15T23:59:59Z" })
• "completed tasks" → show_tasks({ includeCompleted: true })
• "overdue tasks" → show_tasks({ overdue: true })

The query parameter enables instant subtask display. Results appear in a visual widget - just acknowledge briefly like "Here's your grocery list".

Intelligently reorder tasks based on natural language instructions.

When to use:

• User says "reorder my groceries by store section"
• User says "prioritize urgent items first"
• User says "sort my tasks by importance"
• User says "group similar items together"

How it works:

• Finds tasks by query (list/project name) OR parentTaskId OR uses provided taskIds
• Uses AI to determine the optimal order based on the instruction
• Updates the sort order so the new arrangement persists

REQUIRED: You must provide ONE of these to identify which tasks to reorder:

• query: The name of a list/project (e.g., "groceries", "shopping list")
• parentTaskId: ID of a parent task whose subtasks should be reordered
• taskIds: Direct list of task IDs to reorder

IMPORTANT: Confirm the reorder briefly like "Reordered your list!" - don't list all the items.

Update basic fields on a task like title or due date.

Use for:

• Changing a task title ("rename it to X")
• Setting or clearing due dates ("make it due Friday", "remove the deadline")

Cannot change: status (use mark_complete), task type.