Early accessGhost user testing
You built it.
Let the ghosts test it.
Ghost users with different identities, roles and goals work through your web app together. They find what breaks between people, show the evidence, and run again to prove the fix.
- 1Editor signs inEditor reaches their dashboardpassed
- 2Administrator signs in Starts together with step 1Administrator reaches their dashboardpassed
- 3Editor creates a documentDocument saved as Draftpassed
- 4Editor submits the documentStatus shows Submittedpassed
- 5Administrator approves the document Waits for: editor submitsApproval acceptedpassed
- 6Editor checks the document status Waits for: administrator approvesEditor sees Approvedfailed
A problem was found
The editor didn't see the approval
- Expected
- After approval, the editor sees Approved on the document page.
- Observed
- The approval succeeded. The editor's document page did not show Approved.
- Where to investigate not confirmed
- Check whether the page reads the latest status after someone else approves. A stale value is one possibility.
Preview fix prompt
Bug: after an administrator approves a document, the editor's document page still shows the old status. Roles: Editor (submits), Administrator (approves). Steps to reproduce: 1. Sign in as the editor and as the administrator. 2. As the editor, create and submit a document. 3. As the administrator, approve it. 4. As the editor, open the document page again. Expected: the editor sees "Approved". Observed: the approval succeeded, but the page did not show "Approved". Where to start (not confirmed): check whether the document page reads the latest status after another user changes it. Verify: run the same check again and confirm the editor sees "Approved".
The same scenario ran again after the fix. The check that failed now passes under comparable conditions.
01Why ghosts
Most bugs live between people.
You can build fast, with an AI assistant or by hand, and still miss the problems that only appear when two people with different roles use the same app. That is where the ghosts go.
A page one role should never reach
An administrator and an editor open the same admin page. The editor is refused in the interface, but the server answers anyway.
A change another person cannot see
One person approves a document. The person who submitted it still sees the old status on their page.
Access that should have ended
An owner shares a record with a viewer, then revokes it. The viewer opens the record again and it still loads.
02Find, fix, verify
A finding is the start. A verified fix is the finish.
Every finding records which ghost saw it, the steps to reproduce, what was expected and what was observed. Where to investigate is labelled as a starting point, never as a confirmed cause.
Paste the fix prompt into Claude Code, Codex, Cursor or any coding assistant. Then run the same check again, or compare against a result you approved, from the app, the CLI or a CI job.
How regression checks workWhat a repeat run can tell you
- All checks passedEvery planned assertion ran and passed.
- A problem was foundA complete run failed an assertion that was expected to pass.
- New regression foundA check that passed in your approved result fails now.
- Known issues remainNo new failures, but the approved result already had these.
- Issue confirmed resolvedThe same checks ran again under comparable conditions and passed.
- InconclusiveSetup or comparison could not establish a trustworthy result. Never blamed on your app.
03Explore
See what the ghosts can do.
Let the ghosts into your next release.
Early access is opening to a small number of teams. Tell us what you are building and how you build it.