> 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/quickstart/create-or-connect-project.md).

# Create a Project

A project is created right in the app: give it a name and the URL of the site you want to test. No repository is required — all project content lives in TestVibe's cloud.

If this is the very first project on your account, TestVibe shows it to you automatically right after sign-in, as a single screen — there's no multi-step wizard and no repository-connect step here. Connecting a source repository is a separate, later step in **Settings → App Repository** (see below), not part of creating the project.

## Steps

1. Enter a project name.
2. Enter the base URL of the site you want to test — the address your tests will open.
3. Optionally, pick the target framework(s) so TestVibe can better read your app's UI (TestVibe also auto-detects on the first visit).
4. Create the project.

Creating a project is instant and free — it doesn't spend credits and doesn't probe the site. You land directly in the project on the Test Suite (Features) with the **Describe a flow** dialog open, ready to write your first test in plain English. See [Create your first test](/quickstart/create-first-test.md).

If you'd rather have TestVibe explore your live site and suggest tests to cover it, you can trigger that from the assistant at any time — it's optional, not automatic. See [Assistant](/assistant.md).

## Site URL

The site URL is the address your generated test will open.

Use a URL the cloud test session can reach. For example:

* a deployed test environment
* a staging environment
* a shared QA environment

If the app is private — behind a VPN or only reachable from your network — install the `tvtunnel` agent on a machine inside that network. See [Tunnel devices](/account-settings/tunnel-devices.md).

## Source Repository (Optional)

Once your project exists, you can connect a source repository from GitHub, GitLab, or Azure DevOps in **Settings → App Repository**. It helps the assistant and AI generation understand your app from the code, not just the rendered pages, and is read-only context — your tests and project files still live in TestVibe. Repository permissions are requested only when you connect a repo there — never at sign-in and never during project creation.

Test file sync (mirroring your generated tests two-way to a Git repo) is a separate setting — **Settings → Test Files Sync**.

## Project Settings

Project settings can control details such as:

* site URLs
* AI agent and model
* variables and secrets
* Playwright configurations

You can keep defaults for the quickstart and refine settings later. See [Configure site URLs and project settings](/workspace/configure-site-url-and-repository.md).

## Next

Continue to [Create your first test](/quickstart/create-first-test.md).


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.testvibe.com/quickstart/create-or-connect-project.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.