AskUserQuestion for pi

Claude Code-style AskUserQuestion tool for the pi coding agent.

This package adds a global LLM-callable tool named AskUserQuestion. The tool lets the agent pause mid-task, ask structured questions in your terminal, and continue with your selected answers.

Features

• Ask 1–8 questions in one tool call
• 2–4 options per question
• Single-select radio choices
• Multi-select checkbox choices
• Auto-added Other... custom text input
• Optional per-answer notes with n
• Side-by-side preview panel for single-select visual/code comparisons
• Dedicated review/submit tab for multi-question dialogs
• Richer color states for focus, answered tabs, warnings, and review actions
• Arrow-key navigation, plus j/k
• Tab / Shift+Tab between questions
• Esc then Esc dismisses the dialog and returns control to chat
• Input validation before rendering

Install

From npm:

pi install npm:@mazli/pi-ask-user-question

From GitHub:

pi install git:github.com/HamdiMaz/AskUserQuestion

Pinned to a release tag:

pi install git:github.com/HamdiMaz/AskUserQuestion@v1.1.0

For a one-off test without installing:

pi -e npm:@mazli/pi-ask-user-question

or:

pi -e git:github.com/HamdiMaz/AskUserQuestion

After installing, restart pi or run:

/reload

Tool name

AskUserQuestion

What it returns

Normal result:

{
  "cancelled": false,
  "answers": {
    "Which HTTP client should we use?": "fetch (Recommended)",
    "Which resilience features do you want?": "Retry, Timeout"
  }
}

Cancelled or dismissed result:

{
  "cancelled": true
}

When the dialog is dismissed with Esc then Esc, pi returns to the chatbox without an immediate model follow-up so you can steer the conversation.

Agent usage guidance

Use AskUserQuestion when:

• There are 2–4 reasonable paths and the user's preference materially changes the result.
• The task is ambiguous and context is not enough to infer the answer.
• You want to recommend an option while still letting the user steer.

Do not use it for:

• Yes/no confirmation of risky actions. Use pi's permission or confirmation flow instead.
• Plan approval. Use the planning flow instead.
• Questions that can be reasonably inferred from project conventions or prior context.
• More than 8 questions at once. Use sequential calls instead.

Authoring rules:

• Ask 1–8 questions per call.
• Provide 2–4 options per question.
• Never include an Other option; the tool adds it automatically.
• If recommending an option, place it first and suffix the label with (Recommended).
• Keep header at 12 characters or less.
• End each question with ?.
• Use previews only for single-select visual/code comparisons.

Example tool input

{
  "questions": [
    {
      "question": "Which HTTP client should we use?",
      "header": "HTTP",
      "multiSelect": false,
      "options": [
        {
          "label": "fetch (Recommended)",
          "description": "Built-in and dependency-free."
        },
        {
          "label": "axios",
          "description": "Popular ecosystem and interceptor support."
        },
        {
          "label": "got",
          "description": "Node-focused with retry support."
        }
      ]
    },
    {
      "question": "Which resilience features do you want?",
      "header": "Resilience",
      "multiSelect": true,
      "options": [
        {
          "label": "Retry",
          "description": "Retry transient failures."
        },
        {
          "label": "Timeout",
          "description": "Apply a per-request timeout cap."
        },
        {
          "label": "Cache",
          "description": "Cache responses in memory."
        }
      ]
    }
  ],
  "metadata": {
    "source": "clarify"
  }
}

Local development

Clone this repo, then run pi with the extension directly:

pi -e ./extensions/ask-user-question.ts

Or install the local package:

pi install /absolute/path/to/AskUserQuestion

Then restart pi or run /reload.

Security

Pi extensions run with your local user permissions. Review any extension source code before installing it.

License

MIT