Coder/deepseek-harness
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(web): surface max-tokens turn ends as a localized truncation notice

Browse Source 
A turn the provider ends at its per-request output cap previously produced
no visible sign in the Web chat flow: only error-kind turn/end events built
a conversation node, so the truncated answer read as a normal completion.

Add a turn-max-tokens conversation node Definition over the durable
turn/end event, a warning-styled localized notice row distinct from
turn-error, a fixture max-tokens sample turn, and an assembled keyless
snapshot pinning the dot state, title, and hint.

Closes #1522
This commit is contained in:
creatixchu
2026-08-12 15:36:27 +08:00
parent 3784607f3d
commit e4ca03cb85
22 changed files with 356 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
apps/web/tests/snapshots/max-tokens-notice/history-turn.expected.txt Normal file
View File

@@ -0,0 +1,3 @@
dot=warning
title=Output token limit reached
hint=The reply was cut off; earlier output is preserved in the conversation. Send "continue" to let the model resume.