> For the complete documentation index, see [llms.txt](https://gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs/collaborate/comments.md).
# Comments
Ask questions to your team or receive feedback on the content you create
Comments allow you to provide feedback around specific pieces of content — without switching out of context from GitBook.
### Add a comment
You can open the comments panel by clicking on the **Comments** button in the [section header](/url/gitbook.com/docs/reference/gitbook-ui.md#space-header).
Adding a comment here will attach a comment to the entire page. You can also comment on a specific block by hovering over a block and clicking the content icon that appears on the right.
You can tag teammates by typing the `@` symbol followed by their name.
{% hint style="info" %}
Guests will be able to make comments but they will not be able to see or mention other users in the organization.
{% endhint %}
### Comment threads
You can reply to any comment to start a conversation with your teammates, turning it into a discussion thread.
You can also leave an emoji reaction on any comment by clicking the emoji button on the message or thread you’d like to react to.
### Resolving comments
If you’re done working through a comment thread or idea, you can **resolve** a comment at any time. Resolving a comment will hide it in the interface, but still keep it accessible in the ’Resolved’ tab of the section’s comments panel.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs/collaborate/comments.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 `build a script that syncs our docs to a CMS` 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.
