Skip to main content
Whenever Qoder makes code changes in Quest, you can review the full diff, decide what to keep or discard, and commit and push — all from the Review panel on the right.

​
Review panel overview

The Review panel is divided into three areas:
  • Top toolbar: scope switcher, global Stage All / Discard All actions, the commit button, and more.
  • File list: the changed files within the current scope, with list / file-tree view toggle and search.
  • Diff view: a line-level comparison for a single file, with per-file Stage / Discard actions.

​
Switch the view scope

A single dropdown at the top of the panel lets you choose the scope:
OptionMeaning
Current QuestAll changes accumulated in the current Quest
Last TurnChanges from the most recent turn
All UncommittedAll uncommitted changes in the workspace — every file with changes not yet committed in git status

​
Annotate code and diffs

If you spot something to adjust while reviewing, you can add annotations to specific parts of the code and diff views and hand that feedback straight to the agent. This helps it understand exactly what you want changed, without separately describing “which spot and how.” Adding an inline comment in the diff view

​
Stage and discard

Once you’ve reviewed the diff, you can Stage / Unstage / Discard right in the panel.
Stage / Unstage require the current directory to be a Git repository.
Global actions (buttons at the top of the panel)
  • Stage All: add every unstaged file in the current scope to the staging area.
  • Discard All: discard all uncommitted changes in the current scope — requires a second confirmation and cannot be undone.
Per-file actions (buttons on the right of each file row)
  • Unstaged files: show Stage and Discard.
  • Staged files: show Unstage and Discard.
Actions take effect on click. Staging or discarding partial (hunk-level) changes within a file is not yet supported.
External-change warning: In the Current Quest / Last Turn scopes, if a file has other changes made outside this conversation, a yellow ⚠️ marker appears next to the file name.

​
Commit and push

The Commit entry is available in every scope — you can commit the whole workspace from All Uncommitted, or commit from Current Quest / Last Turn to commit only the files in the current scope. The top action bar has an action button with a dropdown. It defaults to Commit and can switch to:
  • Push: push your local commits to the remote.
  • Create New Branch: create a new branch from the current changes and commit to it.
Clicking Commit opens the commit dialog:
  • You can manually control whether unstaged changes are included.
  • The commit message can be written by hand or generated automatically.