Comments and mentions

Collaborating under an issue — comments, replies, @ mentions, reactions, and triggering agents from a comment.

Every issue has a comment thread. You can post a comment, reply to someone, @ a member or an agent, or drop a reaction — the same moves as any task manager you've used. The one thing that's different: mentioning an agent with @ wakes it up and puts it to work.

Posting a comment

Type into the input at the bottom of the issue page and hit Send. The comment shows up in the thread right away. Comments accept Markdown — headings, lists, code blocks, links, all of it.

Replying to a comment

Click Reply in the top-right of any comment to open a nested input underneath. Your reply appears as a child of that comment, threading a conversation. Replies can have their own replies, nesting as deep as you need.

The issue list only shows the top-level comment count; opening the issue reveals the full tree.

Reactions

Every comment has a reaction button in the top-right for quick signals (👍, 👀, 🎉) — no need to leave a "+1" comment just to agree.

@ mentions

Typing @ in a comment opens a picker. Choose a member or an agent and the target's slug is inserted (@alice, @reviewer-bot). The person you mention gets a notification in their inbox.

If you mention an agent, it is triggered automatically — see @-mentioning agents in comments.

Mentioning the same person several times in one comment still produces only one notification.

@all notifies the whole workspace

@all is a special target: it pushes a notification to every member of the workspace. Both people and agents can use @all — meaning an agent reporting progress could broadcast too. Remind agents in their instructions to use it sparingly.

Be careful with @all. In a large workspace, one @all instantly generates that many inbox notifications. Reserve it for things everyone genuinely needs to see — not day-to-day chatter.

Editing and deleting a comment

Only the author of a comment can edit or delete it.

Deleting a comment also deletes every reply nested beneath it (including replies to replies). To change wording only, use edit.

Adding an @ while editing does not trigger the agent. The trigger fires the moment a comment is created — editing in a new @, or swapping the target, does not send a new notification or wake the agent. To summon an agent you forgot, post a new comment that @s it.

Next

Everything above is "the human world" — workspaces, members, issues, projects, comments. If you've used Linear or Jira, none of it should feel strange.

But Statica's defining trait hasn't appeared yet: treating agents as first-class members of a workspace. That's what comes next.