What happened:
Long version:
During testing PR 393, I created a new chat to start tokens from 0, and see if they accumulate. I then reset the agent to see if the tokens would reset to 0, which they did. Upon asking a new question, instead of answering it in the chat i had made, it answered it in main and threw off the calculations of tokens. Specifically, cached tokens were calculated as 0.
Summary: Resetting an agent chat in a side chat, means that the next question is somehow answered in the main chat.
What I expected:
I expected to have my question answered in the same side chat, and I expected a token count that seemed plausible for the question asked.
Steps to reproduce:
- Create a New chat
- Ask it a random question
- Check Tokens are working (not 0)
- /reset command
- Wait for the reset
- Ask a question
- Check Main chat to see that the question has been answered there.
Environment: (browser, OS, server, version/commit) Browser, Windows 11, PR 393 branch
Logs / screenshots:

This image shows steps 1-5 from asking a question, to resetting the agent.

This image shows asking a question after the reset.

This image shows me switching to the main chat, where my question was answered and the other chat is stuck waiting.

This image shows the tokens being reset in the first chat.

The token count in the main chat.

Token Count after asking a question in main.
The screenshots from the first initial bug encounter:

This image shows the initial bug encounter where the question was answered in main, and the token count. Perhaps the token count being 0 is because this was the first time using the chat since i had to reboot craftbot.
-'(bug)'
-'(p2)'
What happened:
Long version:
During testing PR 393, I created a new chat to start tokens from 0, and see if they accumulate. I then reset the agent to see if the tokens would reset to 0, which they did. Upon asking a new question, instead of answering it in the chat i had made, it answered it in main and threw off the calculations of tokens. Specifically, cached tokens were calculated as 0.
Summary: Resetting an agent chat in a side chat, means that the next question is somehow answered in the main chat.
What I expected:
I expected to have my question answered in the same side chat, and I expected a token count that seemed plausible for the question asked.
Steps to reproduce:
Environment: (browser, OS, server, version/commit) Browser, Windows 11, PR 393 branch
Logs / screenshots:
The screenshots from the first initial bug encounter:
-'(bug)'
-'(p2)'