From 51bdde93b9f6430ebb0db052332a09cfe3c4543c Mon Sep 17 00:00:00 2001 From: Johannes du Plessis Date: Fri, 8 May 2026 14:59:14 -0700 Subject: [PATCH] slack: move feedback-reaction ask out of every reply, into the tip rotation (#1279) Appending "Please react with :+1: or :-1:..." to every Slack completion message ended up being repetitive noise. Drop the prompt-side instruction and add the same ask as one of the rotating tips on the trace reply, so users still see it occasionally without it cluttering each final summary. --- agent/prompt.py | 2 -- agent/utils/slack.py | 1 + 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/agent/prompt.py b/agent/prompt.py index cbcb53cf..246e6833 100644 --- a/agent/prompt.py +++ b/agent/prompt.py @@ -138,8 +138,6 @@ For tasks that require code changes, follow this order: **Strict requirement:** Never claim "PR updated/opened" unless `gh` returned success and you have the PR URL from command output or `GH_TOKEN=dummy gh pr view --json url --jq .url`. If push or PR creation fails, state that explicitly. -For Slack-triggered tasks, end your final `slack_thread_reply` completion summary by asking the user to react with `:+1:` or `:-1:` to provide feedback. - For questions or status checks (no code changes needed): 1. **Answer** — Gather the information needed to respond. diff --git a/agent/utils/slack.py b/agent/utils/slack.py index bac041f7..e075e874 100644 --- a/agent/utils/slack.py +++ b/agent/utils/slack.py @@ -700,6 +700,7 @@ TRACE_REPLY_TIPS: tuple[str, ...] = ( "Tag me on a PR comment of an open-swe PR to have me address review feedback on the same branch.", "I can spawn subagents for independent subtasks — useful for parallel research or fan-out work.", "Click `View trace` above to watch every tool call and model response live in LangSmith.", + "React to my final reply with :+1: or :-1: to share feedback — it helps me get better.", )