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

# Biodock Assistant

*What you'll get: an assistant inside Biodock that answers questions about your data and about how to use Biodock.*

The Biodock Assistant reads what you are looking at and answers in plain language: what an analysis found, how two groups compare, or where a setting lives. It only reads. It cannot start a run, or rename, move or change anything.

{% hint style="info" %}
The assistant is **off until you turn it on**, and turning it on only affects you. If you don't see **Assistant** in the sidebar, it is not available on your account yet. Contact <support@biodock.ai>.
{% endhint %}

## Turn it on

1. Click your name at the top right, then **My Account**.
2. Find the **AI features** card ("Off until you turn them on. Only affects you.").
3. Turn on **Biodock Assistant**.

<figure><img src="https://3806122466-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk3DfNQKoMy1JXdaDLvpG%2Fuploads%2Fgit-blob-d226cfa7d3e53575aafbcd8def56ffccd89edf2e%2Fdocs-assistant-turn-on.png?alt=media" alt="The AI features card on the Account page, with the Biodock Assistant and MCP access switches."><figcaption><p>The <strong>AI features</strong> card on <strong>My Account</strong>.</p></figcaption></figure>

The same switches are on the last slide of the assistant's introduction on **Home**.

## Ask a question

You can ask from two places:

* **Home**: type into the ask bar at the top of the page and press Enter. **Open Assistant** opens the full assistant.
* **Assistant** in the sidebar: the full page, with your earlier conversations.

<figure><img src="https://3806122466-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk3DfNQKoMy1JXdaDLvpG%2Fuploads%2Fgit-blob-0b3dee3ccc1e18c180e67bc24852bcec96c42428%2Fdocs-assistant-ask.png?alt=media" alt="Home with a question typed into the ask bar, the suggested questions below it and Open Assistant on the right."><figcaption><p>The ask bar on <strong>Home</strong>. <strong>Open Assistant</strong> opens the full assistant.</p></figcaption></figure>

Good questions name the thing you mean: "How many nuclei per image did the Control group have in my latest analysis?" or "Where do I change a model's prediction threshold?". When an answer comes from the documentation, the assistant links the page it used.

## In a workspace

Inside a workspace, the assistant can answer from the Biodock documentation. It can't read the workspace's files, analyses, projects or molecules yet, or anything in your personal account.

Answers asked in a workspace are paid from the workspace's credits. Each answer shows what it used. See [Credits, storage and billing](https://docs.biodock.ai/workspaces/workspaces/credits-storage-and-billing.md).

Owners and admins can turn the assistant off for a whole workspace in **Settings** with **Ask Biodock assistant**. When it is off, nobody can ask it in that workspace. See [Workspace settings](https://docs.biodock.ai/workspaces/workspaces/workspace-settings.md).

## Related

* [Connect Claude or ChatGPT](https://docs.biodock.ai/assistant/connect-claude-or-chatgpt.md): use Biodock from your own AI assistant.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.biodock.ai/assistant/biodock-assistant.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
