Sessions and follow-ups
A session is one conversation about one repository and branch. It is made of turns. Each turn is your message plus one run of the agent, with its own budget, result and receipt.
Start a session
Click "New task" in the sidebar, pick the repository and branch, choose Ask or Code and send. The first message becomes the session's title.
When the session starts, the branch is resolved to a commit and the session stays pinned to it. Everything the agent does in this session starts from that commit plus the session's own earlier changes. To work on newer commits of the branch, start a new session.
A message can be up to 30,000 characters.
Follow-ups
Type in "Ask a follow-up or describe the next change…" once the previous turn has finished and been settled. Until then the note under the box says "Continue after the current turn has settled."
A follow-up turn:
- Starts from all changes the session has made so far, restored in a fresh sandbox.
- Sees your earlier requests and the agent's summaries from up to five previous turns.
- Has its own mode, model and budget, so you can switch between Ask and Code within a session.
- Gets a new execution environment. Commands from earlier turns are not replayed.
The diff in "Session details" is always the whole change from the pinned commit, not just the last turn.
The session list
The sidebar groups your sessions:
| Group | Sessions whose latest turn… |
|---|---|
| "Needs your attention" | failed, was cancelled, or is waiting for usage to be reconciled |
| "Running" | is queued or running |
| "Ready for review" | finished successfully |
The list shows only sessions you started. Administrators can also read everyone's sessions, see Organization sessions.
While a turn runs
The turn shows the phase it is in: "Fetch source", "Detect validation", "Execute", "Validation", "Collect artifacts". Before that it may wait for an execution environment ("Submitted; waiting for an execution environment."). If nothing is assigned after 5 minutes, the turn says so. You can keep waiting, or cancel the turn to release its budget.
"Tool steps" fills in as the agent works. Each step shows the command or file edit, its output and its exit code.
To stop a turn, open "Session details" and click "Cancel turn". The sandbox is shut down first, then the turn is settled. You pay for what was used up to that point, never more than the turn's budget.
Click "Enable completion notifications" to have the browser notify you when a turn ends. If the tab is in the background, its title changes to "Task complete · Yi Code".
After a turn
Each turn ends with the verification box and a receipt: "Turn cost", the budget and the pinned commit. "Session details" adds the session's total cost, the changes, "View diff" and "Raw logs and artifacts":
| File | What it holds |
|---|---|
changes.patch | The session's changes from the pinned commit, as a Git patch |
tests.txt | The verification result and reason, with the output of the run before and after the change |
report.md | The turn's outcome, failure reason if any, verification result, knowledge sources used and the agent's summary |
memory-draft.md | Changes the agent proposed to the project's memory, see Memory |
Archive and restore
When you're done, click "Archive session" in "Session details". Archived sessions leave the main list. Click "Archived" at the bottom of the list to see them, and "Back to recent sessions" to return.
Open an archived session and click "Restore session" to bring it back. Its turns, results and pull request are kept, and you can follow up again. A session with a running turn can't be archived. Cancel the turn or let it finish first.
If a submission is unconfirmed
Starting a turn holds money, so the browser keeps each submission until the server confirms it. If the connection drops at that moment, you see "Your previous submission is unconfirmed". Click "Check submission result" to look it up, or "Retry original submission" to send exactly the same request again. The server recognises a repeated submission and returns the original turn instead of starting a second one.
This needs the browser's session storage for the tab. If it is blocked, Yi Code won't submit: "Could not save submission recovery state. Allow browser storage for this tab, then try again."
Organization sessions
Owners and administrators can open "Settings" and click "Load organization sessions" to read every session in the organization. They can't continue or publish someone else's session. The page says "You are viewing an organization session. Only its author can continue or publish."