Agents
Interview
Answer a project's interview once and every agent turn in that project reads the rules it produces first.
The interview is how you tell agents how a project works: what it is and who it’s for, which tests a change needs, how a change reaches the main branch, what an agent may do without asking, the rules no linter checks, its user interfaces, and the project’s own words. You answer a list of questions, an agent asks about whatever is still unclear, then it writes the interview memory. Every agent turn in the project reads that memory before anything else.
Open Interview under the project in the sidebar. The page has two tabs, Questions and Memory. On Questions the sources sit beside the questions on a wide window and under them on a narrow one. The line above the tabs shows the latest run and holds Regenerate and Audit via AI, whichever tab is open.
The page follows the Memories and interview area in the role editor: someone without Read there doesn’t see Interview in the sidebar, and answering or adding sources takes Create and update.
Answer the questions
-
Work down the questions. Each one opens on its own with any options to pick, and a recommended option already picked. Next saves your answer, Skip saves a skip. Click any earlier question to change it.
The bar above the questions has a segment per question, and the line under it counts what’s answered, what’s skipped, and what needs you. Need you counts every question with no answer yet and every draft or suggested change waiting on you; click it to open the first one.
-
Once every question is answered or skipped, press Done.
-
The agent reads your answers and the code, then asks only what it can’t read for itself: a skipped question the code doesn’t settle, a gap that changes how work is done, or an answer the code contradicts. It never asks an answered question again. Its follow-ups appear on the page a round at a time, up to four in a round and two rounds in a run, each with a recommended answer and a line on why it’s asked. Answer them the same way.
-
When nothing is left to ask, or after its second round, the agent writes the memory, on the Memory tab.
The run happens on your paired computer, like any play. The line above the tabs shows where it is: Agent working, Agent asking, Memory ready, Memory out of date, or Run failed. While the agent asks, Answer beside it opens the question.
The agent writes a rule only when you gave or confirmed it, and writes rules, not a transcript of your answers. The one rule it takes from the code is how a change reaches the main branch, when you skip that question. An agent may do without asking only what you tick under What may an agent do without asking a person?: skip it, or leave a box empty, and agents ask first, merging their own pull requests included.
Change it later
Change any answer, including a follow-up, and the line above the tabs reads Memory out of date with a count of the answers changed since the memory was written. Press Regenerate the memory to run it again; the agent changes only what your changed answers change and keeps every other rule. You can also edit the memory by hand like any memory.
The memory is capped at 8,000 characters, so keep it to rules. Deleting it keeps your answers, ready to write it again.
Point it at sources
If the rules already exist somewhere, add them as sources instead of typing them in. Press + in the Sources header beside the questions. A source is one of:
- a Path, a file or folder in the project’s checkout, such as
docs/standards.md; - a Doc or a Memory in the workspace;
- another Project;
- Text you paste, up to 32,000 characters. Dropping a text or markdown file onto the form pastes it for you.
Give each a stance:
- Follow means the team stands behind it. Drafting reads it to propose answers.
- Question means it shows how something was done, not how it should be, such as a predecessor’s code. The follow-up run asks you about it and never drafts from it.
Sources are listed in two groups, Follow and Question, each row with the number of drafts that cite it. Hover a row, or tab to it, for its buttons: move it to the other group, remove it, and for pasted text edit its label and text in place. With the sources beside the questions, hovering a source lights the questions whose drafts cite it, and hovering a draft’s source lights the source.
A project holds up to 50 sources. A source is read where it lives, never copied in.
Draft answers from sources
With at least one follow source, press Draft answers. The agent drafts an answer for each unanswered or skipped question a source speaks to, and names where it came from.
- A drafted question carries an amber dot and reads Drafted from 2 sources. It opens with the draft picked and a chip per source: a doc, memory or project opens where it lives, pasted text opens in a popover, and a path shows itself in full. Keep draft confirms it; change anything and the button reads Next.
- A draft on a question you already answered shows as a suggested change: your answer under Now, then what accepting would add (+) or drop (−). Accept makes it your answer, Dismiss throws it away.
A draft is never an answer until you confirm it. The button carries a dot when a source was added or changed since the last drafting run.
Audit code against it
Once the memory exists, Audit via AI checks code against it: your sources under question, such as a predecessor’s code, or the project’s own checkout when there are none. The agent writes a doc in the project’s Main folder, titled “Audit of
Each run writes a new audit. Run To tickets via AI on it to turn the findings into work.
Change the questions
The questions come from the workspace’s interview template, in Configuration → Interview template. It’s markdown: a ## heading per question, text under it as a hint, - bullets for single-choice options and - [ ] bullets for multi-select ones. A question with no bullets takes free text.
Until you edit it, the workspace follows the instance’s template, and the card says Instance template; once the workspace saves its own it says Edited here, and Reset to instance template beside it goes back. Editing the template never changes a memory already written. Saving or resetting it takes Edit the workspace Interview template (memories:template), a workspace permission in the role editor, which also shows the template in Configuration; anyone in a project reads it there.
When there is no interview
The project wizard offers the interview on its last step. Skip it and the project’s board shows a banner with Run the interview until the memory exists. Agents still work without it, just without the project’s rules.