Example route
Agent Workbench
A long-running agent flow with tool events, checkpoints, artifacts, and a handoff into review.
Why this pattern works
- Tasks can change visual language when moving from execution to waiting or review.
- Users see stage progression and artifacts at the same time, which avoids false certainty.
- The surface keeps control chips visible so backgrounding and review never feel hidden.
Full event feed
Provisioning a fresh execution environment.
Five stages are visible before any write happens.
Parsing the request and defining safe checkpoints.
Scope is locked and the workspace can be inspected.
Reading files and inferring the change boundary.
Search is scanning the repository for entry points.
The main routes and reusable primitives are identified.
Safe edit boundaries are now visible.
The agent is editing and staging artifacts for review.
A patch preview is available before verification.
The user can leave without losing progress.
The code changes are stable enough for verification.
Build and smoke checks are underway.
The verification suite finished without blocking failures.
Diffs, artifacts, and next steps are bundled for inspection.
2-10 minutes. This is no longer a loading state.
Stage Rail
Lock scope, constraints, and success criteria.
Read files and infer the safe edit boundary.
Mutate the project with checkpoints.
Execute tests and gather proof.
Collect diffs, screenshots, and review notes.
Artifacts
diff
Patch previewA reviewable diff summary with ownership notes.
bundle
Review bundleDiff, screenshots, logs, and verification output.
Evidence Feed
Diffs, artifacts, and next steps are bundled for inspection.
The verification suite finished without blocking failures.
Build and smoke checks are underway.
The code changes are stable enough for verification.
The user can leave without losing progress.
A patch preview is available before verification.