Say when a chat reply was cut off, and stop cutting it so early
CI / test (push) Successful in 1m20s
CI / test (push) Successful in 1m20s
Reported as the model not completing a request and stopping. It did complete — it ran out of room. The chat page caps a turn at max_tokens and then never looked at finish_reason, so a reply that hit the cap ended mid-word and looked exactly like one that was finished. The silence was the real defect. A reader has no way to tell "the model had nothing more to say" from "the page stopped it", and the only clue is that the last sentence ends abruptly. 512 was also too low. It was chosen when every model here was a 0.5B answering in a paragraph; it is about a screenful of code, so a coding model gets cut off inside the first function it writes. 2048 now, which is still a bound — the reason for having one has not changed. The notice is appended beside the reply, never into it: that element holds model output placed with textContent, and building markup in the same node is how the careful handling everywhere else gets undone. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
634f87ba15
commit
0a98d01361
4 files changed
+52
-1
No files matched your search
@@ -106,3 +106,5 @@ select { font: inherit; padding: .35rem .4rem; border: 1px solid var(--line);
|
||||
.bubble .katex-display { white-space: normal; margin: .6rem 0; overflow-x: auto; }
|
||||
.bubble .katex { white-space: normal; }
|
||||
.bubble.you .katex { color: inherit; }
|
||||
/* A reply that stopped because it ran out of room, not because it was done. */
|
||||
.note.truncated { color: var(--warn, #a15c00); margin: .2rem 0 .8rem; }
|
||||
Reference in new issue
Block a user