{"version":"2.1.288","anchor":"remote-session-denycancel-tracking-and-epoch-conflict-state","canonical_anchor":"remote-session-denycancel-tracking-and-epoch-conflict-state","heading":"Remote sessions get handling for conflicts and pending denials","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/remote-session-denycancel-tracking-and-epoch-conflict-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Remote sessions get handling for conflicts and pending denials\n\nRemote sessions gain logic for epoch conflicts and for denials awaiting cancellation, and close upload paths on shutdown\n\n**Unclear.** Whether this logic is in use yet, and what sets it off, is not known.\n\n**What**\n\nFor remote sessions, where Claude Code runs on another machine, Claude Code gains several pieces of logic:\n\n- it keeps track of its own denials of a request that are still waiting for the request to be cancelled\n\n- on an epoch conflict, it picks one of several outcomes: stand down, send a follow-up, send a follow-up without fencing, or refuse a follow-up\n\n- it closes its upload paths when it shuts down\n\n**Why**\n\nThis is meant to make remote sessions more robust when competing updates clash.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}