Unverified50% confidenceFactExact time
After turning off the chat history toggle, new conversations are no longer saved to the account history, but the already-saved records and whether they are used for training follow a different set of logic.
1
Sources
50%
Confidence
Long-term
Relevance
11/4/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedOpenCode终端模式关闭窗口后本轮聊天记录即丢失无法保存，而桌面版会持久保存历史记录69% similarUnverifiedFixed an issue where managed settings and organization policies were not fetched for the remainder of the session after logging in from the VS Code extension.68% similarUnverifiedWhen resuming historical sessions with --continue and --resume, early messages may be resent in an altered form, causing the API to discard Claude's previous reasoning; the new version fixes more such edge cases.66% similarUnverifiedWhen repairing chat history, APX follows one rule: an interrupted tool call must have an explicit outcome in the conversation history, recorded as 'not run: the turn was interrupted'.64% similarUnverifiedBy default, only the current session is processed upon restoration; long-term memory and workspace files are not automatically restored and will only be synced if the user explicitly checks the corresponding option.63% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1134950API
curl https://kongchang.com/api/v1/knowledge/claims/1134950MCP
get_claim(id=1134950)