You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6a7f2cb
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: CHAT_GUI_PACING_FIX.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,3 +7,11 @@
7
7
This fixes optional vision admission, not every possible source of latency. An admitted image request still uses the configured remote timeout. A chat request can still show `queued` while executing. It is not proof that the dashboard was edited or that the latest layout passed host validation.
8
8
9
9
Verification: 123 remote-helper/campaign tests passed, including deferred cooldown, thread contention, preserved screenshot and unchanged idle reservation. Ruff and installer shell syntax checks passed. V100/RTX deployment requires the operator upgrade; no real hardware result is claimed here.
10
+
11
+
## v43: interactive budgets and visible processing
12
+
13
+
Research policy no longer overrides chat thinking/output settings. Chat uses no thinking, at most 2048 output tokens and at most 60 seconds per HTTP operation. A shared monotonic 180-second deadline follows the client's copies across template/token counting, tool routing, final generation and helper pacing. This is an inference/pacing budget, not a hard wall-clock guarantee for CPU model startup or arbitrary guest tools. Timeout ends the request with a visible failure instead of endlessly retrying the same timeout.
14
+
15
+
`chat-status` includes a `processing` record for the request currently handled by the live mission PID, including start time and time budget. The persisted state remains `queued` for compatibility while execution is active. The record is cleared when handling finishes. Completion updates only still-queued requests, preserving operator cancellation.
16
+
17
+
The dashboard request still requires actual execution and host layout validation. These changes do not claim that an HTML edit or profitable training has occurred.
0 commit comments