Fix Sessions

Fix Sessions let VibeRails automatically apply code changes to resolve approved issues. The AI generates patches for each issue, applies them to your working tree, and pauses for your intervention when it encounters ambiguity or conflicts.

Fix Table Overview

The Fix Sessions screen lists all fix sessions for the active project. Each row shows the session name, the number of issues included, how many have been fixed, the current status, and the AI model used.

Fix sessions table showing sessions with issue counts and status — The fix sessions table provides a high-level view of all automated fix operations.

Sessions can be in the following states:

Queued — waiting to start.
Running — the AI is actively generating and applying patches.
Intervention — the session is paused and needs your input.
Complete — all issues in the session have been processed.
Failed — the session encountered an unrecoverable error.

Creating a Fix Session

There are two ways to start a fix session:

From the Issues table — select one or more approved issues and click Send to Fix in the batch toolbar.
From the Fix Sessions screen — click New Fix Session to open the creation wizard.

The wizard guides you through two steps:

Select Issues — choose which approved issues to include. Issues are pre-filtered to show only those with "approved" triage status.
Configure — select the AI model, enable or disable auto-commit, and set intervention preferences.

Animated walkthrough of creating a new fix session — Creating a fix session from the wizard.

Tip: Enable Auto-commit to have VibeRails create a git commit for each successfully applied fix. This makes it easy to review and revert individual changes.

Intervention System

Not every fix can be applied automatically. When the AI model is uncertain about a fix, encounters a merge conflict, or identifies a change that could have unintended side effects, the session pauses and enters the Intervention state.

An intervention banner appears at the top of the session detail view, explaining why the session paused and what your options are:

Accept Fix — apply the AI's suggested change and continue.
Edit Fix — open the suggested patch in an editor so you can modify it before applying.
Skip Issue — skip this issue and continue with the remaining fixes.
Abort Session — stop the fix session entirely.

Animated demo of handling an intervention during a fix session — Handling an intervention: review the suggested fix, edit if needed, then continue.

Warning: Always review intervention fixes carefully. The AI paused because it was not confident in the change — applying without review could introduce new issues.

Progress Tracking

While a fix session is running, a progress bar shows how many issues have been processed. The bar is divided into segments:

Green — successfully applied fixes.
Yellow — fixes that required intervention.
Red — fixes that failed or were skipped.
Grey — remaining issues not yet processed.

Below the progress bar, a live log shows each fix as it is applied, including the file modified, the issue addressed, and whether the change was auto-applied or required intervention.

Tip: After a fix session completes, use git diff or your editor's diff view to review all changes before pushing. If auto-commit was enabled, each fix is a separate commit that can be cherry-picked or reverted independently.

Reviewing Results

Once a session is complete, click into it to see a detailed breakdown of every fix:

Which issues were fixed, skipped, or failed.
The diff for each applied patch.
Any intervention notes you provided during the session.
Git commit hashes if auto-commit was enabled.

You can re-run failed fixes by selecting them and creating a new fix session, or manually apply them using the suggested patches from the Fix tab in Triage Mode.