You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: Color the bash tool's command as shell code in the TUI #54700
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
The bash tool's command is drawn as plain text ($ command), while write, edit and apply_patch already color their code through tree-sitter. Bash is the most common tool call (about half of all tool calls in my sessions), and a long multi-line command with pipes, quoting and $(...) is much easier to scan colored. The bash parser is already registered in the TUI.
Proposal: render the command through <code filetype="bash">, plain at first and colored when the parser worker answers, with a tui.json switch to turn it off.
This is AI generated, but under direct supervision and on request of @Nowaker.
Thanks for the suggestion! You're asking for the bash tool's command in the TUI to be highlighted as shell code with tree-sitter, the same way write, edit and apply_patch already are. It would start plain, get colored once the parser answers, and have a tui.json option to turn it off. The maintainers will consider it.
Related items:
feat(tui): highlight Bash commands #42214: an earlier PR that rendered bash tool commands (and ! shell input) with <code filetype="bash">. It was closed without being merged.
Activity
opencode-agent commentedon Oct 12, 2026
Thanks for the suggestion! You're asking for the bash tool's command in the TUI to be highlighted as shell code with tree-sitter, the same way
write,editandapply_patchalready are. It would start plain, get colored once the parser answers, and have atui.jsonoption to turn it off. The maintainers will consider it.Related items:
!shell input) with<code filetype="bash">. It was closed without being merged.This can't be done as a plugin yet, because TUI plugins have no slot for rendering a tool's output in the session view.