Feature: Add toolOutputText theme color for customizing bash output #9331

Closed
opened 2026-02-16 18:12:12 -05:00 by yindo · 2 comments
Owner

Originally created by @olosegres on GitHub (Feb 14, 2026).

Originally assigned to: @thdxr on GitHub.

Currently bash command output uses the same text color as regular text. It would be useful to have a separate theme color for tool output, allowing users to distinguish command output from other text.

This adds toolOutputText as an optional theme color with fallback to text.

Originally created by @olosegres on GitHub (Feb 14, 2026). Originally assigned to: @thdxr on GitHub. Currently bash command output uses the same `text` color as regular text. It would be useful to have a separate theme color for tool output, allowing users to distinguish command output from other text. This adds `toolOutputText` as an optional theme color with fallback to `text`.
yindo added the needs:compliance label 2026-02-16 18:12:12 -05:00
yindo closed this issue 2026-02-16 18:12:12 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 14, 2026):

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

  • Issue title should start with [FEATURE]: (uppercase) not "Feature:"
  • The feature request template requires a verification checkbox confirming you've checked for duplicates - this appears to be missing
  • Consider providing more detail about the problem or use case you're solving with this feature request

Please edit this issue to address the above within 2 hours, or it will be automatically closed.


Additionally, this issue might be a duplicate of or related to existing issues. Please check:

  • #6831: How to get diff colors in custom tool output
  • #258: [feat] support color output when invoke tools
  • #1708: Force colored output in shell tool adding env variable FORCE_COLOR=1
  • #13536: [FEATURE]: opencode run --colorize (very recent, Feb 13)

If you believe this was flagged incorrectly, please let a maintainer know.

@github-actions[bot] commented on GitHub (Feb 14, 2026): <!-- issue-compliance --> This issue doesn't fully meet our [contributing guidelines](../blob/dev/CONTRIBUTING.md). **What needs to be fixed:** - Issue title should start with **[FEATURE]:** (uppercase) not "Feature:" - The feature request template requires a **verification checkbox** confirming you've checked for duplicates - this appears to be missing - Consider providing more detail about the **problem or use case** you're solving with this feature request Please edit this issue to address the above within **2 hours**, or it will be automatically closed. --- Additionally, this issue might be a duplicate of or related to existing issues. Please check: - #6831: How to get diff colors in custom tool output - #258: [feat] support color output when invoke tools - #1708: Force colored output in shell tool adding env variable `FORCE_COLOR=1` - #13536: [FEATURE]: opencode run --colorize (very recent, Feb 13) If you believe this was flagged incorrectly, please let a maintainer know.
Author
Owner

@github-actions[bot] commented on GitHub (Feb 14, 2026):

This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new issue that follows our issue templates.

@github-actions[bot] commented on GitHub (Feb 14, 2026): This issue has been automatically closed because it was not updated to meet our [contributing guidelines](../blob/dev/CONTRIBUTING.md) within the 2-hour window. Feel free to open a new issue that follows our issue templates.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#9331