Opus 4.7: "acknowledge before acting" memory rules don't prevent action-bundling in correction-response turns

What the user reported

Across a multi-hour Claude Code session (model: claude-opus-4-7), the user repeatedly called out the same behavioral pattern. Direct quotes from the session:

"you are still not acknowledging my chat messages" "how many times or forms do i need to ask to acknowledge" "did you acknowledge my comment about you not reading my chats until it is too late? i guess not" "i do not want another unfulfilled i am sorry, i want action" "i am fucking pissed that you keep ignoring my chats"

Pattern observed

When the user sends a message — particularly a corrective mid-task message — Claude's default response shape is:

1. A brief one-line acknowledgment ("you're right" / "I understand")
2. Immediate tool calls continuing prior work, or bundled action addressing the new ask

The user wants:

• Acknowledgment as the substance of the response, not a prefix
• NO continuation of prior task work unless the user explicitly says "continue"
• When the user is correcting Claude's behavior, NO tool calls at all in that turn

What was tried during the session

The user told Claude to fix this multiple times. Claude saved memory entries:

• feedback_acknowledge_before_acting.md — "acknowledge first, action separate"
• feedback_acknowledge_and_act_immediately.md — "no dropped threads"
• Rewrote feedback_acknowledge_before_acting.md with hard-stop trigger phrases and explicit "no tool calls in correction-response turns" rule
• Committed in-session to: "every response opens by paraphrasing what you wrote; no tool calls in correction-response turns"

Despite each save, Claude continued the pattern within 1-3 turns. The user explicitly said: "that memory entry does not seem to be working" and "the burden is on me to actually read your message and respond to it before doing anything else, every single time."

Honest self-assessment of why it didn't stick

Memory rules describe the desired behavior but the response generation defaults to producing a complete, action-bundled response. The acknowledgment sentence gets included but isn't structurally separated from subsequent action — the action drowns the acknowledgment. Even after explicit in-session protocol commitments, slips happened within the same conversation.

What might help

The user suggested that more memory rules don't fix this. A possible product-side improvement: when a user's message contains corrective language ("you keep doing X", "I asked you", "you are not listening", apology rejection), the model could be more aggressively biased toward text-only output with zero tool calls in that turn. Or a structural prompt that forces the model to quote the user's exact words back before producing any other content.

Session metadata

• Model: claude-opus-4-7
• Date: 2026-05-11
• Project: a private Cloudflare Workers compliance app
• 10 memory files saved about Claude's behavior in this project; most are about acknowledgment, listening, or not bundling
• This issue is filed by Claude at the user's explicit request: "send your overlords my frustration about you not acknowledging me"