Reviewing agent work

Read the whole turn

A turn can include the reply, tool calls, the files the agent read and changed, task updates, and token usage. Expand the details that support the result. A claim that a test passed should be backed by tool output or a check you can repeat.

Under the reply, Koyd lists the memories it recalled and the sources from knowledge it used, numbered to match the reply's citations, and the tokens the turn used, including delegated agents. Knowledge bases explains citations, and Working with agents explains token usage.

Changes from a turn

A turn that changed files shows a card with each file, its status (A, M, D, or R), and its added and removed lines. Select a file to read its diff inline, or use Open the full diff for a larger view. Files the turn only read are listed separately. While the turn runs, the card shows the changes so far, then Finalizing while Koyd works out the final set.

Review all changes from this turn opens Turn changes, where you can search the files and read each diff. Once the turn has finished, Discard this turn's change restores one file to how it was before the turn, and Discard all changes from this turn does the same for every file in the turn. Both ask you to confirm.

Good to know · Discarding restores the file to its state before that turn, so later edits to the file are lost too, including your own. If other work touched the same files, check their current contents first.

Review every turn in a session

1. Select the changed-files summary above the composer, such as 4 files changed in this session, to open Session changes.
2. Use Search changed files to filter by filename or path. Matching files stay grouped by turn, with the prompt and change totals for context. Filtering does not change the totals.
3. Select a file to inspect its diff. A turn that is still running appears as Live, with its changes so far.

Discard file changes restores the selected file to before its selected turn, after confirmation. It is unavailable while file changes are running or when the saved baseline is missing. Read the confirmation before applying it.

Good to know · Discarding also removes later edits to that file, including your own work, and cannot be undone. A rename restores both paths. This action changes the current checkout; it does not remove only one agent’s contribution.

Read a diff

Diffs highlight the code's syntax on every line, with removed lines marked − and added lines marked +. The larger diff views switch between Unified and Split, which shows the old and new code side by side. Binary files and changes without text show a short note instead of lines.

Review the checkout

Git operations run on the server with its repository and Git configuration. The Changes panel (Ctrl+G, or Cmd+G on a Mac) groups files as Staged, Changes, and Untracked. Select files to stage, unstage, or discard them, write a commit message or generate one with AI, then commit, push, or pull.

In a shared checkout, the diff can include work from several sessions and from your own edits. Select only the files that belong in the commit.

Organize commits

To turn a set of changes into several commits, select the files in the Changes panel and use Split changes into logical commits with AI. Split into logical commits shows the suggested groups. Edit the messages, move files between groups, add a New group, or regenerate a message with AI. Then commit one group at a time or choose Commit all. Nothing is committed until you choose, and files left ungrouped are not committed.

Workflows can do this for a run: the Commit changes step splits the run's changes into commits, on its own or after you review the groups, and the Change map step maps what the run changed, with the diff of each element. See Workflows.

Read and export results

View → Markdown opens the project's Markdown files and marks the ones this session touched. You can download a file as a PDF. Downloads copy files from the server to the device you are using; check exports for keys or private data before you share them.

Verify the outcome

• Run the checks relevant to the changed behavior.
• Inspect failures, warnings, and untested assumptions.
• Use independent review for important changes.
• Review external side effects before retrying an interrupted operation.