diff options
| author | Agando <roduccomm@gmail.com> | 2026-10-23 20:25:19 +0200 |
|---|---|---|
| committer | Agando <roduccomm@gmail.com> | 2026-10-23 20:25:19 +0200 |
| commit | bc013618059fb5b4d08f23fb039252918c1aec99 (patch) | |
| tree | d0a8e81b7457e76520ba282d7f10b8d8be6205ec /modules/core/module-debug-supervisor.js | |
| parent | a803cc418260f977d8086f113bcc8008839400f5 (diff) | |
fix(newos4): agent read gets its own chat cursor (v4.6.76)
Two readers shared one cursor. The 30 s UI poller printed each reply and advanced
webx11_chat_state.cursor, so the agent's chat_hermes read then asked for 'since=<that>'
and got an empty list — the answer appeared on the terminal and never reached the model.
That is the reported symptom exactly.
chat_hermes read now uses webx11_chat_agent_cursor, starts from 0 on first use so the
whole thread is visible, and never touches the display cursor. Empty reads say why
('still awaiting Hermes' vs 'no new messages since your last read').
Proven: UI poll consumed the reply (printed to terminal), then chat_hermes read still
returned both the agent's question and Hermes's answer.
Diffstat (limited to 'modules/core/module-debug-supervisor.js')
0 files changed, 0 insertions, 0 deletions