Answering agents

An agent that lacks a fact it cannot find in the repository stops and asks you. The run waits, and the item lands in the inbox of everyone in the project who may run pipelines.

What a question carries

• What the agent found
• The question
• The files it cites: each opens rendered in a panel beside the page
• Up to four suggested answers

Only some steps may ask: enrich and plan, and test-results about a test you failed (Pipeline steps). Every other step decides alone and records what it decided.

Answering

Open the question in the Inbox or on its ticket.

To	Press
Pick a suggestion	1 to 4
Write your own answer	R
Send	⌘↵

You can pick a suggestion and add context to it. On a phone, tapping a suggestion answers at once.

The same step continues where it stopped, in the same session, on the runner that asked. No attempt is spent.

The limit

A step may ask a limited number of times: 3 by default, at most 20, set per step. A question past the limit is not asked: the run blocks, naming the step and its limit, and waits for you to resume it.

While a ticket waits on an answer in enrich or plan, it does not hold its project’s slot: other tickets go ahead.

Putting it aside

On an inbox card:

Action	Does
Snooze	Hides it for 1 hour, 3 hours or until tomorrow. On a phone, swipe right
Mark done	Hides it (E). On a phone, swipe left

Both hide the item for you only: the question stays open for everyone else. Snoozed & done lists what you put aside and brings an item back.

From Telegram

With notifications on, a question reaches you with a button per suggestion. Tap one to answer, or Write my own answer and reply to the message the bot sends. A loose message is never taken as an answer.

Once a question is answered, from anywhere, its message is edited to say who answered, and loses its buttons.