qst_. For why agents ask and how the run waits, see Approvals and questions.
States
A system close sets
answer.text to [system:<reason>] and leaves answeredBy null. For a secret_input question, answer stays null.
Answer modes
A thread reply stores your reply as
answer.text with selected null. It works for every mode except secret_input.
Fields
string
required
Question id,
qst_….string
required
Always
question.string
required
Workspace the question belongs to.
string
Linked task,
tsk_…. Null when the ask named no task.string
Conversation the answer shows in,
cnv_…. Null when there is none.string
required
Run that asked,
run_….string
required
Session that asked.
string
required
open or resolved.string
required
The question text, in Markdown, with secrets redacted.
string
required
free_text, single_select, multi_select or secret_input.object[]
Choices for select modes. Null for
free_text and secret_input.object
What a
secret_input question asks for. Null for other modes.object
required
Who asked.
type is agent with an agt_… id, or system.object
The answer. Null while
open.object
The answering person,
{ "type": "user", "id": "usr_…" }. Null while open or after a system close.string
Answer time. Null while
open.string
required
Creation time.
string
required
Last change time.
GET /api/v1/questions/{id} also accepts include[] with task, run, session or conversation to embed those objects.
CLI
The CLI asks only
free_text and secret_input questions.
API
Errors
An agent that calls the secret route gets 403
http_exception. For shared codes, see API errors.
Limits
- A list returns 25 questions by default and 100 at most.
secretRequest.reasonholds 1 to 2,000 characters.- A secret value holds 1 to 10,000 characters.
Approvals and questions
Why agents ask, and how the run waits.
Answer approvals
Answer from the inbox, the task or the terminal.
Approval
The yes or no gate, for comparison.
Secret
What a
secret_input answer creates.