Repository navigation
Conversation
…output Long tool results and terminal-command output are previewed so one result cannot flood the transcript, but the hidden remainder was unreachable without exporting the session (issue huggingface#730). The full text is now retained per item and rendered on demand: - ChatItem keeps the full text when the preview was actually lossy - Ctrl+O, which already expanded tool results, renders the untruncated text too - --show-full-output starts the TUI with expansion on; it is per-invocation Preview defaults are unchanged, so nothing grows unless asked for. The terminal-command path (app.py:5840) now retains its untruncated output as well. Docs updated under website/content/.
PerryLink
force-pushed
the
feat/tui-show-full-output
branch
from
September 21, 2026 15:09
c20ff3f to
d3b917b
Compare
This branch has not been deployed
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.
Closes #730.
What
Long tool results and terminal-command output are previewed (
[Preview only: …],src/tau_coding/tui/state.py:924) so one result cannot flood the transcript — but the hidden remainder was previously unreachable without exporting the session.This adds both things the report suggested:
--show-full-output— start the TUI with expansion on (per-invocation, not durable)How
Full text is retained per item (
ChatItem.tool_result_full_text) and only when the preview was actually lossy, so memory does not grow for short results. Rendering goes throughChatItem.result_text(expanded=…), and the flag threadscli.py→run_tui_app→TauTuiApp→TuiState.Preview defaults are unchanged — nothing expands unless asked for. The
!-command path (app.py:5840, capped at 120 lines / 2000 chars) now retains its untruncated output too.Files: 8 (+432/−20), including
tests/test_tui_full_output.py(14 tests) and docs underwebsite/content/.Verification
uv run pytest tests/test_tui_full_output.py→ 14 passedgit stash, same files): Windows-only sidebar path/editor issues, drive-letter casing, and%formatting in print-mode prompts. Zero regressions.uv run ruff check .→ All checks passed ·uv run ruff format --check .→ 196 files already formatteduv run mypy→ 14 errors, all pre-existingfcntl.flockon Windows, none in the changed filesOne caveat on methodology: the full suite is resource-flaky in this environment (52 vs 29 failures across two identical runs, killed early), so the no-regression claim rests on the controlled stash-vs-changed comparison above rather than on a full-suite count.