Cast

Cast personas are synthetic users that test your product. Each one has a backstory, a personality, and a focus area; every visit it pursues one concrete goal, drives a real browser through your app, and leaves a terse, evidence-based report of what worked, what broke, and what's missing — then updates its own memory so the next visit builds on this one.

Cast exists to keep your backlog from going empty. A solo founder rarely has time to sit and use their own product like a stranger would; Cast does it on a schedule and hands back findings tied to a specific screen and action.

How a session works

1. Becomes the persona. It loads who it is, its focus area, the session's goal, and its memory from past visits — so it picks up where it left off and re-checks whatever was broken or missing last time.
2. Reads your app from source. When a GitHub repo is connected, it shallow-clones it read-only to map which URL serves which feature — so it goes straight to the relevant surfaces instead of wandering. It never pushes or commits.
3. Drives a real browser. It exercises the flows hard with Playwright (Chromium), on a desktop or mobile viewport, logging in with a throwaway test account when the goal needs it. The whole session is recorded to one video you can watch back.
4. Writes findings + ideas. The deliverable is a worked / broken / missing report plus buildable product ideas — no mood, no review-speak — each one something you could act on. It also updates its persistent memory.

What you get back

Cast is read-only by design — it uses your product, it never changes it — so it runs without a human gate. The findings surface as a ticket; comment on one to send the persona back with new direction.

Running a persona

Create a persona, then start its first session from the dashboard. Cast is a paid feature: if you haven't subscribed yet, the first run hands you a checkout link, and the session starts automatically once payment clears. After that, personas wake on their own cadence.