fix(tui): keep subagent labels in collab events#1
Open
iqdoctor wants to merge 1 commit into
Open
Conversation
0025288 to
d4b5392
Compare
d4b5392 to
cb07c2e
Compare
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
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.
What
Preserve subagent nickname/role metadata in collab agent tool-call state so TUI transcript rows can render readable labels such as
Hume [code-reviewer]instead of raw thread IDs.Why
Reference: openai#24581.
The
/agentspicker can show readable subagent labels, but live history rows likeSpawned ...andWaiting for 2 agentscan still fall back to UUIDs because the app-serverThreadItem::CollabAgentToolCallpath drops metadata before the TUI caches receiver threads.How
agentNickname/agentRoletoCollabAgentState.Validation
cargo fmt --allgit diff --checkLocal Rust test/check execution is blocked in this environment by missing OpenSSL development files:
Notes
External code contributions are by invitation only per
docs/contributing.md; this PR is opened as a concrete implementation reference for the linked bug report and can be closed if maintainers prefer to land an owner-authored fix.