Update task

What "done" means for this task; null to clear it.

Long-form write-up as HTML

No "wont_do" and no "done" here on purpose — closing a task, or deciding it isn't worth doing, is a human call. Use propose_completion (or complete_task on an agent_ok task) to finish work; comment or call ask_decision if you think it shouldn't be done.

The goal (North Star) this task is an action step toward; null to unfile it.

YYYY-MM-DD, the day work is meant to begin; null to clear it. With due_date it is the task's span on the human's Gantt chart.

Local wall-clock time on due_date, 24-hour "HH:MM"; null for no particular time.

true = hard deadline (must finish on/before due_date); false = soft, a suggested date

true = parked, waiting on someone else. A parked task stays on the board under "Waiting" but leaves the human's calendar feed, Plan my day and Today until its resurface_date arrives (or indefinitely, with none) — so it stops being time-blocked into every day while the ball is in someone else's court.

YYYY-MM-DD. The day a parked (waiting) task comes back onto the human's calendar and into Today; null to park it with no return date. Only meaningful alongside waiting=true.

1–5 rating of how much this moves the needle; null to clear

Optional payout/value; null to clear

URLs/paths for context; replaces the existing list

Structured outputs you produced — {label, url, kind, content}; replaces the existing list. Put a document you wrote in content so it can be read and approved in place, and set kind when it is html or a base64 pdf rather than markdown.

What this deliverable holds. Omit for markdown, which is the default and the right answer for a draft, summary, report or plan. Use "html" only for a page you actually generated as HTML — it is rendered in a locked-down sandbox that cannot run scripts or reach the network, so a page that depends on either will look wrong. Use "pdf" with base64 in content for a small PDF, or with artifact_id for a large one. Use "binary" for anything else you uploaded — a screenshot, a spreadsheet, a zip — which is always an artifact_id and has no inline form.

The document itself, so a human can read it without leaving Done. Markdown or HTML as text, capped at 10,000 characters each (40,000 across the task). A pdf goes here as base64, capped at 800,000 base64 characters (about 600 kB, and 1,200,000 across the task). Put anything larger behind a url rather than truncating it.

An artifact you uploaded, instead of inline content (the two are mutually exclusive). Upload first: call create_artifact_upload with {task_id, label, filename, kind, size_bytes}, then PUT the raw bytes to the one-time upload_url it returns — no Authorization header, the link itself is the credential, and it expires 15 minutes after you request it. Use the artifact_id it returned here. To revise the document later, call create_artifact_upload again with the SAME artifact_id — this pointer keeps working and starts resolving to the new file as soon as its bytes land. Done keeps only that latest file: the previous one is queued for deletion once the replacement is safely stored, so don't rely on being able to fetch an earlier upload back.

What the downloaded file should be called. Ignored for the text kinds, and sanitised before use — the extension comes from an allow-list, not from you.