Skip to content

[FEATURE]: Allow optional text qualifier when selecting a Question tool option - UX #17108

Closed

Description

@jn3ff

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

When using the Question tool, I tend to want to select a predefined option
and provide a short bit of context. Today my only choices are:

  1. Pick a canned option (no way to add detail), or
  2. "Type your own answer" (have to re-state the option + add my detail)

I've been annoyed by this routinely - building workflows in general on the premise of structured interactions, but a simple case where it's made the workflow feel downright bitter:

I've been cleaning up repos at my org and made a prune PR skill,
The agent asks me to triage a stale PR and I get:

  • Decline
  • Keep
  • Skip for now
  • Type your own answer:

I want to decline and note why ("superseded by PR #400"). Right now I
either:

  • pick Decline and lose the reason, or
  • type Decline, comment: superseded by PR xyz in the free-text box, hoping the
    agent parses it correctly.

I can ofc instruct the agent in the skill to interpret my choose own answer within a set of ways, but that feels indirect and non-deterministic (some instruction e.g. "if supplied is a decline reason, interpret as decline, if it's a question about the PR, enter a discussion"). It doesn't feel smooth to use. I just want to add a bit of context to my choice

Proposing that the key to "add user context" is

  1. not enter (I can't tell you the amount of times my stupid mouse cursor has slipped onto a non-insert question option, drawn the focus, and then enter submits it instead of entering the freetext window) - enter != submit when enter also = submit screws me up
  2. allowed on any of the answer options to supply additional context.

I looked over these two files to start to understand the current state of the question interaction
packages/opencode/src/cli/cmd/tui/routes/session/question.tsx
packages/opencode/src/question/index.ts
and would be happy to take a crack at a PR for this if it's not outright rejected in concept.

I did search for a while to see if this feature/request existed, I'm a little surprised it doesn't/hasn't been. Sorry if this is due to incompetence rather than reality.

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Mar 12, 2026
  2. added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on Mar 12, 2026
  3. github-actions commented on Mar 12, 2026

    @github-actions
    Contributor

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

    If your request differs in a meaningful way, please clarify how it's distinct from #8930.

  4. jn3ff commented on Mar 12, 2026

    @jn3ff
    Author

    Whoops. This is pretty much the same request. probably should have used /issues to search rather than doing my own.

    I do hope the 'enter' key feedback is taken as a datapoint.

    Closing this request.

  5. antonio-ivanovski commented on Oct 26, 2026

    @antonio-ivanovski

    Still needed. The important part is keeping the chosen option visible in the answer while attaching a qualifier; replacing it with a custom string throws away the structure the agent asked for. #48820 covers this plus a request-level comment, so that's the thread to watch. Auto-close for inactivity shouldn't be read as no demand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

coreAnything pertaining to core functionality of the application (opencode server stuff)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