Parallax
Delegate a change, get back a reviewed patch. Parallax runs coding agents in isolated worktrees, has a different provider review the change, and gates integration on the project's own checks.
Interactive walkthrough
Follow a change to the gate.
Change the check result or the reviewer's verdict and see which candidates can reach a person for approval.
Select a stage to inspect its role in the workflow.
Step 4: Approve, then deliver. A person approves, then delivers.
Private worktree. Your staged and untracked changes are snapshotted, not touched.
Approves the change without knowing its author.
Approve candidate → Apply locally or Publish draft PR
Step 04 / Inspect
A person approves, then delivers.
Approve candidate records the decision. Applying the patch locally or publishing a draft PR is a separate, explicit action, and merging stays with the developer.
state: Candidate saved · awaiting approval
verification record: gates, settings, checks, patch hash
applied to project: noChecks passed and the independent review approved. The candidate waits for a person; nothing is applied yet.
Illustrative task with sample results. This walkthrough makes no model calls and runs no checks.
How a run reaches your projectResults
- 01Provider adapters for Codex, Claude Code, Grok Build and Antigravity, with roles limited to each transport's enforceable capabilities.
- 02Each run keeps a verification record of gates, settings, checks and the patch hash. It is evidence, not a correctness guarantee.
- 03Public development preview. Live pilot acceptance remains a release gate.
Engineering details
An agent saying tests passed is not verification. Delegated code changes need isolation from in-progress work, a review the author cannot influence, and checks that actually run before anything reaches the project.
Isolate the workers
Parallax snapshots staged, unstaged and untracked changes without touching the index, and agents work in private worktrees. Only the verified patch is applied.
Review independently
A provider that did not implement the change reviews it without learning who wrote it. Every model call receives a compact, role-scoped packet compiled from saved state rather than a shared transcript.
Gate on checks, then approval
Integration requires the project's check commands to pass. A person approves the saved candidate; applying it locally or opening a draft PR is a separate, explicit step.