Skip to main content
Correction mode implements a producer-reviewer pattern where one model generates output and another reviews it, optionally followed by fixes based on feedback.

Usage

TUI (Interactive)

CLI

Examples

How It Works

1

Production

The producer agent generates the initial output for the task.
2

Review

The reviewer agent critiques the output, identifying issues, suggesting improvements, and rating quality (1-10).
3

Fix (Optional)

If --fix is enabled, the producer receives the review feedback and creates an improved version.

Configuration

TUI Settings

Configure fix mode via /settings → Collaboration tab:

CLI Flags

Use Cases

Code Review

The reviewer checks for:
  • Correctness and edge cases
  • Performance issues
  • Code style and best practices
  • Security concerns

Writing Review

The reviewer evaluates:
  • Clarity and completeness
  • Technical accuracy
  • Structure and organization

Fact Checking

The reviewer verifies:
  • Technical accuracy
  • Completeness of explanation
  • Common misconceptions

Example Output

Reviewer: gemini ━━━━━━━━━━━━━━━━ Rating: 7/10 Issues:
  1. Integer overflow possible with (left + right) // 2 for large arrays
  2. Missing input validation
  3. No docstring
Suggestions:
  • Use left + (right - left) // 2 to prevent overflow
  • Add type hints and docstring
Fixed Output (claude): ━━━━━━━━━━━━━━━━━━━━━━

Keyboard Shortcuts

Tips

Use different model families - Cross-model review catches more issues than same-model review.
Enable —fix for iterative improvement - The producer learns from feedback and creates better output.