25 lines
1.2 KiB
Markdown
25 lines
1.2 KiB
Markdown
|
# Story: Collapsible Tool Outputs
|
||
|
|
|
||
|
|
## User Story
|
||
|
|
**As a** User
|
||
|
|
**I want** tool outputs (like long file contents or search results) to be collapsed by default
|
||
|
|
**So that** the chat history remains readable and I can focus on the Agent's reasoning.
|
||
|
|
|
||
|
|
## Acceptance Criteria
|
||
|
|
* [x] Frontend: Render tool outputs inside a `<details>` / `<summary>` component (or custom equivalent).
|
||
|
|
* [x] Frontend: Default state should be **Closed/Collapsed**.
|
||
|
|
* [x] Frontend: The summary line should show the Tool Name + minimal args (e.g., "▶ read_file(src/main.rs)").
|
||
|
|
* [x] Frontend: Clicking the arrow/summary expands to show the full output.
|
||
|
|
|
||
|
|
## Out of Scope
|
||
|
|
* Complex syntax highlighting for tool outputs (plain text/pre is fine).
|
||
|
|
|
||
|
|
## Implementation Plan
|
||
|
|
1. Create a reusable component for displaying tool outputs with collapsible functionality
|
||
|
|
2. Update the chat message rendering logic to use this component for tool outputs
|
||
|
|
3. Ensure the summary line displays tool name and minimal arguments
|
||
|
|
4. Verify that the component maintains proper styling and readability
|
||
|
|
5. Test expand/collapse functionality across different tool output types
|
||
|
|
|
||
|
|
## Related Functional Specs
|
||
|
|
* Functional Spec: Tool Outputs
|