Detailed Analysis
A Reddit user in the r/ClaudeAI community raised a practical question about Claude's interface: whether there is an official name for the interactive prompts Claude sometimes generates mid-session that present the user with a set of discrete choices to shape subsequent output, and whether there are limits on how frequently or extensively this feature can be invoked. The poster's underlying goal was to build a highly detailed planning document by having Claude surface a structured series of multiple-choice or short-answer questions, effectively using Claude as a guided intake form rather than a freeform chat partner. They noted difficulty replicating this behavior reliably through prompting alone, particularly when the number of required questions grew large.
This question touches on a feature set that Anthropic has been quietly expanding across its product surface: structured elicitation, where Claude pauses a task to ask the user for clarifying input through a constrained, easy-to-answer format rather than an open-ended paragraph. In Claude Code and the Claude Agent SDK, this pattern shows up formally as tools like "AskUserQuestion," which let a model pose a question with a fixed menu of options during an agentic workflow, and "plan mode," which asks Claude to draft a structured approach and confirm details before executing multi-step work. In the consumer Claude.ai product, similar behavior can emerge more informally, with Claude offering bulleted options or checkboxes inside a conversation or an Artifact, especially when guided by instructions that explicitly request iterative, checklist-style clarification. However, there is no single, universally documented "name" for this behavior across every surface, which is likely why the poster struggled to find consistent terminology or replicate it on demand — the capability is somewhat fragmented depending on whether one is using Claude.ai, Claude Code, or the API with custom tool definitions.
The difficulty the poster describes — losing the structured-choice format when there are many questions to work through — reflects a real limitation of relying on natural-language prompting to induce a UI-like interaction pattern that the model wasn't explicitly given a tool for. Without a formal mechanism (like a defined "ask_user_question" tool call with schema constraints), Claude tends to default back to prose-style responses as conversational complexity increases, especially once context grows crowded with multiple pending questions. This is a known friction point in agentic and conversational AI design more broadly: models are good at generating options when given a narrow task, but sustaining a multi-turn, multi-question intake flow purely through prompt engineering is brittle compared to using a purpose-built tool-calling interface designed for exactly that purpose.
More broadly, this thread is illustrative of how much of the practical knowledge around Claude's capabilities circulates through community trial-and-error rather than official documentation, particularly for edge-case workflows like building detailed planning documents through iterative Q&A. It also reflects a broader industry trend toward "structured interaction" as a design goal in LLM products — companies including Anthropic, OpenAI, and Google are all investing in mechanisms that let models ask clarifying questions with bounded answer sets, both to improve output quality and to reduce the cognitive load of open-ended prompting for end users. For someone in the poster's position, the more reliable path today is likely to use Claude Code or the Agent SDK with an explicit structured-question tool, or to draft a custom system prompt that forces Claude into a strict "ask one question at a time, wait for an answer" loop, rather than expecting the chat interface alone to sustain a long, structured intake session.
Read original article →