feat(tui): show running tools and LLM status in sidebar #9655

Activity

1. github-actions

   assigned

   thdxr

   on Jan 20, 2026
2. github-actions

   added

   opentuiThis relates to changes in v1.0, now that opencode uses opentuiThis relates to changes in v1.0, now that opencode uses opentui

   on Jan 20, 2026
3. github-actions commented on Jan 20, 2026

   

   github-actionsBot

   on Jan 20, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • feat: Show background tasks status in sidebar #8322: Show background tasks status in sidebar - directly requests the same feature with task count badge and expandable list showing agent type, description, and elapsed time
   • [FEATURE]: Desktop app needs better visual feedback when working #8904: Desktop app needs better visual feedback when working - requests persistent, animated visual indicators showing when OpenCode is actively working
   • [FEATURE]: Show elapsed runtime per command / instruction in TUI + Replay #5872: Show elapsed runtime per command / instruction in TUI + Replay - requests elapsed time visibility for active commands/instructions
   • [FEATURE]: "Waiting for" indicator #7093: 'Waiting for' indicator - requests clearer indication of what the system is waiting for (LLM API response, MCP API response, local command)
   • [FEATURE]: progress indicator #3742: progress indicator - requests visual indicator showing whether response is in progress or finished
   • TUI should show when it is retrying #4089: TUI should show when it is retrying - requests visibility into retry status

   Feel free to ignore if none of these address your specific case.
4. R44VC0RP commented on Jan 20, 2026

   

   R44VC0RP

   on Jan 20, 2026

   Contributor

   More actions

   Thanks for the detailed proposal and mockup @Becktor! This addresses a real pain point - not knowing what's happening during long-running operations.

   A few related issues have been flagged:

   • feat: Show background tasks status in sidebar #8322 specifically asks for background task visibility in the sidebar
   • [FEATURE]: "Waiting for" indicator #7093 and [FEATURE]: Show elapsed runtime per command / instruction in TUI + Replay #5872 request "waiting for" indicators and elapsed time

   Your proposal is the most comprehensive of the bunch and includes a nice UI mockup. Since you mention you have a working implementation ready, would you be open to submitting a PR?

   A few things to consider for the PR:

   • The current SessionStatus types (idle, retry, busy) would likely need to be extended to capture the granular tool/LLM states you're proposing
   • The sidebar component (sidebar.tsx) is already structured with collapsible sections, so adding a "Running" section should fit well with the existing pattern

   Looking forward to seeing the implementation!
5. Becktor commented on Jan 20, 2026

   

   Becktor

   on Jan 20, 2026

   Last edited by Becktor

   Author

   More actions

   Hey thanks for the feedback!
   Yeah I already have a suggestion on how to get the granular states:

   edit: ended up extending the SessionStatus types instead. Was a lot cleaner.

   For running tools, I just look for ToolPart entries with state.status === "running" and check elapsed time against a 2 second threshold.
   The PR is ready: #9658

   ❤️React with ❤️1Reacted by Rene Leonhardt
6. Becktor

   added a commit that references this issue on Jan 20, 2026

   feat(tui): show running tools and LLM status in sidebar

   ...

   This issue will close once commit 164da0a is merged into the 'dev' branch.

   164da0a
7. Becktor commented on Jan 26, 2026

   

   Becktor

   on Jan 26, 2026

   Author

   More actions

   @R44VC0RP Hate to ping you just curious what the process is moving forward. I know there are a lot of PR's and issues coming in so if patience is required I'll just hang tight and wait.
8. R44VC0RP commented on Jan 26, 2026

   

   R44VC0RP

   on Jan 26, 2026

   Contributor

   More actions

   Hey, valid question.

   I can surface this to the team but I am a bit unclear why we actually need the agent1 agent2 statuses, would these be the subagents that a primary agent has started?
9. Becktor commented on Jan 27, 2026

   

   Becktor

   on Jan 27, 2026

   Last edited by Becktor

   Author

   More actions

   Yes correct! Let me update the screenshot to a gif of it running instead. (see above)
10. Becktor commented on Jan 29, 2026

    

    Becktor

    on Jan 29, 2026

    Author

    More actions

    @R44VC0RP Please let me know if I should refrain from pining you. However, I'm still not really certain what the process is to get this merged.
11. jaroslaw-weber commented on Feb 8, 2026

    

    jaroslaw-weber

    on Feb 8, 2026

    More actions

    please merge this, sometimes my agent get stuck and im not sure if its an issue on the provider side or sth else.

    👍React with 👍1Reacted by tedwards-sf
12. github-actions commented on Apr 9, 2026

    

    github-actionsBot

    on Apr 9, 2026 – with GitHub Actions

    Contributor

    More actions

    To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
13. github-actions

    closed this as completedon Apr 9, 2026
14. DerJJ commented on Jul 10, 2026

    

    DerJJ

    on Jul 10, 2026

    More actions

    I just came across this and are slightly disturbed why this was closed.

    Working in an air-gapped environment with on-site hosted models the sidebar is otherwise useless.
    This brings some fine value.

    I don´t understand why the reason for rejection was not commented?! Please be more transparent.