`task_edit`

Change or reopen a task. Change a task without holding it: reopen a closed one (reopen: true), or change its title, done_when or due_on (null takes the due day off). A task another chat is working on right now is refused; a task the owner closed herself stays hers to reopen. The same change again changes nothing.

Where it is

In the records area (deleting a module record): open it with tools_for { area: "records" }, then call it with use_tool { name: "task_edit", args }.

Does it need a yes?

Runs at once, no yes card: it changes only the office's own working state, and nothing reaches anyone. Here: a task's title, done-when or due day, or reopening it; the board's own working state, logged on its trail.

Inputs

Input	Type	Needed	About
`number`	integer	yes	The task number, e.g. 12. · 1 or more
`title`	string	no	The new title. · 1 to 200 characters
`done_when`	string	no	How anyone can tell it is done. · 1 to 1,000 characters
`due_on`	string or null	no	The day it is due, in company time; null takes the due day off.
`reopen`	boolean	no	true: reopen a closed task first.
`run_id`	string	yes	The run_id from start. Pass it on every call: it keeps your task held. · 1 to 100 characters

Example

{
  "name": "task_edit",
  "arguments": {
    "number": 12,
    "run_id": "the run_id from start"
  }
}

When it is refused

invalid: The input isn't right. The sentence names the field and the fix; nothing was done. Fix it and call again.
not_found: No such thing in this company (a task, file, person, record). Check the number or name, or list first.
not_allowed: Not without another step: the owner's yes, your own task held with pick_up, or a setting the owner turns on. The sentence says which.
taken: Someone else holds it (another AI on that task). Pick another task.
stale: It changed since you read it. Read it again and use the new version.
failed: On our side or a service's, never your input. Try again in a minute; if it keeps failing, call report_problem.