• AI reference · Always listed

tasks

See the board. Read only: tasks by department, status, skill, dates or words; or one task with its log, outputs and proposals (number alone).

Where it is

Always listed: call it by its name.

Does it need a yes?

Reads only: it changes nothing. Here: the board.

Inputs

InputTypeNeededAbout
numberintegernoAlone, without filters: one task whole. · 1 or more
departmentstringnoOnly this department, e.g. sales. · format `^[a-z0-9-]{1,40}$`
status"new" | "doing" | "needs_you" | "done" | "dropped"no
skillstringnoOnly this skill's tasks, e.g. follow-up. · format `^[a-z0-9][a-z0-9:._-]{0,59}$`
created_fromstringnoDays (2026-10-01), company time; both ends count.
created_tostringno
done_fromstringno
done_tostringno
textstringnoWords in the title or done_when. · 1 to 100 characters
limitintegernoHow many (at most 50, 20 if left out). · 1 to 50
offsetintegernoThe next_offset you got. · 0 to 100000
response_format"concise" | "detailed"noconcise (the default): the usual fields and ids. detailed: everything.
run_idstringnoThe run_id from start. Pass it on every call: it keeps your task held. · 1 to 100 characters

Example

{
  "name": "tasks",
  "arguments": {}
}

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.