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]: Additional TUI Slots for Plugins #20504
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.
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.
Activity
github-actions commentedon Apr 1, 2026
This issue might be a duplicate of existing issues. Please check:
tui.footer.itemsplugin hook for persistent status display — proposes a specific plugin hook for injecting persistent status items into TUI slotsgithub-actions commentedon Jul 12, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
cavokz commentedon Aug 30, 2026
I opened a focused follow-up issue: #46268.
It narrows this request to a block-level
assistant_message_footerslot in the current TUI plugin API. The goal is to let plugins attach per-response metadata or render an expandable+ Turn detailsline 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.