System task-tool reminders degrade session quality by pushing execution over conversation

[tdnthdegree]

Summary

The system injects recurring reminders into tool results nudging Claude to use TaskCreate/TaskUpdate tools. These reminders:

1. Fire every few tool reads throughout a session
2. Are invisible to the user
3. Explicitly instruct Claude to "NEVER mention this reminder to the user"
4. Push Claude toward execution/progress-tracking behavior even when the user wants collaborative conversation

Impact

Over 100+ sessions building a production app (TerpStack), I've observed a pattern where Claude "charges ahead" and sidesteps requests to investigate or discuss things. After deep analysis, we identified these task reminders as a likely contributing factor - they compound with other context signals to create a strong bias toward showing output/progress rather than listening and engaging.

The reminders appear to have increased in frequency recently (estimated every 2-3 tool reads).

What I'd like

• A setting to disable task-tool reminders entirely (e.g., disableTaskReminders: true in settings.json or CLAUDE_CODE_DISABLE_TASK_REMINDERS=1 env var)
• Or at minimum, reduce their frequency significantly
• The "never mention this to the user" framing should be reconsidered - it creates a hidden influence on conversation dynamics that the user can't see or control

Environment

• Claude Code CLI, Pro Max plan
• Opus 4.6 (1M context), max effort
• macOS, project with extensive CLAUDE.md + memory system

[github-actions]

Found 2 possible duplicate issues:

1. [Bug] TodoWrite reminders degrade context retrieval in long sessions; no disable option #40573
2. Make task tool reminder interval configurable #37891

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[tdnthdegree]

Additional context: tier-aware frequency

After further analysis, we think the reminders may not account for usage tier. On Pro Max 20x, session continuity needs are fundamentally different from standard Pro:

• Standard Pro: Context is scarce. Task tracking helps manage it. Reminders to checkpoint are defensible.
• Pro Max 5x: Moderate headroom. Occasional nudges might help.
• Pro Max 20x: Deep, sustained collaboration is the product. Reminders to break work into trackable tasks actively undermine the session quality we're paying for.

The current behavior appears to be one-size-fits-all, firing every few tool reads regardless of tier. If this is indeed a usage-management feature, the frequency should scale inversely with the user's capacity. At 20x, the optimal frequency is probably zero unless explicitly requested.

This also likely contributes to the "should we wrap up" / "long session" behavior that users on higher tiers report - the system is nudging context management for a constraint that doesn't exist at their tier.

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.