> For the complete documentation index, see [llms.txt](https://docs.visdom.virtuslab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.visdom.virtuslab.com/visdom-control-plane/user-guide/projects-and-repositories.md).

# Projects and repositories

Creating projects, registering repositories and giving the products access to them.

## Creating a project

Only an admin can create a project. Choose the slug carefully: it cannot be changed later, it must be unique, and every product uses it in URLs and API calls. Lowercase letters, digits and hyphens, starting with a letter or digit, up to 63 characters.

Name and description can be edited later by an admin or by the project's Control Plane Operator.

Archiving hides a project from everyone who is not an admin and tells every connected product to stop working in it. There is no delete: history in the other products still points at the slug.

## Adding a repository

Open the project, then **Add repository**:

* **Name** – a slug, unique within the project.
* **Clone URL** – HTTPS. It cannot be changed after the repository is saved; register a new repository instead.
* **Branch** – the branch agents and indexing work from.
* **GitHub App installation ID** – for GitHub repositories where agents authenticate as the organisation's GitHub App. Orchestrator uses it to mint short-lived installation tokens and to commit under the app's identity.

The same URL and branch cannot be registered twice in one project.

## Repository authentication

Under **Repository authentication**, **Set token** stores one access token for all repositories in the project. **Replace token** rotates it. The token is encrypted and never displayed again; the UI shows only when it was set and by whom.

Context Fabric uses the token to read code. Agents working through a GitHub App do not need it.

## Testing the connection

The connection test calls the repository over git smart HTTP with the project token, without cloning, and reports the default branch it found. A failure does not stop you saving the repository: the token may be added later, or the network path may only exist from the cluster where the products run.

## What the other products see

Every change on this page – a new project, an archived one, a repository added, edited or removed – is sent to each connected product within seconds. If a product is down, the event waits and is retried until it arrives.


---

# 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.visdom.virtuslab.com/visdom-control-plane/user-guide/projects-and-repositories.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.
