[FEATURE]: Handle Progress Bars Gracefully #3950

Open
opened 2026-02-16 17:42:03 -05:00 by yindo · 1 comment
Owner

Originally created by @GameDungeon on GitHub (Dec 28, 2025).

Originally assigned to: @rekram1-node on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Pretty often command-line tools or scripts come with progress bars in them. While this is great for humans, this is pretty terrible for models as the context gets flooded with useless progress bar segments and the model does not even get to see the output of the command.

Possibly adding a buffer so that \r can be handled from commands before sending it to the model could prevent this.

Originally created by @GameDungeon on GitHub (Dec 28, 2025). Originally assigned to: @rekram1-node on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request Pretty often command-line tools or scripts come with progress bars in them. While this is great for humans, this is pretty terrible for models as the context gets flooded with useless progress bar segments and the model does not even get to see the output of the command. Possibly adding a buffer so that `\r` can be handled from commands before sending it to the model could prevent this.
yindo added the discussion label 2026-02-16 17:42:03 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Dec 28, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #6119: [Bug] TUI fails to render with raw ANSI output and critical memory leak (72.5G VIRT) on startup - Reports raw ANSI escape sequences flooding the terminal when processing output
  • #4239: TUI hangs when shell outputs massive log - Reports TUI freezing when commands output large amounts of data to stdout

Both issues are related to how OpenCode handles large or complex command output with ANSI sequences. Your feature request about buffering and handling carriage returns (\r) could help address these problems by preventing the context from being flooded with progress bar sequences.

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Dec 28, 2025): This issue might be a duplicate of existing issues. Please check: - #6119: [Bug] TUI fails to render with raw ANSI output and critical memory leak (72.5G VIRT) on startup - Reports raw ANSI escape sequences flooding the terminal when processing output - #4239: TUI hangs when shell outputs massive log - Reports TUI freezing when commands output large amounts of data to stdout Both issues are related to how OpenCode handles large or complex command output with ANSI sequences. Your feature request about buffering and handling carriage returns (\r) could help address these problems by preventing the context from being flooded with progress bar sequences. Feel free to ignore if none of these address your specific case.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#3950