> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-tasks/how-to-use-comments-on-a-task.md).
# How to use comments on a task
This short tutorial goes through comments and notifications on tasks
### What are comments on a task?
Comments enable communication on tasks by allowing users to add notes or ask questions for future follow-up. It also serves as a way of logging changes to the task.
### How to add comments to a task
Inside the task details page, scroll down to the 'Comments'-section. Here you can add comments related to the task.
Inside the Task details page. You can navigate to this from the task overview.
{% hint style="info" %}
Updates regarding the task will automatically be added as a comment to the task. These include new deadlines, status, change of responsibility etc.
{% endhint %}
### Notifications
The creator of the task and assigned users will receive notifications in the Tasks menu whenever there is an update. It will create a notification badge on the task.
If there are any updates on a task, a notification badge appears.
---
# 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.struct.com/tutorials/guides/how-to-use-tasks/how-to-use-comments-on-a-task.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.
