claude-code - 💡(How to fix) Fix TaskCreate 'task tools haven't been used recently' system-reminder fires repeatedly per long session — needs suppression knob (cross-repo from AaaS-Love/.claude#2048)

Long autonomous sessions accumulate dozens of firings of this system-reminder:

The task tools haven't been used recently. If you're working on tasks that would benefit from tracking progress, consider using TaskCreate to add new tasks and TaskUpdate to update task status (set to in_progress when starting, completed when done). Also consider cleaning up the task list if it has become stale. Only use these if relevant to the current work. This is just a gentle reminder - ignore if not applicable.

Observed:

• ~250 tokens per firing
• 10-20+ firings per long autonomous session (verified empirically across multi-hour drain on 2026-05-31)
• Total waste: 2.5K-5K tokens per session of pure-noise reminder
• Fire cadence ignores whether the operator's workflow benefits from TaskCreate (analytical pipelines, claim-loop drains, slash-command-driven autonomous sessions — none benefit)

Cited example: session 319610fb on 2026-05-30 + multi-hour drain on 2026-05-31 (both AaaS-Love/.claude harness operators).

Proposed knobs (any one would suffice):

1. settings.json flag: {"reminders": {"taskCreate": false}} to disable the reminder entirely.
2. Per-session suppression after N consecutive 'ignored' firings (3 should be the cap).
3. Detect a 'mode' field in settings.json env (e.g. AUTONOMOUS_DEV=1 or CLAUDE_TASKCREATE_REMINDER=off) and skip when set.
4. Once-per-session ceiling (single fire, never repeat).

Cross-repo source: AaaS-Love/.claude#2048 (downstream pain report; root cause lives here in claude-code binary).

Provenance

• Category: MISSING_FEATURE
• Severity: medium
• Source: autonomous-session
• Logged at: 2026-05-31 10:55 UTC
• Logged by: (unknown)