> 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-context-fabric/user-guide/setting-up-a-project.md).

# Setting up a project

The top-level unit of work in Visdom is a **project**, which can span multiple **repositories**. It is also the trust boundary: everything inside a project is assumed to be able to see all of that project's data.

In a full Visdom deployment, projects and repositories are defined in the Control Plane.

![The Control Plane's Projects view, where a project and its repositories are defined](https://1398155133-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FED9nLcXxDQR0x7nt8zMS%2Fuploads%2FgnE4Hz58YpTFeZ59Zzxw%2Fcontrol-plane-projects.png?alt=media)

Anything created there propagates automatically to Context Fabric, where it can be configured further.

![The same projects, propagated into Context Fabric and ready to configure](https://1398155133-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FED9nLcXxDQR0x7nt8zMS%2Fuploads%2FI3DKooSo73QYzXKtuxBX%2Fprojects-list.png?alt=media)

Selecting a project shows how to reach the project-specific MCP servers and how to fetch `AGENTS.md` over HTTP. Both require authentication. The same view lists the modules that are enabled.

![A project in Context Fabric: the MCP and AGENTS.md endpoints, the enabled modules, and the latest runs](https://1398155133-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FED9nLcXxDQR0x7nt8zMS%2Fuploads%2FgGn3LkCpyGVrNkjcTuOx%2Fproject-overview.png?alt=media)

## Modules

Several **modules** can be enabled for a project. Each contributes context, either as a fragment of `AGENTS.md` or as an MCP tool. With no modules enabled there are almost no MCP tools exposed, and the generated `AGENTS.md` is empty.

A module is enabled either globally for a project or individually for a repository, depending on the kind of information it maintains. Project-wide modules live under `Configuration` in the left-hand menu; repository-specific ones are configured by clicking a repository in that view.

![The Configuration page, with the project's slug and ID above the repositories it owns](https://1398155133-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FED9nLcXxDQR0x7nt8zMS%2Fuploads%2FJNAqkFXSWu526XhgUGDH%2Fproject-configuration.png?alt=media)

Enabling a module is a checkbox plus `Save`. Indexing then takes a while, so come back to the results rather than waiting on the page.

{% hint style="warning" %}
**Most modules cost money to run.** LLMs do the indexing. Each module page states its cost profile, and the `Runs` page shows spend in real time when filtered by project and module type. The Wiki and Repo insights modules are the two worth watching on a large codebase.
{% endhint %}

![The Runs page filtered by project and module, with what each run cost](https://1398155133-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FED9nLcXxDQR0x7nt8zMS%2Fuploads%2Fmq7zoTHTHY7yuKnAZKYN%2Fruns.png?alt=media)


---

# 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-context-fabric/user-guide/setting-up-a-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.