Unverified50% confidenceCautionExact time
The resumption gating of the governed runtime is only as strict as the flow policy, and only takes effect on the approval path; flows that declare no resume policy resume for anyone. When a paused run is instead picked up from the user's next chat message, the runtime reads the session's role snapshot rather than re-reading assignments, and on denial detaches the run from the conversation, keeping it in the paused state without failing it.
1
Sources
50%
Confidence
Long-term
Relevance
10/16/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedResumption in the governed runtime is purely templated and model-free: it completes the remainder of the flow without calling the reasoner again; if any of the remaining steps calls a model, none of them run, and instead it waits for the user's next message.77% similarUnverifiedPlan mode is no longer lost when resuming with --continue or --resume <session-id>, and restored sub-agents and teammates no longer lose their prior reasoning processes and prompt cache.72% similarUnverifiedThe production-grade approach is to maintain an explicit interrupt context at the Supervisor layer, first determining whether a new message is a semantic response to an active interrupt, and only resuming the corresponding interrupt when there is a clear match, in order to prevent interrupt crosstalk.72% similarUnverifiedThe technical principle behind session persistence is similar to tmux's detach/attach mechanism, where terminal processes do not terminate when the window is closed but instead continue running in the background.70% similarUnverifiedDisabling the context management feature prevents the system from automatically compressing context, thereby maintaining model performance in long conversations.69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1048463API
curl https://kongchang.com/api/v1/knowledge/claims/1048463MCP
get_claim(id=1048463)