> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testsprite.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Setup

> The Setup tab: the project the agent proposes, the environments it tests on and how it signs in, and the code, docs and files it works from.

![The Setup tab beside the chat on a draft project: Properties, Environments and Context, with the Ready to create card above the chat box](https://mintcdn.com/testspriteinc/j_xmvCOBqyVxazzK/images/agent-setup-overview.png?fit=max\&auto=format\&n=j_xmvCOBqyVxazzK\&q=85\&s=390cb72856e982f4b28dfee4f3243cea)

## What the Setup Tab Is

A project starts as a conversation. You tell the agent which app to test, it asks for what only you know, and it proposes a project. The **Setup** tab, beside the chat, shows that proposal: what the agent works from, and what it knows.

**Nothing is created until you create it.** While the project is a proposal it is a **Draft**: it shows in **Recent Projects** and **All Projects** with a <kbd>Draft</kbd> badge, and the Setup tab reads *"{name} · proposed, not created"*.

## Starting a Project

**1. Open New Project**

Click <kbd>New Project</kbd> in the sidebar. The page asks **"What should we test?"**

**2. Point the agent at your app**

Paste your app's address in the chat box, or say what to test. Use the <kbd>+</kbd> menu to add **Documents** (PRDs, specs, notes; up to 50 MB each), a **GitHub Repository**, a **Jira or Linear Issue**, or a **Test Account**.

![The New Project page with the + menu open: Documents, GitHub Repository, and more](https://mintcdn.com/testspriteinc/IV-iejaf59JAQSCI/images/source-upload.png?fit=max\&auto=format\&n=IV-iejaf59JAQSCI\&q=85\&s=304e52f99e79f9cbd8cd8f56858c2066)

**3. Answer the agent's questions**

Before it explores, the agent asks once for what it can't find out on its own: the URL and whether it is production, how to sign in, what material you have, and what to cover first.

**4. Review and create**

A card above the chat box reads **Ready to create {name}**. Click <kbd>Review</kbd> to check it on the Setup tab, <kbd>Create Project</kbd> to create it, or <kbd>Not Now</kbd> to keep talking.

Once the project exists, the chat shows **Setup confirmed**, and the agent goes on to [explore the app](https://docs.testsprite.com/web-portal/core/ui/agent-exploration.md) and [propose test cases](https://docs.testsprite.com/web-portal/core/ui/agent-plan.md).

> [!NOTE]
>
> The repository and issue-tracker items in the <kbd>+</kbd> menu appear only when integrations are available to your workspace.

## What's on the Tab

![The Setup tab's three groups: Properties, Environments and Context](https://mintcdn.com/testspriteinc/IV-iejaf59JAQSCI/images/overview-configure.png?fit=max\&auto=format\&n=IV-iejaf59JAQSCI\&q=85\&s=c2f6abdb4da491eea456e84f463ed352)

| Group | What it holds | What you can do |
| :- | :- | :- |
| <kbd>Properties</kbd> | The project's **Name** and **Type** (Frontend or Backend) | Edit both until the project is created |
| <kbd>Environments</kbd> | Where the app runs: each environment's address and how to sign in there | Open an environment to change its address or test account; <kbd>Manage environments</kbd> opens the full [Environments](https://docs.testsprite.com/web-portal/setup/environments.md) page |
| <kbd>Context</kbd> → <kbd>Sources</kbd> | **Code** (the GitHub repository) and **Docs** (PRDs and specs) | Add code, attach docs, or open [Sources](https://docs.testsprite.com/web-portal/setup/project-sources.md) |
| <kbd>Context</kbd> → <kbd>Test Files</kbd> | Files a test uploads into your app | Attach files |
| <kbd>Context</kbd> → <kbd>Outputs</kbd> | What the agent wrote: the **Brief**, the **Test plan**, and any **Files** it made for you | Read and download them |

## How the Agent Signs In

Without a way to sign in, the agent can only explore and test what a signed-out visitor sees, so it never guesses: it asks. Each environment signs in one way, and the agent's browser and every test run on that environment sign in the same way.

![The Add Environment dialog's sign-in choices: test account credentials, a one-time password, or single sign-on](https://mintcdn.com/testspriteinc/IV-iejaf59JAQSCI/images/ui-testing-authentication-overview.png?fit=max\&auto=format\&n=IV-iejaf59JAQSCI\&q=85\&s=12ac72e2c3935f35ae08da4fdcb692f1)

| Sign-in | Best for | What you provide |
| :- | :- | :- |
| **Test account** | A username and password login | The username and password of an account made for testing |
| **One-time code** | Logins and signups that email a code or a sign-in link | Nothing: the agent makes a TestSprite-managed account with its own email inbox, and reads the codes your app sends there |
| **Saved sign-in** (manual login) | Google and other single sign-on, or a sign-in only a person can finish (a phone prompt, an approval) | You sign in once yourself in the agent's browser; TestSprite saves it so later sessions and runs start signed in |
| **No sign-in** | Parts of the app that work without an account | Nothing |

> [!WARNING]
>
> **Use an account made for testing, never a real one.** The agent's browser and the project's test runs sign in with it, and they perform real actions while signed in.

### Giving the agent a test account

Add the account with <kbd>+</kbd> → <kbd>Test Account</kbd> in the chat box, or <kbd>Add Test Account</kbd> under **Environments** on the Setup tab. Don't type a password into a message. If you do, a card stops it before it is sent: *"This looks like a password. Use the test account for it, and only a test login."* Choose <kbd>Test Account</kbd> to enter it properly.

![Test account credentials: the username and password the agent signs in with](https://mintcdn.com/testspriteinc/IV-iejaf59JAQSCI/images/ui-testing-authentication-Existing-Test-Account.png?fit=max\&auto=format\&n=IV-iejaf59JAQSCI\&q=85\&s=15f5568b8b5a12f743e3bdb6fb7ca6ea)

When the agent needs a secret it doesn't have, it asks with a card named for the secret. You type it there, and it is saved straight to the environment, encrypted. It never appears in the chat.

### When the agent makes its own account

If the environment has no sign-in and you gave none, the agent can register a TestSprite-managed account: a TestSprite email address and a generated password. It then saves that account as the environment's sign-in, so the next session signs in with it instead of making another. A managed account can't use Google, GitHub or other single sign-on.

![One-time code sign-in: the agent signs up with a TestSprite email address and reads the codes your app sends](https://mintcdn.com/testspriteinc/IV-iejaf59JAQSCI/images/ui-testing-authentication-OTP.png?fit=max\&auto=format\&n=IV-iejaf59JAQSCI\&q=85\&s=831e68143a633ab34b5b6b106c516b71)

### Saved sign-ins (manual login)

For Google and other single sign-on, or any sign-in only you can finish, you sign in yourself and the agent saves it:

![The agent asking you to sign in, with its live browser on the sign-in page beside the chat](https://mintcdn.com/testspriteinc/j_xmvCOBqyVxazzK/images/agent-setup-manual-sign-in.png?fit=max\&auto=format\&n=j_xmvCOBqyVxazzK\&q=85\&s=5941fd04c71604019c9bfe365cded6f8)

**1. Tell the agent you'll sign in yourself**

For example: *"I can sign in for you, it needs Google login."* The agent opens your app's sign-in page in its browser and hands over: *"Your turn: please sign in in the browser panel next to this chat."*

**2. Sign in in the browser panel**

The live browser on the **Exploration** tab takes your clicks and typing. Sign in there as you normally would.

**3. Tell the agent you're in**

Send a message such as *"I'm logged in, can you check?"* The agent confirms it can see your signed-in app.

**4. Let it save the sign-in**

The agent saves the signed-in session to the environment while the browser is still open; confirm the card if it asks. The chat then shows **Saved 1 change to environments**.

From then on, later sessions start their browser already signed in, and so do test runs.

> [!NOTE]
>
> **Sign in soon after the agent asks.** Each browser lasts about 15 minutes. If it times out before you finish, the agent opens a new one and you sign in again.

A saved sign-in lasts as long as your app keeps that session alive. When it expires, sign in again the same way, or from the environment's dialog.

![A saved sign-in on the environment, with Log In Again to sign in once more](https://mintcdn.com/testspriteinc/IV-iejaf59JAQSCI/images/ui-testing-authentication-Expired-Session.png?fit=max\&auto=format\&n=IV-iejaf59JAQSCI\&q=85\&s=afc94f364c60b9ab2f3e5763491484c2)

A few changes stay in the environment's settings instead of the chat: switching an existing environment to or from one-time-code sign-in, leaving a saved sign-in, and changing a managed account's inbox. See [Environments](https://docs.testsprite.com/web-portal/setup/environments.md).

## Environments

A project can have several environments (staging and production, an admin and a member account). The agent works on the project's default environment unless you name another, and says which one it used. When a run is ready to start, its card shows the environment and lets you pick another.

![The plan card's arrow open beside Apply and Run: 1 the arrow, 2 Run on Staging, Dev or Production](https://mintcdn.com/testspriteinc/IV-iejaf59JAQSCI/images/ui-testing-agent-environment-pick.png?fit=max\&auto=format\&n=IV-iejaf59JAQSCI\&q=85\&s=a38de84bc0470b102c0ee77d3eed93a1)

> [!NOTE]
>
> **Local addresses can't be reached.** The agent's browser runs in the cloud, so `localhost` and private addresses don't work. Use a public staging address, or set up the [CLI](https://docs.testsprite.com/cli/getting-started/overview.md) to test a local app.

## Who Can Do What

Asking the agent needs edit access to the project. Viewers can browse projects and results, but can't create a project, message the agent, or confirm its cards.

## Troubleshooting

> [accordion] The agent tested my app signed out
>
> The environment has no sign-in. Add a test account (<kbd>+</kbd> → <kbd>Test Account</kbd>), or tell the agent how users sign in and let it set the environment up.

> [accordion] My login sends a one-time code
>
> Tell the agent. It signs in with a TestSprite-managed account and reads the code from that account's inbox. If the code goes somewhere only you can read, such as your phone, the agent asks you for it.

> [accordion] My app signs in with Google or another SSO
>
> A stored username and password can't drive these, and a TestSprite-managed account can't use them. Use a [saved sign-in](#saved-sign-ins-manual-login): sign in once yourself in the browser panel, tell the agent, and sessions and runs reuse it until it expires.

> [accordion] The agent is waiting and I can't send a message
>
> A card above the chat box is waiting for your decision. Only one waits at a time; answer it, and the chat box opens again.

> [accordion] I changed my mind about the proposed project
>
> Click <kbd>Not Now</kbd> and tell the agent what to change, or edit the name, type, address and test account yourself on the Setup tab before you create it.

## Where to Go Next

> [card] [Exploration & Notes](https://docs.testsprite.com/web-portal/core/ui/agent-exploration.md)
>
> Watch the agent walk your app, and read what it learned

> [card] [Proposed Test Cases](https://docs.testsprite.com/web-portal/core/ui/agent-plan.md)
>
> Review the plan the agent proposes, then apply and run it

> [card] [Environments](https://docs.testsprite.com/web-portal/setup/environments.md)
>
> Addresses, accounts and variables for every environment

> [card] [Credentials Setup (API)](https://docs.testsprite.com/web-portal/core/api/agent-credentials.md)
>
> The API equivalent: tokens, keys and sign-in flows


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.