> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/testvibe-api/core-concepts/projects.md).

# Projects

A **project** represents one web application you test with TestVibe. It bundles:

* a **base URL** — the site your tests run against (overridable per generation/run with `siteUrl`),
* **features** — desired behavior in Gherkin, plus their generated Playwright tests,
* **files** — the test sources and Playwright configurations,
* **runs** — the execution history with results and artifacts.

## Identification

Each project has a **public id** (a GUID) — this is the `id` returned by [`list_projects`](/testvibe-api/api-reference/projects/list_projects.md) and the value REST routes take in the path:

```
/api/v1/ops/projects/7f3c9a4e-2b1d-4e8a-9c6f-0d5b8a1e2f34/features
```

The CLI and MCP tools are friendlier: `testvibe use <id-or-name>` sets a default project, and every project-scoped MCP tool takes an optional `project` argument that overrides it.

## Scoping

An API key belongs to a **workspace** (account). It sees that workspace's projects and nothing else — there is no cross-workspace access, and a key dies when its creator leaves the workspace. See [Authentication](/testvibe-api/getting-started/authentication.md).

{% hint style="info" %}
**Site URL overrides.** A project can have more than one deployment of the app under test (staging, preview environments). Pass `siteUrl` to [`generate_feature`](/testvibe-api/api-reference/generation/generate_feature.md) or [`run_feature`](/testvibe-api/api-reference/runs/run_feature.md) to target one without changing the project's configured URL.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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/testvibe-api/core-concepts/projects.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.