> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # List the questions waiting on a person > The questions the agent has asked and nobody has answered yet — the recovery road for a client that was not attached when `question-asked` went out. It is the road `listPermissions` already is for the other kind of ask, and it exists for the same reason: a question is durable state on the host and the event announcing it is long past by the time a client attaches, which reads the transcript and then subscribes after the position that read returned. A question is not a transcript entry, so a client with no retained event cursor has nothing else to reconstruct it from. ONLY PENDING QUESTIONS, and there is no status filter. An answered question is retired by `tool-call-finished` for the call it was blocking, and the decision audit never carries a question, so the only thing there is to list is what somebody still has to answer. ## OpenAPI ````yaml /pt/openapi/v3-current/narya.yaml get /v1/questions openapi: 3.1.0 info: title: Narya Host API version: 1.0.0 description: >- The contract between the Narya host and every client. One long-lived host serves this API over a Unix socket in your Narya home. The terminal client and the one-shot command that Lerian ships drive this API, and a client you write drives the same one. Requests authenticate with a bearer token issued by the identity provider the host is configured with. An operation that declares another security scheme also accepts that credential. A request without a valid credential gets 401 with NRY-0011. A caller whose role lacks the permission an operation needs gets 403 with NRY-0028. Submitting a message returns 202 with a turn id. Everything the turn produces streams over GET /v1/events as server-sent events with a typed envelope, and a stream resumes from a Last-Event-ID header. One error envelope: code, title and message. Codes are NRY- followed by four digits. Cursors are opaque. servers: [] security: - bearerAuth: [] tags: - name: host description: The host process itself — version, uptime, mode, store. - name: sessions description: Durable conversation containers. Archive, never destroy. - name: messages description: Submitting work into a session and interrupting it. - name: events description: The server-sent event stream every client consumes. - name: lanes description: Parallel tracks inside a session — main, subagent, side. - name: agents description: Named recipes — instructions, tools, model, policy. Read-only in v1. - name: ladder description: >- What a person can type: the skills and command files in force for one repository, and expanding one into text. Five origins merged, nearest winning a name, the repository's own rungs gated on trust. - name: permissions description: Pending permission asks, decisions, and the decision audit. - name: intercom description: Sessions on one machine finding and messaging each other. - name: packages description: The one thing a user installs — resources, Go code, or both. - name: extensions description: >- Host-side extensions and the operations each exposes over the wire. This is the generic lane a host extension uses to serve its own client half (a TUI component, a web panel) or any API-only consumer, without adding routes to this contract. - name: workflows description: Deterministic multi-agent orchestration runs. - name: providers description: Model suppliers, their auth state, and the model catalogue. - name: monitors description: >- Long-running watchers a session keeps beside its conversation — a test runner in watch mode, a build, a log being followed. Started by the model or by the person, always listed, always killable. - name: records description: The queryable local record of everything that happened. - name: environments description: >- Where a session's code lives and its commands run — this machine, or a container narya operates. A session that names none runs here. - name: schedules description: >- Work the host's own clock starts with nobody present — a repository, a prompt, a rule and what one fire may spend. Cancel, never destroy. - name: sharing description: >- Publishing a session from a developer's own home to the organisation's, and what is held back before a byte leaves the machine. - name: refinements description: >- What this owner has taught narya and allowed it to keep — distilled facts, and the skills, agents and commands the model wrote for itself. Propose, read, consent, roll back. Nothing here fires until a person answers. - name: platform description: >- Calls Lerian's control plane made to a home it hosts, as this home recorded them. paths: /v1/questions: get: tags: - permissions summary: List the questions waiting on a person description: >- The questions the agent has asked and nobody has answered yet — the recovery road for a client that was not attached when `question-asked` went out. It is the road `listPermissions` already is for the other kind of ask, and it exists for the same reason: a question is durable state on the host and the event announcing it is long past by the time a client attaches, which reads the transcript and then subscribes after the position that read returned. A question is not a transcript entry, so a client with no retained event cursor has nothing else to reconstruct it from. ONLY PENDING QUESTIONS, and there is no status filter. An answered question is retired by `tool-call-finished` for the call it was blocking, and the decision audit never carries a question, so the only thing there is to list is what somebody still has to answer. operationId: listQuestions parameters: - $ref: '#/components/parameters/CursorParam' - $ref: '#/components/parameters/LimitParam' - name: sessionId in: query required: false description: >- Filter to the questions standing on one conversation, which is what a client attaching to a session asks for. schema: type: string format: uuid responses: '200': description: One page of questions waiting on an answer. content: application/json: schema: $ref: '#/components/schemas/QuestionPage' '400': $ref: '#/components/responses/BadRequest' '500': $ref: '#/components/responses/InternalServerError' components: parameters: CursorParam: name: cursor in: query required: false description: >- Opaque pagination cursor from a previous page's nextCursor or prevCursor. schema: type: string maxLength: 1024 LimitParam: name: limit in: query required: false description: Maximum items per page. schema: type: integer minimum: 1 maximum: 100 default: 25 schemas: QuestionPage: type: object description: One page of questions waiting on a person. required: - items - limit properties: items: type: array items: $ref: '#/components/schemas/PendingQuestion' limit: type: integer minimum: 1 nextCursor: type: string examples: - items: - questionId: 4c2e9a71-5b3d-4e8f-9a1c-6d0b2f4e8a3c sessionId: 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d toolCallId: call_01 questions: - question: Where should the export land? options: - value: A new table recommended: true askedAt: '2026-09-12T12:02:00.000Z' limit: 25 PendingQuestion: type: object description: >- One question standing on a conversation with nobody having answered it — the same ask `question-asked` announced, read back by a client that was not there to hear it. It carries what the announcement carries, so a client draws a recovered question through the code path the live event already goes through, plus the two facts an event envelope supplied and a listing row has to say for itself: which conversation it is standing on, and when it was asked. required: - questionId - sessionId - questions - askedAt properties: questionId: type: string format: uuid description: >- The question's id, which is what an answer is posted against (`POST /v1/questions/{questionId}/answer`). sessionId: type: string format: uuid laneId: type: string format: uuid description: The lane whose work raised the question, when not the main lane. toolCallId: type: string description: >- The tool call this question is blocking — the same id `question-asked` carries, and the JOIN a client retires the prompt on: there is no question-decided event, so the box goes down when `tool-call-finished` names this call, whoever answered it and from which client. Absent only for a question no tool call raised, which is not the ordinary road. questions: type: array description: >- The questions, in the order they were asked and with their options already ordered. An answer is matched to its question by position, exactly as on the event. items: $ref: '#/components/schemas/Question' askedAt: type: string format: date-time examples: - questionId: 4c2e9a71-5b3d-4e8f-9a1c-6d0b2f4e8a3c sessionId: 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d toolCallId: call_01 questions: - header: Storage question: Where should the export land? options: - value: A new table recommended: true - value: Something else other: true askedAt: '2026-09-12T12:02:00.000Z' Error: type: object description: >- The single error envelope every operation returns. Codes are NRY- followed by four digits and are catalogued in the top-level x-error-catalog extension. required: - code - title - message properties: code: type: string pattern: ^NRY-[0-9]{4}$ description: Machine-readable error code from the NRY catalogue. title: type: string maxLength: 256 description: Short human-readable summary of the error class. message: type: string maxLength: 4096 description: Specific, actionable description of what went wrong. fields: type: object description: Per-field validation problems. additionalProperties: type: string examples: - code: NRY-0002 title: Session not found message: >- No session with id 6b9f6d2e-1c3a-4f5b-9d7e-2a8c4e6f0b1d exists on this host. Question: type: object description: >- One question the agent is putting to the person. Up to four ride in one call, and the answer names which option index was chosen rather than repeating its label, so the model can tell a pick from a typed sentence. required: - question - options properties: header: type: string description: A short chip naming what this question is about. question: type: string description: The question itself. multiple: type: boolean description: >- More than one option may be chosen. Absent or false is a single choice, and a client draws checkboxes only when this says so. options: type: array description: >- The options in the order they must be drawn — recommended first, free-text row last, both placed by the engine. Two to four options the model wrote, plus that row. items: $ref: '#/components/schemas/QuestionOption' QuestionOption: type: object description: >- One answer a person may pick. `recommended` is a FIELD rather than a convention: the alternative is the model typing "(recommended)" into a label, which puts narya's own vocabulary inside text the model authored and leaves a client parsing for it. required: - value properties: value: type: string description: The option as the person reads it. recommended: type: boolean description: >- The agent's own preference. The engine has already moved the recommended option to the front of the list, so a client drawing the options in the order it received them draws them right — and a client must never reorder, because the indices it sends back are the engine's. preview: type: string description: >- What this option would mean, at length, for the side-by-side pane a client draws beside the option list. Absent when the option speaks for itself. other: type: boolean description: >- The free-text row, which the ENGINE adds to every question and the model never writes. A client draws it as the row that takes typing; an answer naming its index is an answer somebody typed, and the typed text rides the same answer's `text`. responses: BadRequest: description: Malformed request — invalid parameter, cursor, or JSON body. content: application/json: schema: $ref: '#/components/schemas/Error' InternalServerError: description: The host failed — including a store that refuses writes (NRY-0012). content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- Enforced on every transport, with no exempt operation. A person's request — over the default local unix socket exactly as over a TCP listener — must carry a JWT issued by the configured identity provider, which the host verifies itself against that issuer's key set: signature, issuer, expiry, and the person and organisation it names. Requests without a valid one receive 401 NRY-0011. The socket's file permissions are transport and are not an authorisation. ````