Claude defers fixing known problems instead of acting immediately
Resolved 💬 2 comments Opened May 26, 2026 by StefanSuditu Closed May 30, 2026
Bug Report
Category: ux
Severity: Minor
Claude Code Version: 2.1.84
OS: Windows 11 Pro
Description
When Claude identifies a problem during a multi-step task, instead of fixing it immediately, it says "I will come back to this later" or "I will fix this at the end" — and then forgets or needs to be reminded.
Example
During report migration, after rendering BANCAVAL.pdf:
- Claude noticed: "header values (Sold Initial, Sold Final, Incasat, Platit) are empty despite data existing in DB"
- Claude said: "Asta trebuie investigat. Dar acum las asta si continuu cu CASALC_C render. Revin la BANCAVAL la final."
- Claude did NOT return to fix it until the user explicitly asked
Expected Behavior
When a problem is identified:
- If it's quick to fix (< 2 min) → fix it now
- If it's complex → create a task/todo item AND actually return to it
- Never say "I'll come back later" without a concrete tracking mechanism
Impact
- Problems accumulate and become harder to fix in bulk
- User has to remember and remind Claude about deferred fixes
- Trust erodes — "you said you'd fix it and you didn't"
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗