Contradictory Length Limit Alerts Prevent Code Completion and Force Context Loss

Resolved 💬 6 comments Opened Apr 24, 2025 by testanalyst Closed Jan 6, 2026

Environment

  • Claude Web Interface (Claude 3.7 Sonnet)
  • Claude CLI version: N/A
  • Operating System: Windows 10
  • Terminal: N/A
  • Browser: Microsoft Edge Version 135.0.3179.85 (Official build) (64-bit)

Bug Description

Contradictory length limit alerts prevent code completion and force context loss. When Claude reaches maximum response length and displays "Hit Continue," clicking the button shows a conflicting message to start a new conversation, which breaks context continuity.

Steps to Reproduce

  1. Engage Claude in generating a lengthy code response (e.g. a python code)
  2. Wait for notification "This response paused because Claude reached its max length for a message. Hit Continue to nudge Claude along"
  3. Click "Continue" as instructed
  4. Observe contradictory alert "Your message will exceed the length limit for this chat. Try shortening your message or starting a new conversation"

Expected Behavior

Claude should either continue the response in chunks while maintaining context, or process lengthy code responses in the background and deliver them complete.

Actual Behavior

System provides contradictory instructions in sequence - first telling users to click "Continue," then stating that continuing is impossible and suggesting a new conversation. Starting a new conversation causes complete loss of context, making Claude unable to understand or continue the original request.

Additional Context

This issue particularly impacts code generation tasks where context continuity is essential. The suggested workaround (starting a new conversation) fundamentally breaks the user experience by forcing users to repeat complex prompts, often with degraded results due to lost context.

View original on GitHub ↗

This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗