Skip to content

[FEATURE]: Expose the current TUI model to plugins #42817

Closed as not planned
Closed as not planned

Description

@ugiya

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 render beside the prompt, but they cannot read the model currently selected for the next prompt. Session messages and model events only expose submitted or durable state, so plugin UI can remain stale after the user changes the model picker.

Could api.state expose a read-only accessor such as:

api.state.model.current():
  | { providerID: string; modelID: string }
  | undefined

This would project the same live Solid state used by the model picker and prompt submission. Reads inside plugin components or memos would update when the selection changes; reads outside a reactive scope would be point-in-time. It would return undefined until a valid model is available.

This would support model-aware prompt UI, context indicators, and provider-specific controls without switching or persisting the model.

I'm looking for design feedback on the API placement, return shape, and reactive contract before preparing a PR.

Activity

  1. github-actions commented on Oct 16, 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.

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