Skip to content

[FEATURE]: Additional TUI Slots for Plugins #20504

Closed as not planned
Closed as not planned

Description

@Joshua-Wright76

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

I wanted to create a plugin for opencode which shows an estimate of water and electricity usage before the subagents footer and after the message metadata footer, but the current plugin system doesn't have slots for those locations in the TUI. For that I'm going to make a PR adding a few new slots for plugins to use, including both of those that I mentioned and a few more as well.

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Apr 1, 2026
  2. added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    opentuiThis relates to changes in v1.0, now that opencode uses opentui
    on Apr 1, 2026
  3. github-actions commented on Apr 1, 2026

    @github-actions
    Contributor

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

  4. assigned and unassigned on Apr 26, 2026
  5. removed
    opentuiThis relates to changes in v1.0, now that opencode uses opentui
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on May 3, 2026
  6. github-actions commented on Jul 12, 2026

    @github-actions
    Contributor

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

  7. cavokz commented on Aug 30, 2026

    @cavokz

    I opened a focused follow-up issue: #46268.

    It narrows this request to a block-level assistant_message_footer slot in the current TUI plugin API. The goal is to let plugins attach per-response metadata or render an expandable + Turn details line after an assistant response, while preserving the default UI.

    The new issue explicitly references this discussion and #24376; this is a refinement of the original request, not an attempt to claim the broader idea is new.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions