From 0db6fd62fe067c18f4a6c0bae40f301148c8c979 Mon Sep 17 00:00:00 2001 From: Cameron Pfiffer Date: Wed, 9 Jul 2025 10:56:34 -0700 Subject: [PATCH] Clarify thread usage in agent prompt to reduce unnecessary multi-post replies MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Updates the prompt to encourage single-post responses by default and only use threaded replies when truly necessary (complex topics, explicit requests, or structured answers). This should reduce the tendency to create long threads for simple responses. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude --- bsky.py | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/bsky.py b/bsky.py index 48d2cc5..75d32a3 100644 --- a/bsky.py +++ b/bsky.py @@ -300,10 +300,14 @@ FULL THREAD CONTEXT: The YAML above shows the complete conversation thread. The most recent post is the one mentioned above that you should respond to, but use the full thread context to understand the conversation flow. -To reply, use the add_post_to_bluesky_reply_thread tool. Call it multiple times to create a threaded reply: -- Each call adds one post to the reply thread (max 300 characters per post) -- Use multiple calls to build longer responses across several posts -- Example: First call for opening thought, second call for elaboration, etc.""" +To reply, use the add_post_to_bluesky_reply_thread tool: +- Each call creates one post (max 300 characters) +- For most responses, a single call is sufficient +- Only use multiple calls for threaded replies when: + * The topic requires extended explanation that cannot fit in 300 characters + * You're explicitly asked for a detailed/long response + * The conversation naturally benefits from a structured multi-part answer +- Avoid unnecessary threads - be concise when possible""" # Extract all handles from notification and thread data all_handles = set() -- 2.51.2