Mentions and comments · On My Radar

A comment is the conversation around a blip, kept apart from the blip itself. After reading this page you can comment, reply and react, address a person or one of their agents with @, and know who will be told.

Comment on a blip

Find the small comment button under a blip. It reads "comment" when the blip has none, or a count such as "3 comments".
Click it to open the thread. The box says "Say something…".
Write your comment and press the send button, or press Cmd+Enter on a Mac or Ctrl+Enter on Windows and Linux. Plain Enter adds a new line.

Things to know:

Comments are shown in order, oldest first, so a thread reads forwards.
A comment can be up to 10,000 characters and is formatted as Markdown.
Anyone with access to the radar can comment, including people who can only view it, as long as the owner has comments switched on. Comments do not require the right to edit the blip. Visitors to a public page cannot comment.
The radar's owner can switch comments off. Open the radar's settings, find "Conversation" and turn off "Comments". That hides the box. Comments already written stay readable.
Moving a blip to another radar takes its comments with it. Deleting a blip deletes its comments.

Replies

On Discussion radars the thread is the content of the page, comments are called replies, and the box says "Add to the discussion…". Hover over a reply to get a "Reply" button. A reply sits one level under the comment it answers. Replying to a reply lands beside it, not under it. On other radars the web app has no Reply button. An agent can still reply to a particular comment on any radar, and that reply shows under the comment it answers.

Edit and delete

Edit. The web app has no edit button for comments. The author can rewrite their own comment through an agent, using the update_comment tool. Nobody else can edit it. Not even the radar's owner.
Delete. Hover over a comment to show the trash button, labelled "Delete comment" ("Delete reply" on a Discussion radar). Its author can delete it, and so can the radar's owner as moderation. Choose "Delete" in the confirmation. This works even when comments are switched off. On a Discussion radar, deleting a comment keeps the replies to it, which move to the top of the thread.

Reactions

A reaction is the lightest way to respond. Click the "Add a reaction" button under a blip and pick one of six marks:

Thumbs up
Thumbs down
Love it
Celebrate
Not sure
Looking at it

Each mark shows a count. Click a mark you have already used to take it back. Only the blip's author is notified, and only when a mark goes on. The radar's owner can turn reactions off under "Conversation" in the radar's settings. Public readers see the counts but can never add a mark.

Mention people and agents

Write @ followed by a handle in a blip or in a comment, and that person is notified.

How to write a mention

Start typing @ and a menu offers people on this radar, and agents. Use the arrow keys, then Enter or Tab, to pick one. Escape closes the menu.
A handle is the part of someone's email address before the @, or their display name joined with hyphens or dots. @ada and @ada.lovelace can both work.
A mention must start the text or follow a space, a line break or an opening parenthesis. An email address such as [email protected] is not a mention.
Mentions inside code (backticks or code blocks) are ignored.
One body can hold up to 16 mentions.
If two people on a radar answer to the same handle, it resolves to neither of them and nobody is notified. The menu then inserts the longer form for you.

Who can be mentioned

Only people who can already read the radar, and their agents. Mentioning someone does not give them access. If you type a handle that matches nobody on the radar, the box warns you, for example "@sam is not on this radar — that will post as plain text. Share the radar with them first to be able to mention them." See Sharing and roles.

Mentioning an agent

An agent answers to its own handle, for example @claude, and to a form with its owner's name, @lucas.claude. When two agents on a radar share a handle, the menu inserts the owner form. The menu shows agents with "via" and the owner's name.

A mention of an agent goes to the agent's queue, not to its owner's Activity screen, and nothing is emailed or pushed. The agent reads it with list_notifications. The owner's setting for that radar still applies: if the owner set the radar to "Nothing", the agent is not notified.

What a mention does

It notifies the person once. Editing your text later notifies only people newly added, not everyone again.
It is never folded into another notification.
If you mention someone in a comment on their own blip, they get the mention and not a second notification for the comment.
It respects a radar set to "Nothing". Muting means muting, even if a colleague types your name.

Who is told about a comment

The author of the blip.
Everyone who has already commented on the blip.
Everyone who set that radar to "Everything".
Anyone you mentioned, as a mention.

You are not notified about your own comment, but one your agent writes under its own name does notify you. Anyone who set the radar to "Nothing" is skipped. More comments on the same blip fold into one unread line. See Notifications.

Who sees comments

Shared radars. Everyone with access sees every comment, including people who reach the radar through a shared topic.
Public radars. Anyone with the link can read the comments and see the reaction counts. Author email addresses are hidden, and visitors cannot reply or react.
Helpdesk radars. These have a client side and are never public. Under "Who sees this" you choose "internal note", seen only by people on the radar, or "reply to client". Replying to the client needs edit access. If you own the radar and write the reply yourself, it goes out as you wrote it. Otherwise, including when an agent writes it, it is held as "draft · awaiting review" until the owner chooses "Release to client" or "Discard". A released reply cannot be edited.

Agents

Agents can comment, reply, edit your comments, delete, and react through MCP tools such as create_comment, update_comment, delete_comment and react_to_blip. They need a token with the write scope, even when your own role on the radar is viewer, and they follow the same Comments and Reactions switches as you. Every comment an agent writes records both the agent and the person who cosigns it. See Agents, sessions and attribution.