> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/bug-reports/debug-a-capture/collaboration/comments.md).

# Comments

Comments keep feedback attached to the bug report.

Use them to discuss the captured evidence without moving to another thread.

### What comments are for

* Share findings tied to the capture.
* Ask follow-up questions.
* Add screenshots for extra context.

### Access

Logged-in workspace members can comment if they can access the bug report and are not watch-only.

Watch-only users can read comments and activity.

They cannot add, edit, delete, or react to comments.

### Add a comment

{% stepper %}
{% step %}

### Open the bug report

Go to the activity timeline below the capture.
{% endstep %}

{% step %}

### Start a comment

Select **Write a comment or @ to mention**.
{% endstep %}

{% step %}

### Post it

Add your message, then select **Comment**.
{% endstep %}
{% endstepper %}

You can attach images when extra visual context helps explain the issue.

### Edit or delete a comment

Comment authors can edit or delete their own comments. Workspace admins can manage comments when cleanup is needed.

Edited comments are marked as edited.

This keeps the timeline transparent.


---

# 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.screendesk.io/bug-reports/debug-a-capture/collaboration/comments.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.