crashcrewPUBLIC DEMOChecking worker
CRASHCREW / THE PRE-RELEASE CREWFIELD MANUAL 001 · BROWSER EXECUTION
Before your next release

Ship the product.
Keep the receipts.

Send a crew through the clicks that matter.
Catch the broken journey.
Bring back something you can inspect.

01
Current missionFirst workspace
Configure mission

Real browser execution. Included demos only.

{ }mission.spec.jsonFrom your mission brief
SpecificationBrowser workerEvidence archive
Latest completed runNO RUN YET
AWAITING EVIDENCE
Awaiting a missionScreenshots · steps · traceInspect run
CC / SPEC · EXECUTION · RECEIPT
PUBLIC DEMO / OBSERVED ACTIVITY0 completed runs0 captured framesNO RESULT WITHOUT A RUN
The Crashcrew approach

Every release
needs a crew.

The happy path is a theory until a browser completes it. Crashcrew follows the journey and preserves what actually happened.

01 / BRIEF

Tell us where it should go.

An approved website, named controls and a visible result. Simple inputs become an inspectable mission specification.

02 / CONTACT

Let the browser make contact.

A fresh browser context follows the sequence. Every completed action leaves a captured frame.

03 / RECEIPT

Keep the evidence. Fix. Repeat.

A passed step, a missing result, a screenshot and a trace. Rerun the same mission after the repair.

Mission control

Define the journey.
Examine the outcome.

Name the action. Set the expectation.
Watch the browser return the evidence.

BROWSER EVIDENCEAWAITING MISSION
Your journey starts here1280 × 800
[ cc ]

Show your work.

Start a journey. Actual browser screenshots
will appear here as each step completes.

SCREENSHOTS APPEAR AFTER EXECUTION
Waiting for a real run
An outcome, not a safety certificate.
Run archive

A record.
Not a promise.

This browser keeps recent runs, outcomes and screenshots.
Compare the same journey after a fix.

MISSIONOUTCOMETIME

Your first run will start the record.

Built with receipts

Under the hood.
Out in the open.

Inspect your mission as JSON. Keep it with your project. Review the open-source browser engine behind each run.

Browser enginemicrosoft / playwright GitHub

Used for browser execution, screenshots and traces.

Agent app scaffoldvercel / eve GitHub

Agent tooling scaffold. AI planning is not connected to this lab.

Crashcrew sourceLocal build · public repository pending

Dependency links above point to their maintainers, not a Crashcrew repository.

The operator role

A crew that keeps checking.

The proposed token role is a bounded recurring mission. Token access and scheduling are not active in this public demo. Nothing here requires a purchase.

NOT ACTIVATED
LESS CONFIDENCE. MORE EVIDENCE.

A browser has
the final word.

This public demo opens a real browser, clicks the exact controls you name and checks for visible text. Screenshots and a downloadable trace record what happened.

“Passed” means this journey completed in this run. “Failed” means an expected step did not complete. “Blocked” means the worker could not finish. None of these is a security audit.

The demo has a deliberately broken button and a fixed version. They are controlled test targets, not customer results. Natural-language AI planning and token membership are not connected.