Changed files
See the task, branch, commits and files changed before opening the PR.
Demo
See a Dex run the way a reviewer sees it.
This static walkthrough shows how DexCode turns AI coding work into a run record with evidence, cost, review status and next action.
Run assistant
SimulatedEngineering lead
Show me the checkout validation run and tell me whether it is safe to review.
DexCode
The branch changed three files, added request coverage, passed Rails tests and attached a browser screenshot. The PR is ready for human review; deployment still needs approval.
Engineering lead
What should I check first?
DexCode
Start with the failed-card behavior, then inspect the cost summary and the PR evidence block.
Ask DexCode: what changed, what passed, and what needs review?
What you can inspect
A reviewer-ready run record
The demo mirrors the record a team needs after an AI coding run.
Verification
Read test output, browser evidence, screenshots, traces and known limits.
Cost and controls
Check token usage, provider, budget policy and approval status.
Try it
Use DexCode when the work needs to be inspected.
A small run record is easier to trust than a long chat transcript.