Review & Pull Requests

Tarsk includes a built-in diff viewer and pull request creation flow, so you can review and ship the agent’s work without leaving the app.

Review Mode

Open the Review window from the chat dock Window launcher. The Review icon shows a dot when uncommitted changes exist and no Review window is open.

The Diff Viewer

Use the Monaco diff viewer to compare modified files side by side on desktop or inline on mobile. In the side-by-side view:

Left side — original (before changes)
Right side — modified (after the agent’s changes)

Additions are highlighted in green, deletions in red, and modified lines in both.

Navigating Files

A file list on the left side of the diff viewer shows all changed files with their change type:

Modified — file was changed
Added — new file created
Deleted — file was removed

Click any filename to jump to that file’s diff. The viewer also shows untracked files (new files not yet staged).

What to Look For

Use the diff viewer to:

Verify the agent made only the changes you intended
Catch unintended deletions or modifications
Review generated code before committing
Identify which files need manual follow-up

Reverting Individual Files

If a specific file has changes you want to undo, right-click the file in the list and choose Revert Change. Tarsk restores the file to its last committed state (HEAD). For untracked or newly created files, the file is deleted from disk. Other files in the diff are not affected.

Inline Comments

Click any line in the diff to add an inline comment. Comments are stored locally and appear as markers on commented lines. Use comments to note issues, questions, or requested changes before committing.

Fix Comments

When you have inline comments, click Fix all comments to send all comments to the AI agent. The agent reads your feedback and attempts to address each comment in a single follow-up run.

On mobile, the file tree can be toggled to maximize the diff panel. See General Settings for responsive layout details.

Creating a Pull Request

After reviewing and committing changes, create a pull request to merge the thread’s branch into your main branch.

Prerequisites

The gh CLI must be installed and authenticated. Install from cli.github.com and run gh auth login.
The project’s remote must be a GitHub repository.
Commit your changes before creating the PR. Tarsk pushes the branch during PR creation.

Steps

Commit your changes. You can push from the Git Ops dropdown first, or let Tarsk push during PR creation.
Click Create PR on the main Git Ops button, or Create Pull Request in the dropdown (when commit method is pull-request).
Tarsk sends the commit history and diff to the AI model and generates a PR title and PR description in Markdown.
Review and edit the title and description in the dialog.
Click Create PR.

The PR is created on GitHub via gh pr create. A link to the PR is shown so you can open it in your browser.

AI-Generated PR Description

The generated PR description typically includes:

A summary of what changed and why
A list of key changes grouped by file or feature area
Any notable implementation decisions or caveats

You can edit the generated content freely before creating the PR.

Pushing During PR Creation

Tarsk derives a branch name from the PR title and pushes it before calling gh pr create. It also updates the thread title to match the PR title. You do not need to confirm a separate Push Before PR dialog.

Pull Request vs Direct Commit

The project’s Commit Method controls whether the Git Ops dropdown offers PR creation. Committing saves changes on the current branch; pushing is a separate action or part of PR creation.

Setting	Behaviour
`pull-request`	Offers Create Pull Request when the branch has commits ahead of the default branch and no PR exists.
`direct`	Hides Create Pull Request in the dropdown.

Change this in Project Settings.

GitHub Status

For threads connected to a GitHub repository, Tarsk can detect:

Whether the remote is a GitHub repo
The repository URL
Whether a PR already exists for the current branch

This information drives the Git Ops button state and PR creation flow.

Merged Pull Requests

When a pull request for the current branch has been merged on GitHub, Tarsk detects this and can prompt you to sync or start fresh work on a new thread.