Skip to content

[FEATURE]: Plugin Hooks for spawning dialogs #9911

Closed

Description

@ShamanicArts

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

OpenCode already has inline & modal dialogs with permissions, questions & command pallet / models modal.

Plugins should be able to hook into the same primitives to create custom modals, inline dialogs, alerts etc. this would allow plugin developers to create native feeling interactions beyond just modifying & or tracking messages.

this could be done by extending the plugin hooks & api to provide hooks for the creation of dialogs.

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Jan 22, 2026
  2. github-actions commented on Jan 22, 2026

    @github-actions
    Contributor

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

    Feel free to ignore if none of these address your specific case.

  3. grota commented on Feb 3, 2026

    @grota
    Contributor

    I am strongly in favor of this feature request.

    Use case: I may be in the minority, but I actually read the messages and the code the models produce 😏, and they sometimes include useful pearls of wisdom. This happens even more often when I use opencode for non-code questions.

    I would like to be able to interactively tag assistant messages (for example, via a DialogMessage) with a "favorite" or "read it later" tag.

    I believe the missing piece is allowing plugins to hook into the UI components (for example, to add components/commands to packages/opencode/src/cli/cmd/tui/routes/session/index.tsx).

    Once that’s possible, a plugin could:

    • provide a TUI ui component (DialogMessage where the user can choose which tag to apply).
    • trigger, on selection, a plugin-specific event (for example, experimental.<plugin_name>.message.tagged)
    • react to that event itself or delegate to other plugins (avoid hardcoding behavior in opencode core).
  4. ClementGayet commented on Feb 17, 2026

    @ClementGayet

    +1

  5. github-actions commented on Apr 19, 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

discussionUsed for feature requests, proposals, ideas, etc. Open discussion

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions