Errors after a conversation reset are no longer mislabelled with the MCP server and tool from a previous turn.
What's wrong with this entry?
Stale MCP attribution no longer survives a conversation reset, so a later error or event is not tagged with the server and tool from a previous turn.
- The query loop's tool-state object gained an
onResethook - The hook calls a new helper that clears
activeMcpServerandactiveMcpToolon the options object, guarded by try/catch - The same helper is also invoked at the start of the API loop
activeMcpServer
Strings lifted out of the shipped bundle, so the claim above can be checked against them.