claude-code - 💡(How to fix) Fix [Bug] Claude Code overestimates task duration and bails from tasks claiming they're too complicated [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#55576Fetched 2026-05-03 04:49:49
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×3commented ×2
RAW_BUFFERClick to expand / collapse

Bug Description

Claude Code has been consistently overestimating how long tasks will take in recent weeks. It will unprompted provide time estimates numbered in weeks for tasks that I know in the past would take it 30 minutes. This overestimate frequently leads to it bailing out early on tasks claiming that it can't complete them in one session.

Due to the timing of the regression coinciding with its new habit of offering to /schedule background agents as a "follow up" at totally inappropriate times, I suspect that the framing of the "offer to /schedule" prompt is skewing Claude towards the idea that it's always working on a weeks-long project, even in cases where it would be totally inappropriate for it to assume that.

Environment Info

  • Platform: linux
  • Terminal: konsole
  • Version: 2.1.126
  • Feedback ID: f08579a3-adfe-4344-a45d-3417dd2759ca

extent analysis

TL;DR

The issue may be resolved by adjusting the framing of the "offer to /schedule" prompt to prevent Claude from assuming it's working on a weeks-long project.

Guidance

  • Investigate the recent changes to the /schedule prompt and its potential impact on Claude's task estimation.
  • Review the logic behind Claude's task duration estimation to identify potential biases or assumptions.
  • Consider adding a flag or parameter to the /schedule prompt to indicate when it's being used for short-term tasks.
  • Test Claude with a variety of tasks and prompts to verify if the issue is specific to certain types of tasks or prompts.

Notes

The issue seems to be related to the interaction between the /schedule prompt and Claude's task estimation logic, but the exact cause is unclear. Further investigation is needed to determine the root cause and develop a comprehensive solution.

Recommendation

Apply workaround: Adjust the framing of the "offer to /schedule" prompt to prevent Claude from assuming it's working on a weeks-long project, as this change is likely to have the most immediate impact on resolving the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING