[FEATURE] AskUserQuestion: Allow single option (since "Other" is always added)

Resolved 💬 2 comments Opened Jan 30, 2026 by ThomasHarper Closed Feb 28, 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

The AskUserQuestion tool currently requires a minimum of 2 options per question ("minItems": 2). However, since an "Other" option is always automatically appended, there are scenarios where only one predefined option makes sense.

For example, a confirmation prompt:

  • "Proceed with deployment" (single option)
  • "Other" (automatically added for custom input like "Wait, let me check something first")

Currently, this requires adding a second artificial option just to satisfy the schema, leading to awkward UX:

  • "Proceed with deployment"
  • "Cancel" (forced second option)
  • "Other" (auto-added, now redundant with Cancel)

Proposed Solution

Change the minimum options requirement from 2 to 1:

{
  "options": {
    "minItems": 1,  // Changed from 2
    "maxItems": 4,
    ...
  }
}

This acknowledges that "Other" always provides a second choice, so requiring 2 predefined options is unnecessary.

Alternative Solutions

  • Adding a dummy "Cancel" or "No" option - clutters the UI and creates redundancy with "Other"
  • Using natural conversation instead - loses structured input benefits
  • Rephrasing as yes/no questions with two options - sometimes the semantic doesn't fit binary choices

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

  1. Confirmation prompts: "Proceed?" → [Yes] + [Other for custom response]
  2. Recommended action: "Use recommended settings?" → [Yes, use recommended] + [Other to specify custom]
  3. Default selection: "Deploy to production?" → [Deploy now] + [Other for scheduling/concerns]

Additional Context

This is a small schema change that would provide more flexibility for plugin developers while maintaining backwards compatibility (existing 2+ option questions continue to work).

View original on GitHub ↗

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