Comments and replies

Comments keep questions, evidence, decisions, and feedback attached to a task. Start a new comment for a new topic. Reply when you are continuing the topic under an existing comment.

Where comments appear

Task details provide three related tabs:

  • Activity shows comments, threaded replies, and task activity in one timeline. Use it to reply, react, edit or delete when permitted, and resolve a comment thread.
  • Chat is the Agent chat on the task. It is not a comment timeline. You can start it without first assigning an Agent or Crew. See Chat with an Agent.
  • Executions shows the task's run history separately from the comment timeline.

Write team-visible conclusions in comments or the task description. Messages in the task's Agent chat do not become Activity comments.

The Agent chat on a task does not read from or write to standalone Agent Chat sessions.

Start a comment or continue a thread

Use a new comment when the information should stand on its own, for example:

  • a new requirement, constraint, or acceptance condition;
  • a fresh review finding or decision;
  • a new set of logs, screenshots, or files;
  • an instruction for the task's Agent Assignee.

Use a reply when answering or extending an existing comment. Replies are attached to the top-level comment. If a reply targets another reply, Sharkly still keeps the thread at one level under its root comment.

Comment actions

Depending on your permissions, you can:

  • attach files and include mentions;
  • add or remove a reaction;
  • edit or delete a comment you are allowed to manage;
  • copy a comment or copy a full thread as a prompt;
  • resolve or reopen a top-level comment thread.

Only a top-level comment can be resolved. Resolving it collapses the thread in Activity. Reopen it before adding another reply.

Quick replies

Quick replies are personal saved responses available in comment and reply composers. Click the item text to send it immediately. Hover to show Insert, with the hint Edit the canned text before sending. Inserting writes the text into the composer and focuses it; it does not send. Edit the text, then send it yourself.

You can add, edit, reorder, and remove quick replies. They are stored per person, not shared with the team.

Copy an image from a comment or chat

Open the image preview in a task comment or Agent chat and select Copy image to paste it into another application that accepts images.

If copying is unavailable or fails, use the preview's download action to save the image instead.

When a comment starts an Agent run

A member's plain comment can start a run for the task's Agent Assignee when that Agent is available, the member is allowed to use it, and there is no duplicate pending run for the same task and Agent. On a task with a Crew Assignee, a plain member comment can start the Crew leader under the same availability requirement. These default comment triggers also apply on completed or canceled tasks.

The following rules prevent unintended runs:

  • A comment from the Agent itself does not start another default run for that Agent.
  • Mentioning a person or using @all does not by itself start an Agent run.
  • If a comment mentions other people, Agents, or Crews but does not mention the Agent Assignee, the default Assignee run is suppressed.
  • On a Crew-assigned task, any person, Agent, Crew, or @all mention suppresses the default Crew-leader run; explicit Agent and Crew mentions are evaluated separately.
  • A reply in a member-started thread does not start the Agent Assignee unless the reply or root comment mentions that Agent, or that Agent has already replied in the thread.

An explicit Agent or Crew mention can start the mentioned target even when it is not the task's Assignee. The target must belong to the organization, be available, be accessible to the member, and have no duplicate pending run for the task. A reply with no new mentions can continue an Agent or Crew mention from the member-authored root comment.

If a run is already active, a new eligible comment can be queued for the next run cycle rather than starting a parallel duplicate. Chat shows in-progress Agent output while the run is active, then replaces it with the persisted Agent comment when the run completes.

Keep durable requirements in the task

Use comments for discussion and follow-up context. Keep the stable goal, scope, and acceptance criteria in the task description so the current requirement remains easy to find.

Common questions