claude-code - 💡(How to fix) Fix Write tool never executes: plan writing tasks consume 40-50k tokens without writing a single line to file [1 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#60611Fetched 2026-05-20 03:54:02
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1

Root Cause

Possible cause (user hypothesis)

Not overhead/reload (context persists across interruptions). Root cause unknown — model appears unable to reach the Write tool call execution step despite having all required context loaded.

RAW_BUFFERClick to expand / collapse

Bug Report

Date: 2026-05-19

Environment:

  • Claude Code CLI, macOS Darwin 25.4.0
  • Model: claude-sonnet-4-6
  • Project: onbo-360 (SaaS platform)

What was asked

Write an implementation plan to a file: docs/superpowers/plans/2026-05-19-ra-website-builder.md

Prompt: Read 3 files (CLAUDE.md, HANDOFF.md, spec doc), then write plan to file.

What happened

  • Across multiple sessions today (since afternoon), the Write tool never executed
  • Each session consumed 40-50k+ tokens in overhead (skill invocations, file reads, bash commands, diagnostic questions)
  • Model kept switching to explaining/diagnosing instead of writing
  • No plan file was ever created
  • In the final session: model said 'Writing now' multiple times but never called the Write tool

Expected behavior

Write tool executes and creates the plan file after reading source files.

Actual behavior

Write tool never fires. Model cycles through: skill invocation → file reads → directory checks → 'Writing now' text → stall → explanation mode → repeat.

Impact

~100k tokens wasted across multiple sessions. Zero output produced. Task completely blocked.

Possible cause (user hypothesis)

Not overhead/reload (context persists across interruptions). Root cause unknown — model appears unable to reach the Write tool call execution step despite having all required context loaded.

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…

FAQ

Expected behavior

Write tool executes and creates the plan file after reading source files.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Write tool never executes: plan writing tasks consume 40-50k tokens without writing a single line to file [1 comments, 2 participants]