Project-aware checks
Use existing scripts and focused verification instead of inventing a generic pass condition.
All product areas
06 / Foundry + Review
Verification evidence before the result moves.
Foundry discovers and runs the checks a repository already trusts. Review then combines the final response, integrated diff, launch terminal, and browser preview into one approval surface.
Actual completed-run review
WHAT IT CHANGES
Less reconstruction.
More visible progress.
A real integrated preview
Start the candidate result, discover its local URL, and inspect it in the same browser surface used by agents.
Human browser verdict
Mark the visual review good or send the result back with concrete feedback before it is applied.
Evidence tied to exact code
A passing result belongs to a specific attempt, worktree, and fingerprint, so stale verification cannot masquerade as current.
Repair failed checks
Send a failing check back to the same agent, preserve its context, and automatically verify the repaired work again.
Two safe delivery paths
Apply the verified candidate to the local workspace or create a pull request linked to the original GitHub task.
WHAT IS BUILT IN
The working surfaces behind Foundry + Review.
Discover the repository’s own gates
Sourceweave reads scripts for tests, lint, types, and builds, records required and optional checks, and shows duration, status, exit code, and captured output.
Keep the useful handoff prominent
The orchestrator synthesis and each worker’s final response are formatted as review artifacts while low-level command output remains available separately.
Inspect what will actually move
Browse the integrated worktree, open generated files, and compare the candidate against the workspace baseline in a side-by-side editor.
Run the candidate before accepting it
Start the detected command, open its local URL, switch responsive viewports, and record a human pass or a needs-changes verdict with feedback.
HOW IT WORKS
A deliberate path through Foundry + Review.
- 01
Integrate worker branches
Combine completed assignments into the run’s candidate result and preserve their final responses.
- 02
Run the evidence gates
Execute discovered tests, syntax checks, repository hygiene, and browser-aware validation.
- 03
Inspect the running result
Review files and changes, launch the app, and confirm—or reject—the browser experience with concrete feedback.
- 04
Apply or create a pull request
After review, update the local workspace or open a linked PR for the original GitHub issue.
KEEP EXPLORING