Parallax
Using it
The lenses, the line a sweep leaves in your terminal, and where each part is explained in full.
When a session ends
A Stop hook, an explicit end, or thirty quiet minutes, and the door sweeps the session: it proves the agent’s own edits in a sandbox, reviews the transcript, forks the implementation turn to router-picked seats from other labs, re-runs the proven tests of the other sessions on the same files, runs the lenses below with a proof for each finding, scans for dead code, and delivers. Each step and what it can say is on Sessions.
curl -s -H "authorization: Bearer $PARALLAX_TOKEN" "$PARALLAX_URL/v1/sweeps"The lenses
| lens | asks | proof |
|---|---|---|
bugs | what is wrong that the existing test did not check? | the new test fails without the fix and passes with it; the full-suite result is reported separately |
security | what could an attacker use? Asked together with bugs as one question per shard | the same reproduction, with a severity; a mechanical pass first, free |
perf | a faster, simpler or smaller way? | a benchmark on each side, or fewer branches; suite green |
hygiene | what was left behind? | static first: an edit may only remove or reword, never add a branch or a call; then the suite is green with the cleanup |
drift | which document now says something untrue? | the referent is really gone; a one-line prose fix |
dead code | what does nothing reference? | each removal proven alone and together; no model call |
Source: packages/lens/cards/lens.input.json · packages/deadcode/cards/deadcode.input.json
On a pull request
When automatic PR review is enabled or a review is explicitly requested, one check, Parallax, carries a first pass in minutes and a deep pass after it. Automatic PR review is off by default (PARALLAX_PR_REVIEW=on enables it). Findings are line comments, each labelled with its evidence state and a confidence. Eligible patches have a one-click suggestion and one fix PR per review; refuted patches and patches that regress the suite have neither. What each label means, the exact rules, and the sections of the comment are on What a review means.
Memory
A proven finding, a merged fix, or a suggestion you applied becomes a lesson for the repository, and the next session that touches that file is handed it. A suggestion you dismiss becomes a suppression. What a lesson is, what is injected, and how to see the receipts are on Memory.
What it costs
Every reviewer call carries a settled receipt, and every sweep line ends with its own spend. There is no cap on what a review may read, run or spend: the clock is operational only and ends a review that would otherwise not end. The clock, the schedule, and what a repository or a person can set are on Control. The ledger at GET /v1/review-ledger is the account’s record: findings by lens and evidence state, accepted rate, time to complete, and dollars per review.
Source: packages/server/cards/sweep-line.json · packages/ledger/cards/ledger.input.json