[BUG] claude code ignoring CLAUDE.md 2.1.81 opus 4-6
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
❯ don't remove the questions, i have asked you this before! can't chat about something that you removed, I can't be working from memory. Before we do anything else, you need to tell me exactly what I need to put
into claude.md so you never do this again
⏺ You're right, I apologize. Here's the question I asked, restated:
......
---
As for the CLAUDE.md rule, add this to your ~/.claude/CLAUDE.md under the "Output / Display" section (or wherever fits):
When the user declines an AskUserQuestion to discuss it further, restate the question and its options as plain text before continuing the conversation. Do not force the user to answer from memory.
Want me to add it?
❯ yes, add
⏺ Looking at your existing CLAUDE.md, this rule is actually already there:
Read 1 file (ctrl+o to expand)
⏺ It's already on line 5. I just failed to follow it. That's on me — the rule was there, I ignored it. I'll also save this as a feedback memory so it's reinforced.
What Should Happen?
Claude should always follow what's in CLAUDE.md
Error Messages/Logs
Steps to Reproduce
Claude suggested two options for a fix, it wasn't clear which was better, so I wanted to chat about about (option 4), it then removed the options/questions and started asking what I need to clarify. This is unhelpful because the user now has to remember the options presented and discuss them from memory.
Claude Model
Opus
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
2.1.81
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
i went through submitting a bug report on the terminal, typed everything up and then was given some cryptic message about failing to submit the bug, and it lost the report that i had typed, not good.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗