• AI reference · Always listed

start

Start here. Call first, once a session; do its next_move first.

Where it is

Always listed: call it by its name.

Does it need a yes?

Reads only: it changes nothing. Here: the session's start bundle.

Inputs

InputTypeNeededAbout
departmentstringnoYour department's id, e.g. marketing.
taskintegernoA task number, to get its full start bundle. · 1 or more
asked_by_ownerbooleannofalse for a run nobody asked for in the chat. Then it takes only what Task pickup allows, and ends at once when there is nothing; left out, the owner asked.
requeststringnoThe owner's request in this chat, in one line. · 1 to 300 characters

Example

{
  "name": "start",
  "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.