Orbicus LogoOrbicusBeta
Product

Reviews & Diffs

Orbicus employs a deterministic review layer between generated code and your local file system. Rather than modifying your files unchecked, proposed code changes are staged as visual diffs, giving you full control over what is applied to your repository.

The Review Pipeline

When an agent executes file modifications, the changes progress through three distinct stages:

Proposed Changes  ──►  Virtual Staging (Diff)  ──►  Disk Application
                            │                              │
                            └── Reject / Discard           └── Rollback
  1. Generation: The agent calculates replacement chunks against the current file state.
  2. Virtual Staging: Changes are formatted into a visual diff without overwriting files on disk.
  3. Approval & Commit: Once you approve the changes, the edits are written atomically to disk.

Diff Inspection Modes

The review panel provides two viewing modes depending on the scope of the change:

  • Side-by-Side (Split): Compares the original file on the left with the proposed replacement on the right. Best for structural refactors, large function rewrites, and file migrations.
  • Inline (Unified): Displays additions and deletions in a continuous single-column feed. Ideal for targeted bug fixes, single-line modifications, and quick audits.

Granular Approval Controls

You do not need to accept or reject changes on an all-or-nothing basis:

  • Per-File Acceptance: Review a multi-file pull request proposal and accept configuration updates while rejecting changes to business logic.
  • Hunk-Level Reviews: In unified diff view, select individual hunks to accept while discarding extraneous stylistic edits.
  • Rejection with Feedback: When rejecting a proposal, you can provide corrective feedback directly into the prompt bar, prompting the agent to adjust its solution based on your notes.

Reverting Changes

Every accepted edit step is recorded in the session history. If an applied change breaks your test suite or causes regression:

  1. Locate the specific edit turn in your session timeline.
  2. Click Revert Changes to roll back the modified files to their exact pre-edit state.
  3. Your local git working tree remains consistent, and you can resume prompting with adjusted instructions.