Assistant

The Assistant helps you understand tests and results, explore your app, and prepare changes for review. Open Assistant in the navigation. Conversations belong to the selected project and can be reopened from the conversation list.

Start a conversation, send a question with the run attached as context, debug a failed scenario and review the proposed change, explore the app for suggested tests, and write a request that uses a project secret, as in the sections below.

Start a conversation

Ask a specific question, such as “Why did run #25 fail?” or “Suggest tests for password reset.” Use Suggestions for common starting points. You can choose an available model in the composer.

Ask Assistant actions on tests, runs, and load results include context from the selected item. These requests appear as a short, readable request in the conversation. They do not require you to copy the result or write a prompt from scratch.

Debug a failed test

Open a failed scenario and choose Debug with Assistant. The trace workspace opens with Trace and Assistant tabs, and the Assistant investigates the supplied result.

When the evidence supports a fix, it prepares a concrete proposal for review in the same conversation. Review the code change before applying it or opening a proposed source pull request. An environment problem, missing evidence, or a correct test catching an app bug may need another action instead of a test patch.

The work runs in a background session. Activity such as checking a trace is progress, not the final answer. Read the explanation and any proposal, or the visible error if the session could not finish. Continuing in the app does not require keeping the chat in view.

Explore and suggest tests

Use Explore my app and suggest tests to have the Assistant inspect your configured site. Review each suggestion's behavior and verification state. Suggestions produced with verified code can be accepted as runnable tests; other drafts still need generation or an Assistant run.

The Assistant can offer Continue exploring when there is more work to do. Check the scope before continuing, since exploration uses credits.

Keep requests useful

Name the behavior, test, or run you want help with and explain the expected outcome. Use project variables and secrets for credentials. If the Assistant asks a necessary question, answer it in the conversation. Changing projects also changes the context and conversation list.

See Assistant reference, Inspect failed steps, and Review generation progress.