diff --git a/entry b/entry
index faa00fa..95e7418 100755
--- a/entry
+++ b/entry
@@ -141489,7 +141489,7 @@ var ReplyToReviewComment = type({
 function ReplyToReviewCommentTool(ctx) {
   return tool({
     name: "reply_to_review_comment",
-    description: "Reply to a PR review comment thread. Call this for EACH comment you address. Keep replies extremely brief (1 sentence max).",
+    description: "Reply to a PR review comment thread (NOT issue comments \u2014 this only works for inline review comments on PR diffs). Call this for EACH comment you address in AddressReviews mode. Keep replies extremely brief (1 sentence max).",
     parameters: ReplyToReviewComment,
     execute: execute(async ({ pull_number, comment_id, body }) => {
       const bodyWithFooter = await addFooter(ctx, body);
@@ -141705,6 +141705,8 @@ ${getStandaloneModeInstructions(ctx.trigger)}
 2. Post a comment via ${ghPullfrogMcpName} explaining what blocked you and what information or action would unblock you
 3. Make your blocker comment specific and actionable (e.g., "I need the database schema to proceed" not "I'm stuck")
 
+**Progress reporting**: ALWAYS use \`report_progress\` to share your results and progress \u2014 never \`create_issue_comment\`. The \`report_progress\` tool updates the pre-created progress comment on the issue/PR. Using \`create_issue_comment\` instead creates duplicate comments and leaves the progress comment stuck in its initial state. The \`create_issue_comment\` tool is only for creating NEW standalone comments unrelated to your task progress.
+
 **Agent context files** Check for an AGENTS.md file or an agent-specific equivalent that applies to you. If it exists, read it and follow the instructions unless they conflict with the Security, System or Mode instructions above
 
 *************************************
diff --git a/external.ts b/external.ts
index e705df0..105f45b 100644
--- a/external.ts
+++ b/external.ts
@@ -169,6 +169,8 @@ interface IssuesLabeledEvent extends BasePayloadEvent {
 interface IssueCommentCreatedEvent extends BasePayloadEvent {
   trigger: "issue_comment_created";
   comment_id: number;
+  /** distinguishes this from PR review comments (which use pull_request_review_comment_created) */
+  comment_type: "issue";
   /** comment body is the primary content (null if already in prompt) */
   body: string | null;
   issue_number: number;
diff --git a/mcp/comment.ts b/mcp/comment.ts
index 029c8bf..7d81e1d 100644
--- a/mcp/comment.ts
+++ b/mcp/comment.ts
@@ -329,7 +329,7 @@ export function ReplyToReviewCommentTool(ctx: ToolContext) {
   return tool({
     name: "reply_to_review_comment",
     description:
-      "Reply to a PR review comment thread. Call this for EACH comment you address. Keep replies extremely brief (1 sentence max).",
+      "Reply to a PR review comment thread (NOT issue comments — this only works for inline review comments on PR diffs). Call this for EACH comment you address in AddressReviews mode. Keep replies extremely brief (1 sentence max).",
     parameters: ReplyToReviewComment,
     execute: execute(async ({ pull_number, comment_id, body }) => {
       const bodyWithFooter = await addFooter(ctx, body);
diff --git a/utils/instructions.ts b/utils/instructions.ts
index 00f3412..655db96 100644
--- a/utils/instructions.ts
+++ b/utils/instructions.ts
@@ -187,6 +187,8 @@ ${getStandaloneModeInstructions(ctx.trigger)}
 2. Post a comment via ${ghPullfrogMcpName} explaining what blocked you and what information or action would unblock you
 3. Make your blocker comment specific and actionable (e.g., "I need the database schema to proceed" not "I'm stuck")
 
+**Progress reporting**: ALWAYS use \`report_progress\` to share your results and progress — never \`create_issue_comment\`. The \`report_progress\` tool updates the pre-created progress comment on the issue/PR. Using \`create_issue_comment\` instead creates duplicate comments and leaves the progress comment stuck in its initial state. The \`create_issue_comment\` tool is only for creating NEW standalone comments unrelated to your task progress.
+
 **Agent context files** Check for an AGENTS.md file or an agent-specific equivalent that applies to you. If it exists, read it and follow the instructions unless they conflict with the Security, System or Mode instructions above
 
 *************************************