fix: GitHub PR reviews now post single response instead of multiple comments (#94)

Skip intermediate acknowledgment messages ("Thinking...", "Processing...")
for Git platforms (GitHub, GitLab, Bitbucket) since they create new comments
instead of updating existing ones. This keeps PR threads clean.

- Chat platforms (Slack/Telegram/Discord) still show progress indicators
- Only final response is posted for Git platforms
- Updated docs with Git platform behavior section

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 4.5 <[email protected]>

Author: gouravjshah

CHANGELOG.md

@@ -12,6 +12,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - Changed from tracing (default level: error) to println for critical startup messages
   - Users can now see server bind address, registered platforms, loaded agents/flows
   - Error messages use stderr for proper output separation
+- GitHub/GitLab/Bitbucket PR reviews now post a single response instead of multiple comments
+  - Intermediate acknowledgment messages ("Thinking...", "Processing...") are skipped for Git platforms
+  - Only the final response is posted, keeping PR threads clean
+  - Slack/Telegram/Discord still show real-time progress indicators
 
 ## [0.3.1-beta] - 2025-12-26
 

crates/aof-triggers/src/handler/mod.rs

@@ -977,7 +977,12 @@ impl TriggerHandler {
         };
 
         // Auto-acknowledge if enabled
-        if self.config.auto_ack {
+        // Skip for GitHub/GitLab/Bitbucket - they create new comments instead of updating
+        let is_git_platform = matches!(
+            platform_impl.platform_name(),
+            "github" | "gitlab" | "bitbucket"
+        );
+        if self.config.auto_ack && !is_git_platform {
             let ack = TriggerResponseBuilder::new()
                 .text("Processing your request...")
                 .build();
@@ -1765,11 +1770,17 @@ impl TriggerHandler {
                 // Trigger the selected flow
                 info!("Triggering flow: {}", callback_value);
 
-                // Send acknowledgment
-                let ack = TriggerResponseBuilder::new()
-                    .text(format!("Running flow: *{}*...", callback_value))
-                    .build();
-                let _ = platform_impl.send_response(&message.channel_id, ack).await;
+                // Send acknowledgment (skip for Git platforms - they create new comments)
+                let is_git_platform = matches!(
+                    platform_impl.platform_name(),
+                    "github" | "gitlab" | "bitbucket"
+                );
+                if !is_git_platform {
+                    let ack = TriggerResponseBuilder::new()
+                        .text(format!("Running flow: *{}*...", callback_value))
+                        .build();
+                    let _ = platform_impl.send_response(&message.channel_id, ack).await;
+                }
 
                 // Execute the flow if we have a router
                 if let Some(ref router) = self.flow_router {
@@ -1896,11 +1907,17 @@ impl TriggerHandler {
             if let Some(flow) = router.get_flow(flow_name) {
                 info!("Executing flow '{}' for message: {}", flow_name, message.text);
 
-                // Send acknowledgment
-                let ack = TriggerResponseBuilder::new()
-                    .text(format!("🔄 Running {} flow...", flow_name))
-                    .build();
-                let _ = platform_impl.send_response(&message.channel_id, ack).await;
+                // Send acknowledgment (skip for Git platforms - they create new comments)
+                let is_git_platform = matches!(
+                    platform_impl.platform_name(),
+                    "github" | "gitlab" | "bitbucket"
+                );
+                if !is_git_platform {
+                    let ack = TriggerResponseBuilder::new()
+                        .text(format!("🔄 Running {} flow...", flow_name))
+                        .build();
+                    let _ = platform_impl.send_response(&message.channel_id, ack).await;
+                }
 
                 // Create FlowMatch and execute
                 let flow_match = FlowMatch {
@@ -1933,11 +1950,17 @@ impl TriggerHandler {
         if let Some(fleet_config) = self.available_fleets.get(fleet_name) {
             info!("Executing fleet '{}' for message: {}", fleet_name, message.text);
 
-            // Send acknowledgment
-            let ack = TriggerResponseBuilder::new()
-                .text(format!("{} Running {} fleet...", fleet_config.emoji, fleet_config.display_name))
-                .build();
-            let _ = platform_impl.send_response(&message.channel_id, ack).await;
+            // Send acknowledgment (skip for Git platforms - they create new comments)
+            let is_git_platform = matches!(
+                platform_impl.platform_name(),
+                "github" | "gitlab" | "bitbucket"
+            );
+            if !is_git_platform {
+                let ack = TriggerResponseBuilder::new()
+                    .text(format!("{} Running {} fleet...", fleet_config.emoji, fleet_config.display_name))
+                    .build();
+                let _ = platform_impl.send_response(&message.channel_id, ack).await;
+            }
 
             // Set user's fleet context
             self.set_user_fleet(&message.user.id, fleet_name);
@@ -2060,10 +2083,18 @@ impl TriggerHandler {
         self.add_to_conversation(&message.channel_id, thread_id, "user", &input);
 
         // Send typing indicator / acknowledgment
-        let ack = TriggerResponseBuilder::new()
-            .text("🤔 Thinking...")
-            .build();
-        let _ = platform_impl.send_response(&message.channel_id, ack).await;
+        // Skip for GitHub/GitLab/Bitbucket - they create new comments instead of updating existing ones
+        // This prevents noisy "Thinking..." comments in PR threads
+        let is_git_platform = matches!(
+            platform_impl.platform_name(),
+            "github" | "gitlab" | "bitbucket"
+        );
+        if !is_git_platform {
+            let ack = TriggerResponseBuilder::new()
+                .text("🤔 Thinking...")
+                .build();
+            let _ = platform_impl.send_response(&message.channel_id, ack).await;
+        }
 
         // Build the full input with conversation context
         let input_with_context = if conversation_context.is_empty() {
@@ -2326,11 +2357,17 @@ impl TriggerHandler {
 
         info!("Executing AgentFlow '{}' with input: {}", flow_name, input);
 
-        // Send typing indicator / acknowledgment
-        let ack = TriggerResponseBuilder::new()
-            .text(format!("🔄 Processing with flow `{}`...", flow_name))
-            .build();
-        let _ = platform_impl.send_response(&message.channel_id, ack).await;
+        // Send typing indicator / acknowledgment (skip for Git platforms - they create new comments)
+        let is_git_platform = matches!(
+            platform_impl.platform_name(),
+            "github" | "gitlab" | "bitbucket"
+        );
+        if !is_git_platform {
+            let ack = TriggerResponseBuilder::new()
+                .text(format!("🔄 Processing with flow `{}`...", flow_name))
+                .build();
+            let _ = platform_impl.send_response(&message.channel_id, ack).await;
+        }
 
         // Create AgentFlowExecutor
         let mut executor = AgentFlowExecutor::new(

docs/reference/daemon-config.md

@@ -475,6 +475,32 @@ The server exposes these endpoints for each platform:
 | Telegram | `https://your-domain/webhook/telegram` |
 | Discord | `https://your-domain/webhook/discord` |
 | WhatsApp | `https://your-domain/webhook/whatsapp` |
+| GitHub | `https://your-domain/webhook/github` |
+| GitLab | `https://your-domain/webhook/gitlab` |
+| Bitbucket | `https://your-domain/webhook/bitbucket` |
+
+---
+
+## Git Platform Behavior
+
+GitHub, GitLab, and Bitbucket handle responses differently from chat platforms:
+
+| Aspect | Chat Platforms (Slack/Telegram/Discord) | Git Platforms (GitHub/GitLab/Bitbucket) |
+|--------|----------------------------------------|----------------------------------------|
+| Response style | Real-time updates | Single response only |
+| Progress indicators | "🤔 Thinking...", "🔄 Processing..." shown | Skipped (would create noisy comment threads) |
+| Message updates | Can edit existing messages | Creates new comments |
+| Best for | Interactive conversations | PR reviews, issue triage |
+
+**Why single responses for Git platforms:**
+- Each `send_response` creates a NEW comment in GitHub/GitLab/Bitbucket
+- Progress indicators like "Thinking..." would flood PR threads with multiple comments
+- Only the final response is posted, keeping PR reviews clean and professional
+
+**Example: `/review` on GitHub PR**
+1. User posts `/review` comment on PR
+2. Bot processes (no intermediate comments)
+3. Bot posts ONE comment with the complete review
 
 ---