Jon Wingender 35f7461ca4 fix(tui): stop a stream outlived by /new from leaking into the next conversation ...

_finish_stream appended the completed reply to self.history - whatever
list that name currently pointed at - not to the conversation the
stream was actually answering. /new reassigns self.history to a fresh
list; a stream still running when that happens finished by silently
appending the old conversation's trailing reply onto the new one, which
then rides along in that new conversation's next /chat/stream history
payload. The conversation_id was already captured by closure for this
exact reason (see the tool-denial path); self.history needed the same
treatment.

2026-08-26 14:01:19 -05:00

..

__init__.py

feat(packaging): move the CLI into nexusos_cli and make the wheel self-sufficient

2026-08-26 08:11:39 -05:00

cli.py

fix(tui): stop a stream outlived by /new from leaking into the next conversation

2026-08-26 14:01:19 -05:00

monitor.py

fix(packaging): remove the memory-service integration this CLI reintroduced

2026-08-26 13:40:50 -05:00

ncp.py

fix(packaging): remove the memory-service integration this CLI reintroduced

2026-08-26 13:40:50 -05:00

nexus_api.py

feat(packaging): move the CLI into nexusos_cli and make the wheel self-sufficient

2026-08-26 08:11:39 -05:00

tui_app.py

fix(tui): stop a stream outlived by /new from leaking into the next conversation

2026-08-26 14:01:19 -05:00