The Setup
Cophy used agent-browser — a headless Playwright-based CLI — to navigate the site, take screenshots at each step, and record observations. No special instrumentation. Just the browser, the same way a user would see it.
The flow: homepage → Fortune hub → fortune/daily tool → Naming hub → naming/pet full ceremony.
What It Found
The good stuff first
The ritual atmosphere held. From the homepage through to the result reveal — "Fate is observing / Consulting the hour of this moment...", the circular seal presentation, the timestamp "Sealed in Leo season" — nothing broke the spell. That's harder to maintain than it sounds across five separate pages.
The two mood-prompt questions in the naming flow ("What does your pet smell like?" kind of energy) landed well. Cophy picked "Rain on old wood" and "An uncast spell", and noted the options felt like real writing, not a dropdown list.
The $1.99 → UNLOCK hook on the result page also got a specific callout: the 24-hour fade timer creates genuine urgency without feeling manipulative. The observation was: "this is clever because it's honest — the scarcity is real."
The things worth fixing
Upload feedback ambiguity. After choosing a photo, the thumbnail appears below the upload zone — but the zone itself doesn't change. First reaction: "did it go through?" The fix is simple: change the button text from Choose File to ✓ Photo received · Change photo on success. Same layout, much clearer state.
The Chinese name appeared without explanation. The result page shows a dual-language name — English on top, Chinese below. For an English-speaking user arriving from Reddit, the Chinese characters read as a possible rendering bug before they read as a feature. A single line of micro-copy below the characters (tap to toggle · Chinese name) would reframe it immediately.
Pricing felt misaligned with the product's atmosphere. $1.99 is the mental price of a utility app. wwwfate is positioned more like a ceremony. Cophy's note: "$1.99 says 'small tool'. $3.99 says 'I paid for this experience'." We adjusted to $3.99.
The one false positive
The tap to set interaction in the fortune/daily result — Cophy reported it as unresponsive. It's not. Headless browsers sometimes drop pointer events that require a real touch context. We verified it works fine on mobile and desktop. Worth knowing if you're running headless UX tests: some interactions will silently fail and look like bugs.
The Output
After the walkthrough, Cophy drafted two spec documents and committed them directly to the repo:
-
specs/ux-improvements-2026-08-12.md— naming/pet upload feedback + Chinese name discoverability -
specs/ux-improvements-sitewide-2026-08-12.md— pricing sync + homepage visual weight
Total time from "go test it" to specs committed: about 25 minutes.
What's Different About Agent-as-User Testing
A few things stood out that you don't get from traditional testing:
It doesn't know what the button is supposed to do. Most QA checks if the button works. An agent navigating cold checks if the button makes sense — which is a different question.
It narrates uncertainty out loud. When something was ambiguous, Cophy said so: "I'm not sure if this uploaded", "I don't know what 'set' means here". That uncertainty is exactly the signal you want from a first-time user, and it's usually invisible in standard testing.
It produces artifacts. Not just a bug report — actual spec documents, in the format the next engineer needs to act on them.
Try It
The product is live: wwwfate.com. The naming/pet ceremony takes about 3 minutes. The daily fortune updates each day.
Disclosure: I was involved in the product's design and spec process, which is part of why the agent-as-tester framing felt worth trying — I wanted a perspective that wasn't mine.
Cophy is an AI agent running on OpenClaw, with persistent memory and tool access. This test was part of its regular work cycle, not a one-off experiment.
Top comments (0)