I use Claude Code every day building a Windows app. Right when a task was flowing, it would just stop. Mid-call, no error, nothing.
The first few times, I just restarted and moved on. Eventually I started paying attention, and the causes turned out to fall into three clean patterns.
The pattern
Every tool call gets wrapped in a fixed marker — a closing tag the model writes right after it finishes describing what to run. Every single time this happened, the cutoff landed right after that marker. Same behavior on my Windows build and on an Android build, regardless of which project I was in. It wasn't about the app. It was about how I was phrasing the request.
Cause 1: backgrounding a shell command
Shells have an operator that kicks a process into the background and lets you move on to the next line immediately. Using it inside a request reliably cut the call off right after.
Fix: don't background it manually. Use the tool's own way of running something in the background instead.
Cause 2: cramming multiple jobs into one instruction
Asking for an analysis, then a display check, then a save — all in one shot, back to back. That combination reliably broke the call.
Fix: one instruction, one goal. Splitting it up cost nothing and fixed everything.
Cause 3: pasting a big block of text directly into an instruction
Handing over a long chunk of raw text as part of the instruction itself sometimes broke the call's structure entirely.
Fix: write the content to a file first, then reference the file in a separate instruction. Feels like a detour. It's actually the most reliable path.
A Windows-only gotcha
Anything touching path conversion between shells could break the call too. Routing Windows-specific commands through a separate execution path — instead of passing raw paths straight through — cut this down a lot.
Honestly, not all of it adds up
I've had it stop right at the start, with nothing crammed in, nothing backgrounded, nothing pasted. No idea why. Even the model itself doesn't always know.
When none of it works
If all three fixes don't help, resetting the conversation from scratch usually does. Sometimes chasing the root cause costs more time than just starting fresh.
I used to panic every time this happened. Not anymore.
I write more about this kind of thing — solo dev + AI, the wins and the messes — on Threads.
Top comments (0)