{"version":"2.1.301","anchor":"cache-keepalive-touch-window-can-be-extended-for-in-flight-r","canonical_anchor":"cache-keepalive-touch-window-can-be-extended-for-in-flight-r","heading":"Keep-alive window can now be longer while a run is in progress","tier":"internal","area":"Prompt Cache","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/cache-keepalive-touch-window-can-be-extended-for-in-flight-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Keep-alive window can now be longer while a run is in progress\n\nA new server-set option, inFlightWindowMinutes, can extend the keep-alive window while a run is in progress; it does nothing until set\n\n**What**\n\nThe cache keep-alive settings, which Claude Code receives from its server rather than from you, gain an optional value called `inFlightWindowMinutes`. It can be anywhere from 1 to 1440 minutes and has no default.\n\nWhile a run is in progress, Claude Code now uses whichever is longer: `activityWindowMinutes` (60 minutes by default) or `inFlightWindowMinutes`. Before this release, only `activityWindowMinutes` applied.\n\n**Why**\n\nThis lets the keep-alive period stretch to cover long runs. It has no effect until the server sets the value.\n\n- Area: Prompt Cache\n- Tier: Under the hood\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}