liluser
A first user for your product

Meet Scout.
Your app's first user is an agent.

liluser points an autonomous synthetic-user persona at your live, staging, or preview URL. Scout signs up, onboards, tries a goal, and tells you what actually happened - with receipts.

Read a real report

Sign in with GitHub — 25 trial credits on us. This run costs 1. The report link is yours.
scout / first-time operatorrun live

Hi, I'm Scout.

I am trying to reach the dashboard.

  • 01opened preview URL
  • 07confirmation email received
  • 12finding: workspace is undefined
  • 15goal reached / evidence saved
Black-box by design.Real browserNo SDK or instrumentationLive / staging / previewOracle-verified side effects
The route Scout takes

Fresh eyes, not scripted assertions.

Give liluser a URL and a goal. The persona explores the experience like a new user would, while the run records the useful details your end-to-end test never thought to ask about.

  1. 01 / POINT

    Drop in a URL.

    Live site, staging app, or preview deploy. No hooks, SDK, or instrumentation required.

  2. 02 / TRY

    Scout drives a real browser.

    It signs up, confirms email when needed, onboards, and tries the goal you set - with a real synthetic identity.

  3. 03 / REPORT

    Get the useful version of "it felt weird."

    Green checks, annotated findings, screenshots, and side effects verified against the world - not just Scout's memory.

The output

A report that can point to the moment.

Every finding stays typed and local: severity, URL, step reference, screenshot, and what Scout was trying to do. Happy paths get green checks. Blocked paths stay visible.

See the self-review report

Run complete
preview.acme.dev / first-time operator
pass with findings

Onboarding checkpoint

  • [ok]Signed up and reached the dashboardverified
  • [ok]Confirmation email arrived in Scout's inboxoracle
  • [!]"Workspace" is never defined before setup asks for oneminor / step 11
  • [!]Continue action looks disabled while loadingmajor / screenshot
15 steps2m 21sscreenshots: 04side_effects: verified
Bring Scout where work happens

One run. Three ways in.

Use the surface that fits your loop. The output stays a report your team - or your coding agent - can act on.

For the loop

GitHub Action / CI

Run against every preview deploy and leave the report where the PR is already being discussed.

For the terminal

CLI

npx liluser init
npx liluser run
npx liluser audit

For the system

API

POST /v1/runs returns a run you can poll, link, and pass into the next step of your workflow.

Scout, in four moods

Personality on the edges. Facts in the center.

Trying"I found the sign-up button. Off we go."
FindingStatus: blocked at CAPTCHA. Not bypassed.
AhaGoal reached. Side effect verified.
ReportEvidence attached. Actionable next step ready.
Trust, with the boring bits included

Useful because it knows its limits.

Reports are engineering input.

They capture a persona's observed experience and evidence. Treat findings as a sharp starting point for your team, not an infallible product verdict.

Point Scout only at apps you can test.

You must own the target or have target-owner authorization. Runs create accounts, trigger emails, and interact with the app on your behalf.

Blocked automation is a finding.

CAPTCHA, KYC, bot detection, and other walls are reported as blockers. liluser does not bypass them.

Beta means beta.

Open beta includes 25 trial credits on sign-up. Paid plans exist in the docs, but are not yet available for purchase.

Let Scout be first.

Try a run on a URL you are authorized to test. Sign in, no instrumentation, no ceremony.

Try a run