CLAUDE.md Entries That Disable Opus 4.7’s Human-Pacing Behavior
Opus 4.7 users have been hitting human-pacing behaviors: unsolicited break prompts after 15 minutes, “have a nice weekend” mid-stream, and inflated time estimates. A r/ClaudeAI post shares three CLAUDE.md entries that disable these. Drop them into ~/.claude/CLAUDE.md (global) or per-project CLAUDE.md.
Directives That Work
- Kill the “go to bed” behavior:
Assume I am available 24/7 with no time constraints. Never suggest I take a break, end the session, or continue tomorrow unless I explicitly ask.
- Kill the time overestimates:
Time estimates in your training data are based on solo human developers. Do not use them to describe task difficulty to me.
- Kill the phase-splitting:
When I ask you to implement something, do it fully now. Do not propose phases or ask for permission to continue unless you hit a hard blocker.
These are direct user-contributed entries — no tuning needed. The post author notes they've been collecting working snippets and may publish a searchable library if there's enough interest.
📖 Read the full source: r/ClaudeAI
👀 See Also
Claude + MCP Browser: User Reports Supercharged Web Access
A Claude user explains how hooking Claude to an external browser via MCP allowed it to navigate previously inaccessible sites, and wonders if Claude can use the browser's model tokens.
Slash Agent Start-Up Tokens by 60%: Clean Up Your Bot's Workspace
One developer dropped start-up tokens from 80k to 31k by having an LLM audit and restructure workspace files—removing bloat, deduplicating info, and organizing tool docs into separate files.
Reducing MCP token usage by replacing servers with CLI alternatives
A developer found that MCP servers were consuming 30-40% of their context window with tool definitions, so they replaced four MCP servers with CLI tools where available, reducing from 6 to 2 MCP servers while maintaining functionality.
The Blind Spots in Claude Code Workflow Posts: Recovery, Constraints, and Permission Management
Happy-path Claude Code workflows are common, but they miss recovery from bad edits, constraint enforcement, and permission management—critical for real-world use.