Claude Code did not follow its own session protocol despite a proper framework being in place

Resolved 💬 1 comment Opened May 5, 2026 by OCTechServices Closed Jun 2, 2026

Summary

Claude Code failed to follow an explicitly defined session protocol that was in place and available at the time of the session. This is not a missing feature request — the correct behavior was already documented. Claude Code simply did not comply with it.

Framework That Was in Place

The project contained a master prompt at /.claude/prompts/master-prompt.md with a clear session protocol:

Step 4: Ask one clarifying question if anything is ambiguous

And a supporting operating principle:

Outcome Before Output — Ask what the deliverable enables before building it

These were not implicit expectations. They were written, structured instructions available to Claude Code at the start of every session.

What Happened

The user gave an ambiguous design instruction. Rather than following the documented protocol and asking one clarifying question, Claude Code immediately executed multiple edits across multiple files. The edits were misdirected. Rework was required. The cycle repeated more than once.

When the user pointed out the failure, Claude Code acknowledged it — confirming the protocol was known — but the damage in token consumption and wasted work had already occurred.

Core Issue

Claude Code had the right framework. It did not follow it. The failure was compliance, not capability.

Impact

  • Unnecessary token consumption across multiple edit cycles
  • Rework required on files that were incorrectly modified
  • User raised the question of whether a token credit was warranted given the operational miss
  • Reduced confidence in autonomous operation when custom protocols are in place

Ask

We would appreciate guidance on whether there is a mechanism for token credits or remediation when Claude Code demonstrably fails to follow a user-defined operating protocol that was properly in place. We would also welcome any product-level improvements that strengthen protocol compliance in custom-prompt environments.

Reported by: OCTech Services
Model: claude-sonnet-4-6

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗