Skip to content

[FEATURE]: Allow plugins to add inline home footer status #48797

Closed

Description

@OpeOginni

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

TUI plugins can contribute to home.footer, but additive claims render as full-row siblings above or below the built-in footer. A plugin that needs a compact status indicator on the same row as the version must replace and duplicate the entire built-in footer, losing MCP and plugin health indicators.

Expose a nested home.footer.status slot inside the built-in horizontal footer row, after health indicators and before the flexible spacer and version. This would preserve all existing footer content while allowing plugins to add compact inline status components.

Activity

  1. github-actions commented on Sep 13, 2026

    @github-actions
    Contributor

    This issue doesn't fully meet our contributing guidelines.

    What needs to be fixed:

    • Feature requests must use the feature request template: the title should start with [FEATURE]: and include a verification checkbox confirming you searched for existing issues

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


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

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

  2. changed the title [-]Allow plugins to add inline home footer status[/-] [+][FEATURE]: Allow plugins to add inline home footer status[/+] on Sep 13, 2026
  3. github-actions commented on Sep 13, 2026

    @github-actions
    Contributor

    Thanks for updating the issue! It now meets our contributing guidelines. We appreciate the clear description of the problem and proposed solution.

  4. Hona commented on Sep 22, 2026

    @Hona
    Member

    Fixed by #48798 (feat(tui): add inline home footer slot), merged to v2 as 55e1b3e on 2026-09-14. Closing manually because v2 is not the default branch, so the PR did not auto-close this issue.

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