> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/models/work-in-the-app/ai/mentions.md).
# @Mentions & Context
@mentions let you tell the AI exactly which elements you want to work with, so it doesn't have to guess. They're the fastest way to get a precise result in a busy diagram.
## How to Use @Mentions
1. Type `@` in the chat input.
2. A list of available diagram elements appears as a dropdown.
3. Use the **arrow keys** to navigate and **Enter** or **Tab** to select.
4. The selected element is inserted into your message as a highlighted chip. You can add multiple mentions in a single message.
> 
## Referencing Your Selection
If you already have elements selected on the canvas, type `@Selected` to reference all of them at once — no need to mention each by name:
* *"@Selected change the color to red"*
* *"@Selected connect these nodes with curved links"*
* *"@Selected group into a boundary called 'Core Services'"*
`@Selected` always reflects what's currently highlighted on the canvas at the moment you send the message.
## When to Use @Mentions vs. Plain Text
| Use @mentions when... | Use plain text when... |
| ------------------------------------------------ | ----------------------------------------------------- |
| The element name is long, generic, or ambiguous | The element name is unique and easy to type |
| You want to reference multiple specific elements | You're creating new elements (nothing to mention yet) |
| You have a selection and want to act on it | You're asking a general question about the board |
## Related
* [AI Chat](/models/work-in-the-app/ai/chat.md) – The main chat panel
* [Reviewing & Staging Changes](/models/work-in-the-app/ai/staging.md) – How proposed changes appear on the canvas
---
# 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.ins-pi.com/models/work-in-the-app/ai/mentions.md?ask=&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.