Repository navigation
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
brsbl
added this pull request to stack #4823
October 4, 2026 00:22
brsbl
removed this pull request from stack #4823
October 4, 2026 02:10
brsbl
changed the base branch from
bb/always-load-bb-tools-in-claude-code
to
bb/improve-how-agent-to-agent-messages-are-thr_4u5mgu9qe7
October 4, 2026 02:10
brsbl
added this pull request to stack #4834
October 4, 2026 02:10
Add the bundled Agent messages plugin with a bb_thread_message tool. An agent messages another thread, or answers one that messaged it, through the tool, and addresses the user in its normal response. The receiver already shows "Message from"; the sender now shows the tool call as a matching "Message to" chip outside the turn's work summary. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The thread id reached the SDK's unencoded URL path, so a crafted id could traverse to other loopback API routes or bypass the self-send guard. Accept only a single id segment, and render chips only for canonical thread ids. A side chat's forwarded message reads as an agent message in its main thread; refuse to message side chats so the main agent answers the user. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Tell agents the timeline already shows messages they send and receive, so they should not announce or restate them, and to prefer bb_thread_message over bb thread tell unless they need its options. Only lift successful or in-flight calls out of the work summary, so a failed attempt stays folded. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Collapse two or more settled agent-started exchanges into one Agent conversation row, skipping live, user-steered, pending, pinned, and side-chat exchanges. Explain in the tool's instructions what bb_thread_message and bb thread tell each offer, keep that out of the core bb-cli skill, and keep the tool result to delivery status. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Write the tool instructions as one short imperative paragraph like core bb tool guidance, listing only the bb thread tell options agents need. Keep GeneratedConversationMessage's existing layout, inline the side-chat check, and collapse overlapping test cases into tables. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Treat the live row and the first unread row as pinned, so one rule keeps those exchanges expanded instead of separate active-turn and divider handling. Render the Message to row in ThreadTimelineRows from its contexts like ConversationRow, and print grouped rows flat in CLI text. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
brsbl
force-pushed
the
bb/improve-how-agent-to-agent-messages-are-thr_4u5mgu9qe7
branch
from
October 4, 2026 02:39
258f7b7 to
a9f3fc9
Compare
brsbl
force-pushed
the
bb/roll-up-agent-conversations
branch
from
October 4, 2026 02:39
338dbef to
4aee2bd
Compare
The bb-guide introduction applies to every agent, so the exception for answering an agent now lives in the plugin's own instructions and the core line is unchanged. The tool refuses recipients that run with broader permissions than the sender, because bb tools skip the sender's approvals. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Collapse two or more settled exchanges started by other agents into one Agent conversation row that counts the agent messages exchanged. Exchanges that are live, unread, user-steered, pending, from a side chat, or targeted by search or navigation stay expanded. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
brsbl
force-pushed
the
bb/roll-up-agent-conversations
branch
from
October 4, 2026 03:19
4aee2bd to
270ddb6
Compare
brsbl
force-pushed
the
bb/improve-how-agent-to-agent-messages-are-thr_4u5mgu9qe7
branch
from
October 4, 2026 05:46
a96bc1e to
ec663e6
Compare
brsbl
removed this pull request from stack #4834
October 4, 2026 09:51
Collaborator
Author
|
Closing: we're dropping the roll-up. Each agent message already collapses to one line, and the roll-up hid the agent's answers to the user and re-rendered every timeline row on any thread change.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Human comments
What was wrong
When agents trade several messages, each exchange adds a "Message from" row, a "Message to" row, and the agent's reply to the receiving thread. In coordinating threads these back-to-back exchanges push the messages meant for the user out of view.
What changed
bb thread tell. The "Message to" rows need the Agent messages plugin.How you verified
270ddb63df: 31 checks passed and 3 were skipped.Before:
62a8531898. After:e81212789f. Captured before the stack was rebased onto mainc201f6490a; the rebase and the dropped Claude Code change don't touch the timeline. Same dev database, thread, and viewport, captured at 2×.BB-Thread-ID: thr_h86jusyw6k
🤖 Generated with Claude Code