# Repository settings

Repository settings control the active TestVibe project. They affect AI generation, the default site URL, source context, and the secrets used by the selected agent.

## Open repository settings

1. Load a repository workspace.
2. Open **Settings**.
3. Select **Repository**.

## Core repository fields

| Field                         | What it controls                                                  |
| ----------------------------- | ----------------------------------------------------------------- |
| Team                          | The GitHub team context for organization projects when available. |
| Project Name                  | The display name for the TestVibe project.                        |
| Default Test URL              | The target site URL used when generation or runs need a default.  |
| Website framework             | The application framework context given to AI generation.         |
| Application Source Repository | Optional repository containing the application under test.        |
| AI coding agent               | The agent TestVibe uses for generation work.                      |
| API Key                       | The selected agent's repository secret, such as `OPENAI_API_KEY`. |
| Project Description           | Helpful context for teammates and future generation.              |

## Default Test URL

Use a URL the selected runner can reach. A public staging or QA URL usually works with GitHub-hosted runners. Private, VPN-only, or internal URLs usually require a self-hosted runner.

Avoid `localhost` unless the app is running on the same machine as the runner.

## Website framework

The website framework helps TestVibe generate better Gherkin and Playwright code. Choose the closest option, such as Wisej.NET, Angular, React, Blazor, or Other.

## Application source repository

Use the source repository field when the application code lives in a separate repository from the TestVibe project. This gives generation better context while keeping the test project in the repository your team selected.

You can leave this field empty when the test repository already contains the application context you want TestVibe to use.

## AI agent and key

Choose the agent the project should use for generation. If the selected agent requires a key, enter it in the API key field and save. Existing secrets may show as `***`; saving without changing that placeholder keeps the existing secret.

For detailed key handling, see [API keys](/account-settings/api-keys.md).

## Related repository settings

Other settings pages also affect the selected repository:

| Page           | Use it for                                                           |
| -------------- | -------------------------------------------------------------------- |
| Secrets        | Store sensitive workflow values.                                     |
| Variables      | Store non-sensitive workflow values.                                 |
| Runners        | Choose the default GitHub Actions runner labels.                     |
| Configurations | Manage Playwright browser, viewport, evidence, and reporter presets. |
| Suggestions    | Configure repository suggestion inventory.                           |

For a broader setup walkthrough, see [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/account-settings/repository-settings.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.