Feature: buffer outputs locally even when too large to include in context.

Summary

Claude Code should store large tool outputs (e.g., compiler error messages, logs) in a local
buffer or temporary file, rather than truncating them when they exceed size limits.

## Problem
Currently, when tools like Bash return large outputs (e.g., complete compiler error traces),
Claude truncates them (e.g., "... [480572 characters truncated] ..."). This results in lost
information that may be critical for debugging.

## Use Case
When debugging complex systems like Numba/CUDA code, error traces can be several megabytes in
size. These traces contain valuable debugging information, but they're currently truncated to
fit in the context window, making it impossible to see the complete error.

## Proposed Solution

1. Store complete tool outputs locally in a buffer or temporary file
2. Show a summary or initial portion in the UI
3. Provide commands to:

• View specific portions of the output
• Search within the complete output
• Analyze the full output without affecting context limits
• Export the full output to a file

## Benefits

1. Maintains all critical information for debugging
2. Doesn't impact token limits or context window size
3. Greatly improves debugging experience with verbose tools
4. Allows Claude to analyze the complete output when needed
5. Avoids having to rerun tests to retrieve omitted information

## Technical Considerations

• Local storage requirements should be minimal (a few MB per large output)
• Can use filesystem temporary storage or in-memory buffers
• Should have a retention policy or explicit cleanup mechanism

## Impact
This feature would significantly improve Claude Code's debugging capabilities, making it much
more effective for working with complex development tools.