[Sonnet 4] - Plagued by response too large 'nudge'

Preflight Checklist

• [x] I have searched existing issues for similar behavior reports
• [x] This report does NOT contain sensitive information (API keys, passwords, etc.)

Type of Behavior Issue

Other unexpected behavior

What You Asked Claude to Do

Provide a patch for a website/application I was developing with the assistance of the model

What Claude Actually Did

Developed the patch but during development a msg stating "This response paused because Claude reached its max length for a message. Hit continue to nudge Claude along." is presented; when I pressed continue the resulting code 70% of the time is mangled where code is inserted randomly into the file - it does not resume where it stopped

Expected Behavior

Resume file where it paused

Files Affected

Permission Mode

Accept Edits was ON (auto-accepting changes)

Can You Reproduce This?

Sometimes (intermittent)

Steps to Reproduce

Any request where the model takes more than about 1.5m results in the prompt and most times it mangles the code

Claude Model

Sonnet

Relevant Conversation

I'll help you enable file upload and OpenSearch indexing functionality. Based on the existing codebase, I need to create a comprehensive patch that implements proper EVTX file processing and indexing.

3 continue prompts

I've created a comprehensive patch that enables full file upload and OpenSearch indexing functionality for your caseScope EVTX analysis system. Here's what the patch accomplishes:
....

resulting file mangled; try new approach enable upload only

I'll create a simpler, focused approach that only enables file upload functionality without the complex indexing components that may have caused issues.

continue prompt

Impact

High - Significant unwanted changes

Claude Code Version

?

Platform

Other

Additional Context

This is from the website directly - this results in me using most of time/tokens just trying to repair issues oevr and over instead of making progress on project; at current I have 40+ hours of which minimally 10 is spent dealing jjust with this issue