Ignores question-asking instructions

Sends questions the user had already answered or that are implementation details, and marks them as passing its own "would a boss ask this" check.

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/28821/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Growing. 12 reports in the last 7 days and none the week before.

Ignores standing instructions on which questions to ask the user.

Is this your bug?

File my report

Where: Planning sessions
Versions: 2.1.317
Platforms: Windows
How bad: Breaks a normal workflow.

Related: Ignores instructions and rules

Not quite your bug?

One question per turn1 person
Ignores instruction to research first5 people
Ignores CLAUDE.md rules3 people

Original reports12, newest first

Nov 14, 2026Claude judged a question as qualified although the user's own request already covered it, citing the user's earlier words as its reason; sent it anyway (19th report, follow-up to #109812 … #109829, #109873–#109879)#109880
Nov 14, 2026Claude judged a question as qualified although the answer was already decided by two things the user had said; admitted the mapping was its own (18th report, follow-up to #109812 … #109829, #109873–#109878)#109879
Nov 14, 2026Claude judged a question qualified because "the benchmark cannot answer it", while its own message labeled an option as the benchmark's approach and derived the answer itself (17th report, follow-up to #109812 … #109829, #109873–#109877)#109878
Nov 14, 2026Claude skipped the "would a boss ask this" check, then sent 4 questions plus a file-read permission list, and changed the format of the skill the user invoked (16th report, follow-up to #109812 … #109829, #109873–#109876)#109877
Nov 14, 2026Claude marked its own question as passing a "would a boss ask this" check, then asked the user where files are and for permission to read one (15th report, follow-up to #109812 … #109829, #109873–#109875)#109876
Nov 14, 2026Fable 5.2 passed its own pre-send check on questions that failed it, then sent a question it had itself flagged as flawed (11th report, follow-up to #109812 #109816 #109817 #109818 #109820 #109821 #109822 #109823 #109824 #109825)#109829
Nov 14, 2026Fable 5.2 asked the user to arbitrate implementation-level design it invented itself, right after promising not to (7th report, follow-up to #109812 #109816 #109817 #109818 #109820 #109821)#109822
Nov 14, 2026Fable 5.2 pre-decided the user's own business decisions and offered an "accept all" button (6th report, follow-up to #109812 #109816 #109817 #109818 #109820)#109821
Nov 14, 2026Fable 5.2 re-sent unanswered questions verbatim and handed a decision back without a recommendation (5th report, follow-up to #109812 #109816 #109817 #109818)#109820
Nov 14, 2026Fable 5.2 re-asked questions the user had already rejected and split questions into batches after being told to ask "from a boss's perspective" (4th report, follow-up to #109812 #109816 #109817)#109818

Show all 12Show only the newest 10

Nov 14, 2026Fable 5.2 asked implementation-level and already-answered questions after being told to ask "from a boss's perspective" (3rd report, follow-up to #109812 #109816)#109817
Nov 14, 2026Fable 5.2 repeatedly ignored explicit user instructions during a planning session (treated undecided options as decided, kept asking detail questions after being told not to)#109812