From 6a984d86c44054bccf9ead18758c56ee5ee652ac Mon Sep 17 00:00:00 2001 From: "open-swe[bot]" <215916821+open-swe[bot]@users.noreply.github.com> Date: Fri, 8 May 2026 22:52:29 +0000 Subject: [PATCH] feat: add 10 more tips to the trace-reply rotation (#1283) * feat: add 10 more tips to the trace-reply rotation The TRACE_REPLY_TIPS pool only had 9 tips, so users mostly saw the same ones. Added 10 more grounded in actual features (review command, image attachments, GitHub-issue triggers, persistent sandboxes, OAuth fallback, etc.) so the rotation surfaces more of what open-swe can actually do. Co-authored-by: Johannes du Plessis <51395795+johannes117@users.noreply.github.com> * swap out 3 tips per review feedback Replaced the suggestion-blocks, sandbox-auto-recovery, and OAuth-fallback tips with three more practically useful ones: cross-posted Slack message resolution, the web_search tool, and the Linear ticket-management tools. Co-authored-by: Johannes du Plessis <51395795+johannes117@users.noreply.github.com> --------- Co-authored-by: open-swe[bot] Co-authored-by: Johannes du Plessis <51395795+johannes117@users.noreply.github.com> --- agent/utils/slack.py | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/agent/utils/slack.py b/agent/utils/slack.py index e075e874..66cb8701 100644 --- a/agent/utils/slack.py +++ b/agent/utils/slack.py @@ -701,6 +701,16 @@ TRACE_REPLY_TIPS: tuple[str, ...] = ( "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.", + "Send me `review ` in Slack and I'll spin up the reviewer agent to leave inline comments on that PR.", + "Pasting a GitHub URL into your message also works to point me at a repo — no `repo:` prefix needed.", + "Attach screenshots or images directly in Slack or Linear — I'll read them as part of the task context.", + "Tag `@openswe` on a Linear issue and I'll pull in the full title, description, and comment thread before starting.", + "I also pick up `@openswe` mentions in GitHub issue bodies and comments — not just on PRs.", + "On a GitHub PR, comment `@open-swe review` to trigger the reviewer agent and get inline review comments.", + "Each thread keeps a persistent sandbox — follow-up runs reuse the same workspace, so my context sticks around.", + "Paste a Slack message link from another thread and I'll fetch its content (and any images) as extra context.", + "Ask me to search the web — I have a `web_search` tool for finding docs, examples, and GitHub repos mid-task.", + "I can read, update, and create Linear issues directly — useful for filing follow-up tickets or linking work back to a project.", )