AskUserQuestion shown as permission request instead of question form on mobile

[begna112]

Description

When using certain skills in YOLO mode, the mobile client shows AskUserQuestion tool calls with BOTH the correct question form (with selectable options) AND a generic permission dialog ("Permission required: AskUserQuestion") simultaneously. Interacting with the permission dialog instead of the question form dismisses the question without sending an answer.

Observed behavior

1. Both UIs appear — The question form renders correctly in the transcript (e.g., "What would you like to focus on?" with options), AND a permission footer appears above the text input area with Yes/No/Don't-ask-again buttons.

2. Answering the question form works — Selecting options and submitting through the question form works correctly, and the permission dialog also dismisses.

3. Answering the permission dialog breaks it — Tapping "Yes" on the permission footer calls sessionAllow() which resolves the permission without any answers. The question form is dismissed without the user's selection being sent. The agent receives an empty/approved result instead of the structured answers.

4. "Don't ask again" doesn't persist — Selecting "Yes, don't ask again for this tool" dismisses the dialog but the same dual-UI behavior repeats on the next AskUserQuestion call.

Root Cause

There are two separate locations that render PermissionFooter for pending permission requests:

Location 1: ToolView.tsx:441 — Correctly excludes AskUserQuestion

{isWaitingForPermission && toolForRendering.permission && sessionId &&
    toolForRendering.name !== 'AskUserQuestion' &&   // ← excluded
    toolForRendering.name !== 'ExitPlanMode' &&
    toolForRendering.name !== 'exit_plan_mode' &&
    toolForRendering.name !== 'AcpHistoryImport' && (
    <PermissionFooter ... />
)}

This is correct — AskUserQuestion is excluded from the inline permission footer because AskUserQuestionView provides a custom question form instead.

Location 2: AgentInput.tsx:1759-1776 — Does NOT exclude AskUserQuestion

{props.sessionId && pendingPermissionRequests.length > 0 ? (
    <View style={styles.permissionRequestsContainer}>
        {pendingPermissionRequests.map((req) => {
            return (
                <View key={req.id} style={styles.permissionRequestCard}>
                    <PermissionFooter
                        permission={{ id: req.id, status: 'pending' }}
                        sessionId={props.sessionId!}
                        toolName={req.tool}
                        toolInput={req.arguments}
                        ...
                    />
                </View>
            );
        })}
    </View>
) : null}

This renders a PermissionFooter above the text input for ALL pending permission requests, including AskUserQuestion. There is no exclusion check here.

Result

• AskUserQuestionView renders the question form in the transcript ✓
• AgentInput renders a duplicate PermissionFooter near the keyboard ✗
• User sees both, and if they interact with the PermissionFooter (which is more prominent/closer to where they're looking), it resolves the permission via sessionAllow() without structured answers
• The question form is dismissed without the user's answer being sent

Fix

Add the same exclusion to AgentInput.tsx:1761 that exists in ToolView.tsx:441:

{pendingPermissionRequests
    .filter(req => req.tool !== 'AskUserQuestion' && req.tool !== 'ExitPlanMode' && req.tool !== 'exit_plan_mode' && req.tool !== 'AcpHistoryImport')
    .map((req) => { ... })}

Similarly, ToolFullView.tsx:175 has the exclusion but should be verified to match.

Affected Files

• apps/ui/sources/components/sessions/agentInput/AgentInput.tsx (line 1759-1776 — missing exclusion)
• apps/ui/sources/components/tools/shell/views/ToolView.tsx (line 441 — has correct exclusion)
• apps/ui/sources/components/tools/shell/views/ToolFullView.tsx (line 175 — has correct exclusion)

🤖 Generated with Claude Code

[begna112]

Related: Regular permission requests also render twice

The same AgentInput.tsx:1759-1776 code path causes a related issue for all permission-requiring tools (Bash, Edit, Write, etc.), not just AskUserQuestion.

For regular tools, both locations render PermissionFooter:

1. ToolView.tsx:441 — renders PermissionFooter inline with the tool card in the transcript (AskUserQuestion is excluded here, but regular tools are not)
2. AgentInput.tsx:1764 — renders another PermissionFooter above the text input for ALL pending requests (no exclusions at all)

The result is two identical permission dialogs visible simultaneously — one in the tool card in the transcript, and one stacked above the keyboard. Both resolve the same permission ID, so tapping either one works, but the duplication is confusing.

Suggested approach

The AgentInput.tsx permission footer was likely intended as a convenience so users don't have to scroll to find the permission in the transcript. Rather than simply filtering out all duplicates, a better fix might be:

• For tools with custom UIs (AskUserQuestion, ExitPlanMode, AcpHistoryImport): filter them out of AgentInput.tsx's pending list entirely (the fix from the main issue)
• For regular tools: either remove the AgentInput duplicate and rely on auto-scrolling to the tool card, or keep only the AgentInput one and suppress the inline one — but don't render both

🤖 Generated with Claude Code

[begna112]

Additional duplicate rendering instances

Audit found that the AgentInput.tsx no-exclusion bug affects more tools than just AskUserQuestion:

ToolFullView.tsx is a third rendering location

ToolFullView.tsx (~line 175) renders PermissionFooter with the same exclusion list as ToolView.tsx. So there are actually three places rendering PermissionFooter:

1. ToolView.tsx (inline, with exclusions)
2. ToolFullView.tsx (full detail view, with exclusions)
3. AgentInput.tsx (input area, no exclusions)

Other tools affected

The following tools all have custom action UIs but are NOT excluded from AgentInput.tsx, meaning they get a duplicate generic permission footer:

Tool	Custom View	Custom UI Purpose
AskUserQuestion	AskUserQuestionView.tsx	Question form with answer selections
ExitPlanMode / exit_plan_mode	ExitPlanToolView.tsx	Approve/Reject/Request Changes buttons
AcpHistoryImport	AcpHistoryImportView.tsx	Import/Skip buttons

All three are properly excluded in ToolView.tsx and ToolFullView.tsx but not in AgentInput.tsx.

Suggested fix

Centralize the exclusion list into a shared constant (e.g. TOOLS_WITH_CUSTOM_PERMISSION_UI) and apply it in AgentInput.tsx's pendingPermissionRequests.map() as a filter.