Ask about your work
Open Ask in the app header. Ask why a ticket is waiting, what happened while you were away, or how to configure your workflow. An attached ticket gives the conversation context; clear that attachment to ask about other work.
Follow the sources in an answer to inspect the plan, status or test results. If the answer is missing context, ask a follow-up rather than treating it as a complete record.
Request an action
Describe the change you want to make: start a ticket, queue one behind another, archive a landed ticket or grant more attempts. Nothing runs until you confirm the proposed action; several commands arrive as one list with a single Run button. The attendant continues after confirmed commands.
A request is not proof that an action ran. Look for the recorded result. If delivery is uncertain or a command fails, inspect the current ticket state before retrying.
Choose the model
Open Settings, then Attendant, to choose an available model and reasoning effort from Codex or Claude Code. If Ask is unavailable, read the message above the composer, check your repository connection, and confirm that the coding tool is signed in.
Workflow presets use Sol for Codex and Opus for Claude Code. Workflow stage choices and the Ask model can be customized separately.
Decisions while you are away
Plan approval and question settings determine which decisions wait for you. The background attendant can make decisions only within its saved policy and attempt allowances.
When the available facts or model cannot support a decision, the question stays for you. Extra attempts are finite, and they do not repair a failing base or change the request.
Review landed work
Landed tickets stay available until you archive them. Open the ticket to inspect its result and recorded information, then archive it when you are finished reviewing. Archiving is your action, not an automatic attendant cleanup.