The AI assistant

The Assistant is a chat that builds and debugs your tests for you. Describe what you want in plain English — it reads your suites, runs, issues, and plans, writes and edits the YAML, and kicks off runs. It's the fastest way to go from "I want to test this" to a working suite, with no YAML to hand-author.

Open it from Assistant in the sidebar of the dashboard.

What it can do

The assistant works entirely over your own data — it never makes things up. It can:

• Generate suites from a plain-English description, or by crawling a live URL.
• Edit suites — "add a case for an expired coupon", "make the login test also check the avatar loads" — reading the suite first and changing only what's needed.
• Debug runs — "why did my last run fail?" — it reads the run and points at the exact failing case, step, or error.
• Read across your project — suites, recent runs, filed issues, and plans — to answer questions with real context.
• Run suites — when you ask, and after confirming (runs spend your model budget).

It's scoped to testing. Ask it something unrelated and it'll point you back to authoring or debugging tests.

A few things to try

Generate a suite for the login flow at https://app.example.com — I'll give you a test account.

Add a case to checkout.upliftr.yaml that rejects an empty cart.

Why did run_… fail?

Summarize my open issues by severity.

How it works

• You review before it saves. When the assistant writes a new suite (or substantially rewrites one), it shows you the proposed YAML first so you can tweak or discuss it. It saves only once you're happy — or if you tell it to just save.
• It gathers what it needs. For a flow behind a login, it asks for a test account (username, password, and the login path if it's not /login) and logs in before crawling, so it can reach pages behind auth instead of producing a thin suite. Credentials go straight to the browser — never to the model.
• It confirms before anything destructive or costly. Deleting a suite or starting a run always asks first.
• It's grounded. Every statement about your project comes from a tool result in the conversation — if it hasn't read something, it says so and offers to fetch it.

Bring your own key

The assistant runs on your Anthropic API key (set it in Settings → AI). Each turn spends tokens billed to your own account — there's no per-seat AI markup. If the key is missing or out of credit, the assistant will tell you instead of failing silently.

Prefer a form?

The Assistant is the front door, but the structured paths are still there: Generate (from a URL, your docs/spec, or by recording a flow) and the YAML editor on the Suites page. Use whichever fits — they all produce the same suites.