Unverified50% confidenceDecision RuleExact time
After switching modes with the Switch, already-registered clients need to start a new conversation to load the new tool list, because old conversations cache the old tool inventory.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedMid-conversation tool changes allow different tool lists to be passed in across different turns of the same session, enabling agents to load specialized toolkits on demand, thereby reducing token consumption and improving tool call precision.77% similarUnverifiedConversation history and the current working directory are two different things, and conversation handoff itself does not isolate file changes; before letting another tool edit files, the project and existing changes need to be confirmed.74% similarUnverifiedThe "Continue in a New Conversation" feature allows users to select the function entry on the corresponding message, automatically bringing existing context into a new conversation, while the original conversation is fully preserved.69% similarUnverifiedOnce the tool list is fixed, any newly added tool automatically becomes a change request and is mandatorily brought into the approval process.69% similarUnverifiedIn traditional tool-calling workflows, developers typically bind the tool set at the start of a session, making it difficult to change throughout the conversation lifecycle68% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1072757API
curl https://kongchang.com/api/v1/knowledge/claims/1072757MCP
get_claim(id=1072757)