Reviewing changes

Every time the agent edits a file, the changes appear in the file changes panel inside the chat. You can review, accept, or reject edits — per file or all at once.

The file changes panel

The panel appears in the chat whenever there are pending edits. It shows:

• The number of changed files
• Total added and removed lines across all files
• A list of individual files with per-file line counts

Added and removed totals count semantic line changes, not line-ending conversions. The totals shown in the panel match the + and - counts in each edit accordion in chat.

Click the panel header to expand the file list. Click a file to open it in the editor — the cursor jumps to the first changed line automatically.

Diff viewer

Click the FileDiff icon button in the panel header to open all changed files in a multi-file diff viewer. This is useful for reviewing all edits before making a decision.

Inline change snippets in chat strip indentation that is common to every shown line. Deeply nested edits are easier to scan, while the actual file contents and relative indentation stay unchanged.

An approval is tied to the exact file version shown in its preview. If the file or its open working copy changes before you approve it, Kodik leaves the newer content untouched and asks the agent to read the file and produce a fresh preview. Simultaneous edits to the same file are applied in request order; edits to different files can still proceed together.

When a text file is already open and clean, Kodik applies an approved edit through that editor’s working copy and saves it as one undoable range change. If the editor has unsaved changes, Kodik refuses the agent edit before approval; save or revert your changes before asking the agent to retry. The unsaved buffer and its on-disk base are never overwritten.

The edit accordion in chat shows every added and removed line, including large rewrites. Long diffs start collapsed and cross the native-to-chat bridge as a small reference tied to the exact verified edit plan. When you open or scroll the accordion, chat requests only the visible ranges and keeps a bounded page cache, including the first and final ranges. The complete review remains available without copying one object per changed line into chat state, and the same version-checked ranges remain available after a window reload.

Kodik computes large line diffs in a bounded worker pool. A full rewrite with no common lines uses an exact linear path; other edits retain exact line ranges without running the matcher on the shared workbench renderer. If the worker cannot start, Kodik falls back to the exact in-process diff instead of leaving the edit and later tools waiting.

Large edits stay listed in File Changes but do not automatically open a heavy inline editor review. Click the file or use Review changes when you want to inspect it; Keep, Reject, Keep all, and Undo all remain available while it is closed.

Notebook edits use a full-file snapshot diff instead of placing inline review controls inside an individual cell. The Review pending changes prompt stays at the bottom of the notebook editor; select it to open that notebook in a separate Pending Changes diff tab. Keep and Undo actions remain available in the File Changes panel.

Keyboard shortcuts

When a changed file is open in the editor, the following shortcuts are available (when the editor has focus and the file review context is active):

Action	Shortcut
Go to next file	Alt+Right
Go to previous file	Alt+Left
Accept changes in file	Alt+A
Reject changes in file	Alt+R

Accepting and rejecting changes

Individual file:

• Hover over a file in the list — Accept (Check) and Reject (X) icon buttons appear.
• In the editor title bar, use the previous/next, Accept, and Reject actions; the same flow is available from the keyboard with Alt+A / Alt+R.

All changes at once:

• Keep all — accepts all edits and moves the baseline forward.
• Undo all — restores the workspace to the state before all current edits. Kodik handles this as one bulk review operation from both the panel button and Alt+U, so multi-file undo uses the same conflict checks in either path.

Note

Accepting or rejecting changes in the panel works together with checkpoints. Rejecting a file restores it to the state captured at the checkpoint. Accepting makes the edits the new baseline.

Reject is user-safe: Kodik preserves edits you made outside the AI-changed lines, including edits saved after restarting Kodik. If rejecting would delete a user-modified AI-created file, or overwrite a file you recreated after the AI deleted it, Kodik shows an error notification, refuses the reject, and keeps the pending review entry so you can resolve the conflict manually. If Keep, Keep all, Undo, Undo all, or Review cannot complete for any other reason, Kodik also shows the error instead of silently leaving the panel unchanged.

When a checkpoint restore rewinds only part of a task, the panel updates to the restored state: rows for rewound edits disappear, while earlier pending edits remain reviewable.

Worktree tasks

In Worktree mode, Keep, Keep all, Reject, and Undo all operate inside the task’s isolated worktree. They do not apply a patch to your main checkout, and they never remove the worktree — it stays on disk after the task ends, after Undo all, and even after you delete the chat. Use the Worktree badge in the composer to reveal the folder and bring the work back with normal Git workflows. The keep-limit is the only automatic cleanup: it removes the oldest worktrees once you go past the limit, so bring back anything you want to keep before it scrolls out (a worktree a running task is using is never removed).

Relationship to auto-approve

If auto-approve for file edits is enabled, edits are applied automatically without a prompt. The file changes panel still shows all edits, and you can always use Undo all or roll back via a checkpoint.