Unverified50% confidenceFactExact time
The session fork (Fork) feature clones the entire session along with all context, after which different messages can be sent to each fork because they are fully independent sessions.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
9/17/2026
First Seen
Valid until: 12/16/2026
Sources
Related Entities
Related Claims
UnverifiedCodex supports a Fork Chat feature that allows multiple independently evolving conversation branches to be created on the basis of a shared historical context, for parallel handling of different tasks.76% similarUnverifiedIn the open-source world, a fork specifically refers to copying an independent code snapshot from the same repository at a certain point in time and then developing it in different directions.69% similarUnverifiedIn Flock, each chat session has its own independent workspace and code branch, keeping different requirements isolated from one another.65% similarUnverifiedIn multi-turn conversations, all previous context is resent as input each time, so redundant code generated early on continues to incur token costs in every subsequent round.64% similarUnverifiedImproved /fork so that new background sessions retain the prompt cache from the original conversation.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/930112API
curl https://kongchang.com/api/v1/knowledge/claims/930112MCP
get_claim(id=930112)