E2E verification is now visible from dispatch to verdict
A live lifecycle card in the run view, a verifying chip on Done runs, and failed verifications land in Needs you with a one-click retry.
After this entry you'll know where E2E verification results live and what happens when one fails. When a bee finishes a change it can dispatch an end-to-end verification (a real build and device test) that runs in the background after the run is Done. Previously the verdict landed as a barely-visible line of small text, and a failed verification changed nothing anywhere.
What changes for you
- One live card in the run conversation. Dispatch, approval, build and verdict now collapse into a single card that updates through each stage while the verification is in flight, then settles into a clear pass or fail with the evidence (build and device links) as buttons.
- A verifying chip on the run. The run itself stays Done (the agent's work genuinely is done), but the run header, sidebar and runs list now show a chip while verification is still running and a red chip if it failed, so you can answer "is Done actually verified?" from any list.
- Failures come back to you. A failed verification puts the run into the Needs you lane with a retry option. Retrying re-runs the verification through the normal approval gate, so device and CI spend still gets a human yes before anything runs.
See what a run is doing while it runs
Live activity in the run view, a heartbeat on every running job, and automatic stall detection with an ops alert.
Stop a run, choose the fleet's model, see the spend
A per-run Stop button with a distinct Stopped status, fleet-wide model and effort selection from the admin console, and admin cost pages.