support for AskUserQuestion

Resolved 💬 2 comments Opened Mar 26, 2026 by muneermaher Closed Mar 29, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Summary
Claude Desktop supports uploaded plugins (skills) but lacks support for AskUserQuestion — the interactive tool that presents multiple-choice options as clickable buttons. Plugins that depend on gated workflows must fall back to plain text questions, degrading the user experience.

Context
I develop Research Studio, an academic research plugin with 8 commands and 10+ decision gates per workflow. In Claude Code CLI, AskUserQuestion presents options as a clean popup — the user clicks their choice and moves on. In Claude Desktop, the same gates produce a wall of text that the user must read and manually type a response to.

Current behavior
Claude Code CLI: AskUserQuestion renders as an interactive selection widget with 2-4 clickable options
Claude Desktop: Tool is unavailable. Plugins must fall back to embedding options in plain text and asking the user to type their choice
Requested behavior
Claude Desktop should support an interactive selection widget (equivalent to AskUserQuestion) that:

Displays a question with 2-4 options as clickable buttons
Returns the selected option to the conversation context
Works for uploaded plugins that define gated workflows

Why this matters
Plugins already run in Desktop — if Desktop supports plugins, it should support the tools plugins depend on
Reduces user friction — clicking a button is faster and less error-prone than reading a numbered list and typing a response, especially across 10+ gates in a single workflow

Minimal UI effort — Desktop already renders markdown, copy/retry buttons, and file uploads. A selection widget is a small addition

Consistency — the same plugin should behave the same way across Claude Code CLI and Claude Desktop

Workaround
Plugins can detect AskUserQuestion unavailability and fall back to text-based prompts. This works but is significantly less ergonomic for multi-gate workflows.

Proposed Solution

you should solve it easily

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗