Repository navigation
perf(agent): move the agent to nanobot 0.3.5 - #201
Merged
Merged
Conversation
On nanobot 0.2.2 every turn computed the end of the conversation again. The previous user message was sent with its runtime block and replayed next turn without it, so the model server's prompt cache missed from there; and once a room had 40 messages, nanobot summarised the oldest few with a model call before nearly every turn, which the turn waited for. 0.3.5 keeps the runtime block with its message and compacts only under context pressure. Measured on the demo rig (Qwen3.6-35B-A3B 4 bit on oMLX, four list turns in one long room session, cached tokens from the agent's debug log): - first call of a turn: 8192 of about 12,300 prompt tokens cached before, close to the whole previous prompt after - a turn: 12 to 50 s before, plus up to 107 s waiting for a summary; 8 to 16 s after What changes with it: - The family briefing is a runtime-context provider, nanobot's own seam, instead of a patched internal. It now also says when the message was sent: 0.3.5 puts no date in the prompt, and "by Friday" needs one. - The thread-session and microcompact shims are removed; nanobot keeps a session per Matrix thread itself and microcompact no longer exists. - Stacky shows it is typing while it works. - Tool calls, progress text and reasoning stay out of the chat, and the unused websocket channel is off. - The session tools 0.3.5 adds (read or message another room's conversation) are not offered to the model, so nothing said in one room reaches another. - The Matrix channel's dependencies come from its plugin manifest. nanobot moves the existing conversations to its new session store on the first start. Refs: #196
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Refs: #196