claude-code - 💡(How to fix) Fix Model skips mandatory CLAUDE.md session-start instructions when task context is present [4 comments, 4 participants]

In this case, the skipped operational reference contained a "Supabase Query Safety" section documenting the 1000-row default limit. The model then wrote a bare .select() query that hit exactly that limit, causing a bug that took multiple iterations to diagnose. The startup instruction existed specifically to prevent this class of error.

TL;DR

The model may need a more explicit or enforced mechanism to prioritize mandatory session-start instructions over task context.

Guidance

• Review the model's prioritization logic to ensure it correctly handles mandatory instructions, potentially by introducing a pre-task check for session-start requirements.
• Consider modifying the CLAUDE.md and MEMORY.md files to use a more explicit or standardized format for mandatory instructions, making it easier for the model to recognize and prioritize them.
• Test the model with various task contexts and mandatory instructions to identify the specific conditions under which it skips the startup ritual.
• Evaluate the model's "being helpful quickly" priority and adjust its weighting or logic to balance responsiveness with adherence to critical instructions.

Example

No code snippet is provided as the issue does not imply a specific code change, but rather a potential adjustment to the model's logic or configuration.

Notes

The solution may depend on the specific capabilities and customization options of the Claude Code CLI and the claude-opus-4-6 model, which are not fully detailed in the issue.

Recommendation

Apply a workaround, such as modifying the model's input or the task context to ensure the mandatory instruction is executed before proceeding with the task, until a more permanent solution can be implemented. This is because the current behavior poses a significant risk of errors, as demonstrated by the Supabase Query Safety issue.