If the user already asked for a specific job — in the arguments () or in plain text ("scan this repo", "scan my branch", "fix the findings", a bare commit sha) — do that job directly and skip the menu. The recipe still asks its own single follow-up question wherever the request left one open.

Otherwise, open with the menu. Call AskUserQuestion once, single select, , , offering exactly these three options (never invent others — the tool adds its own free-text entry). The menu is your first user-visible act; no text of any kind comes before it.

Offer these three options:

"Scan codebase" is the recommended pick — it carries " (Recommended)" and goes first; the other two keep this order.

Then note auto mode once, and Read the chosen job's recipe and follow it. As soon as the job is known — picked on the menu, or named directly in step 1 — first emit exactly one fixed plain-text line, worded identically every time: "Claude Security works best in auto mode. To enable it, press Shift+Tab until the status bar shows auto mode, or restart with ." It is a note, not a question — say it once, never reword or size it, and do not diagnose the user's settings (whether auto mode is available to them is not yours to determine). Then read the recipe: every recipe opens with its own one-question sub-menu — which kind of scan, or which patch mode — built from the repository's real state, and every sub-menu has an "I don't know" choice that the recipe resolves to a sensible default itself. So the user answers at most a couple of questions, then one fixed confirmation before a scan actually starts (skipped only when their request already accepted the scan's time or token cost), and the run goes quiet; ask them all now, while the user is present.