Skip to content

feat: support structured follow-up questions/options in assistant output #23468

@ShirasawaSama

Description

@ShirasawaSama

Check Existing Issues

  • I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

  • I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

Many skills/workflows need to present users with follow-up questions or a small set of options after a response.
Today, users must manually type the next input, even when the model already “knows” the next suggested choices.
This creates extra friction, especially for guided flows where quick selection is more natural than free-form typing.

Desired Solution you'd like

Allow Open WebUI to detect and render structured follow-up content directly from model output.

For example, if the LLM output contains a dedicated tag/block (e.g. XML-like tag or JSON schema) describing follow-up prompts/options, the UI should render them as clickable chips/buttons below the message.

Image

Expected behavior:

  1. If structured follow-up tags are present, render interactive follow-up options.
  2. Clicking an option should send it as the next user input automatically.
  3. If no tags are present, keep current behavior unchanged.
  4. Keep this format optional and backward-compatible for existing skills/prompts.

This would make skill-driven conversations much smoother and reduce manual typing for users.

Alternatives Considered

This is especially useful for skills that naturally provide a small finite set of next actions (e.g. classify intent, choose a mode, pick a parameter range, select a troubleshooting path).
A simple standardized output contract (tag/schema) would enable reliable rendering and better interoperability across skills.

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    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