> 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/using-context-fabric-with-the-orchestrator.md).

# Using Context Fabric with the Orchestrator

Two things have to be true for an Orchestrator agent to use Context Fabric: the MCP tools have to be available to it, and it has to know where the upfront context lives.

## MCP tools

Tick the `context-fabric` capability in the agent's configuration. That is the whole step: every agent with the capability gets the MCP tools, and authentication is handled for you.

![The context-fabric capability ticked in an Orchestrator agent's configuration](https://1398155133-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FED9nLcXxDQR0x7nt8zMS%2Fuploads%2FKnuYl8VmqVh413nZEj4O%2Fagent-capabilities.png?alt=media)

## AGENTS.md

The generated `AGENTS.md` is written to a shared disk, which is mounted automatically for each flow run. The agent still has to be told where it is.

{% hint style="info" %}
**The project slug must be identical in the Orchestrator and in Context Fabric.** That pairing is how the shared drive contents are matched. A project created through the Control Plane is already consistent.
{% endhint %}

The contents of the shared disk are visible in the `Memory` view in the left-hand menu. With the [Wiki module](/visdom-context-fabric/user-guide/wiki-module.md) enabled, the wiki files are there too, alongside `AGENTS.md`.

![The shared drive for a project, holding the generated AGENTS.md next to the wiki](https://1398155133-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FED9nLcXxDQR0x7nt8zMS%2Fuploads%2FkWWNSgK1qXFliuUIyNNB%2Fshared-drive-files.png?alt=media)

To point the agent at the file, extend its system prompt through the `CLAUDE.md` section of the agent's configuration:

```markdown
@@project_workspace/AGENTS.md
```

![The CLAUDE.md section of an agent's configuration, pointing at AGENTS.md on the shared drive](https://1398155133-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FED9nLcXxDQR0x7nt8zMS%2Fuploads%2FcltBbfhsRCl9J3L6Jxy7%2Fagent-claude-md.png?alt=media)

The two `@` characters are doing different jobs. `@project_workspace` is an Orchestrator reference that resolves to the path of the shared drive. The leading `@` is the model's own directive to fetch the file and pull its contents into its context.

With the Wiki module enabled, the generated `AGENTS.md` also explains where the wiki is and how to browse it, so the agent takes it from there. The whole generated file can be previewed in the Context Fabric UI.


---

# 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/using-context-fabric-with-the-orchestrator.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.