Automated agent repairs

For findings that require semantic edits or refactoring, raigal agent runs an iterative repair session with a local coding tool inside an isolated git worktree.

How worktree repairs work

To protect your active working branch from unverified edits, raigal agent isolates all changes:

Raigal creates an ephemeral git worktree at .raigal/worktrees/agent-<timestamp>-<pid>/, automatically registered in .git/info/exclude to prevent polluting git status.
The agent provider (Claude Code, OpenCode, or Codex) receives diagnostic output, file context, and target score expectations in its prompt.
The provider makes edits and verifies changes inside the worktree.
After reviewing the diff, you can run raigal agent apply <session-id> to merge changes locally, or pass --pr to open a pull request on GitHub.

Supported providers

Raigal supports three local coding tools:

Provider	Invocation	Setup command
Claude Code	`claude`	`raigal agent connect claude`
OpenCode	`opencode`	`raigal agent connect opencode`
Codex	`codex`	`raigal agent connect codex`
Auto-detect	Automatic selection	`raigal agent use auto`

Check which providers are installed on your machine:

raigal agent providers

Workflows

1. Interactive local repair session

Preview and test changes locally before committing:

# Preview what the repair session will target
raigal agent plan .

# Start the interactive repair session
raigal agent --provider opencode .

# Check active and recent repair sessions
raigal agent sessions .

# Inspect the diff and diagnostics from a session
raigal agent show <session-id>

# Apply the approved changes back to your working branch
raigal agent apply <session-id>

2. Automated pull request creation (`--pr`)

To create a branch and open a pull request automatically, run:

raigal agent --provider claude --pr --target 95

With --pr, Raigal:

Runs safe autofixes and passes remaining issues to the agent provider.
Checks that the quality score meets --target (default: 90).
Commits the changes to an isolated branch (raigal/repair-...).
Pushes the branch and opens a GitHub pull request.
Sends telemetry to Raigal Cloud to create a card in the Agent Actions column.

3. Lifecycle synchronization (`report-pr-closed`)

When an agent pull request is merged or closed on GitHub, update your board status with a GitHub Actions workflow:

# .github/workflows/raigal-pr-closed.yml
name: Raigal PR lifecycle

on:
  pull_request:
    types: [closed]

jobs:
  sync:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 22
      - name: Report PR closed to Raigal Cloud
        env:
          RAIGAL_TOKEN: ${{ secrets.RAIGAL_TOKEN }}
          RAIGAL_API_URL: ${{ secrets.RAIGAL_API_URL }}
        run: |
          npx -y @methiu/raigal@latest report-pr-closed --pr ${{ github.event.pull_request.number }} ${{ github.event.pull_request.merged && '--merged' || '' }}

Opening a pull request with raigal agent --pr creates a card in the Agent Actions tab. When merged, report-pr-closed moves it to Merged and records the score delta.

Getting started

Core concepts

CLI reference

Automation & CI/CD

Cloud platform

Automated agent repairs

How worktree repairs work

Supported providers

Workflows

1. Interactive local repair session

2. Automated pull request creation (`--pr`)

3. Lifecycle synchronization (`report-pr-closed`)

​How worktree repairs work

​Supported providers

​Workflows

​1. Interactive local repair session

​2. Automated pull request creation (--pr)

​3. Lifecycle synchronization (report-pr-closed)

How worktree repairs work

Supported providers

Workflows

1. Interactive local repair session

2. Automated pull request creation (`--pr`)

3. Lifecycle synchronization (`report-pr-closed`)