One goal.
More than one
perspective.
Bring Codex and Claude together in a workspace that makes their work easier to compare, check, and improve.
Built for Windows. Uses your installed agents and provider accounts.
Let customers find products by name.
Keep the existing checkout working.
Another approach
Isolated candidateCompare. Propose. Refine.
Use both implementations and the saved checks to shape one result.
Your goal starts the work.
The evidence guides the decision.
A conversation gets you started. Structured workflows keep the next steps visible.
Bring your project
Import a Git URL, choose a local folder, upload a ZIP on your PC, or start from scratch.
Describe one clear goal
Explain the outcome and what must keep working. Review the agents, acceptance checks, and execution limits.
Let different approaches emerge
Codex and Claude work in separate candidate folders. A synthesis stage compares their work and proposes a result.
Decide with the evidence
Inspect the changes, saved check results, and limitations. Approve, request changes, or use reviewed Auto within its limits.
More visibility.
Fewer leaps of faith.
Read the candidate changes and the checks run against the exact result. Agent opinions and test results stay distinct, so you can judge what each one establishes.
Read the workflow details- Changes
- Exact candidate commits
- Checks
- Saved validation results
- Context
- Reasoning and limitations
- Control
- Approvals and bounded Auto
A completed workflow records a decision. Merging, pushing, and deploying remain separate actions.
Choose the depth
your work needs.
Modes define roles and review stages. They do not guarantee a particular cost or quality.
Bright
Beta targetA focused starting point.
Codex and Claude independently implement your goal. Codex C compares the candidates, proposes the approach, and produces the final result.
A + B → C → validationBrighter
Internal previewAn additional authoring stage.
Claude C synthesizes the independent candidates. Codex D uses C’s work to propose and implement the final result.
A + B → C → D → validationBrilliant
Internal previewA separate final review.
A and B plan and implement independently. Claude C produces the final result, then a separate Codex D session reviews the frozen changes and evidence.
A + B → C → validation + D reviewUse the built-in modes or create a custom workflow. Each assignment has explicit call and time limits; these are not monetary price estimates.
Follow what’s next.
PeerLoom is in private-beta preparation. The focused target is Windows with Codex and Claude in Bright mode. Public downloads and open signup are not available yet.
Explore PeerLoom on GitHub