# Set Up Your Workspace

Your workspace connects TestVibe to the GitHub repository where test files, settings, workflows, and run evidence belong.

Most setup happens once per repository. After that, your team can create tests, generate Playwright code, and run the suite without repeating the connection steps.

## Setup Path

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Install the GitHub App</strong></td><td>Give TestVibe access to the repositories you want to use.</td><td><a href="/pages/qXffKdzuA8cnIjJrCbPM">/pages/qXffKdzuA8cnIjJrCbPM</a></td></tr><tr><td><strong>Choose a repository</strong></td><td>Select the repository where tests and workflows should live.</td><td><a href="/pages/xDeOAE7wBtKVZCcc8IaE">/pages/xDeOAE7wBtKVZCcc8IaE</a></td></tr><tr><td><strong>Create or connect</strong></td><td>Start a new TestVibe project or use an existing repository.</td><td><a href="/pages/Dmfrmb2QZrZR31qptfws">/pages/Dmfrmb2QZrZR31qptfws</a></td></tr><tr><td><strong>Configure settings</strong></td><td>Set the target URL, framework, AI agent, runner, secrets, and variables.</td><td><a href="/pages/OmsBY1OXulgZoZnkBH4o">/pages/OmsBY1OXulgZoZnkBH4o</a></td></tr><tr><td><strong>Open the dashboard</strong></td><td>Review repository health and decide what to inspect next.</td><td><a href="/pages/UcU5uBUvegDTXtZopaG5">/pages/UcU5uBUvegDTXtZopaG5</a></td></tr></tbody></table>

## What TestVibe Needs

| Requirement             | Why it matters                                                                     |
| ----------------------- | ---------------------------------------------------------------------------------- |
| GitHub sign-in          | TestVibe uses your GitHub identity to show installations, teams, and repositories. |
| GitHub App installation | The app grants repository access for generated files, settings, and workflows.     |
| Repository selection    | TestVibe needs one active repository as the workspace context.                     |
| Target site URL         | Generated and running tests need an application URL to open.                       |
| AI agent key            | Generation needs a configured provider key when your selected agent requires one.  |
| Runner access           | GitHub Actions needs a runner that can execute generation and test workflows.      |

## New Project Or Existing Project?

| Path                        | Use it when                                                                              |
| --------------------------- | ---------------------------------------------------------------------------------------- |
| Create a new project        | You want TestVibe to create a fresh GitHub repository and initialize the testing setup.  |
| Connect an existing project | You already have a repository and want TestVibe to use it for test assets and workflows. |

If you are unsure, choose the repository where your team expects the test files to live. Some teams keep UI tests beside the application code. Other teams keep a dedicated testing repository.

## Where To Go Next

If you are setting up for the first time, start with [Install the TestVibe GitHub App](/workspace/install-github-app.md). If the repository is already connected, review [Configure site URL and repository settings](/workspace/configure-site-url-and-repository.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.testvibe.com/workspace.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.