Claude’s ‘Continue’ button can break long answers
Claude has brought back a flow where long replies stop partway through and require the user to press a “Continue” button. The likely reason is to stop extra token use when the current limit has been reached. But pressing “Continue” can make Claude lose the thread of the answer.
The continued part may break sentence flow, code syntax, or formatting. Sometimes the continued answer has to be stopped and regenerated several times, which can waste more tokens instead of saving them. In the worst case, the conversation may need to be restarted because Claude cannot continue the earlier answer cleanly.
A suggested alternative is to let users borrow tokens from the next session or choose their preferred behavior with a setting.
Key points
- Claude can stop a long reply and require the “Continue” button before finishing.
- The continued answer may lose the original flow and damage code, syntax, or formatting.
- Regenerating failed continuations can use more tokens than expected.
- Small, focused prompts are safer than asking Claude for one very long output.
- A user-controlled setting or token borrowing model was suggested as a better option.