feat: display subagent tool calls in CLI and UI#6535
Conversation
d4217c1 to
52e5ff6
Compare
jamadeo
left a comment
There was a problem hiding this comment.
this makes sense to me. I could see an argument that it might get too verbose, but let's merge it an if that's the feedback we get, we can scale it back
| arguments: Option<&JsonObject>, | ||
| debug: bool, | ||
| ) { | ||
| if tool_name == "code_execution__execute_code" { |
There was a problem hiding this comment.
any way we can avoid hard coding this? if the name changes it would be easy to miss
There was a problem hiding this comment.
Thanks @jamadeo, "code_execution__execute_code" and other tool names are hardcoded in other places in the codebase as well (e.g., in extension_manager.rs) and we probably have to change everywhere. I'll propose a followup to change them, if that works for you?
52e5ff6 to
c35da50
Compare
- Add notification forwarding from subagent to parent agent - Create tool call notifications for subagent ToolRequest messages - Add render_subagent_tool_call() to display tool headers in CLI - Add formatSubagentToolCall() helper in UI for consistent display - Use session ID suffix for unique subagent identification Signed-off-by: rabi <ramishra@redhat.com>
c35da50 to
c514681
Compare
|
@DOsinga Hey, when you've time, can you please check if this is something that's going to useful for UX perspective? Thanks. |
|
This is amazing, I was looking for something like this! |
|
I think it's a solid improvement in the subagent UX. If we need to allow turning down the verbosity, we can always add that in. |
Signed-off-by: rabi <ramishra@redhat.com> Signed-off-by: Harrison <hcstebbins@gmail.com>
Summary
Type of Change
AI Assistance
Testing
Tested locally with both cli and ui.