{"version":"2.1.309","anchor":"new-no-turn-max-age-ms-retention-policy-field","canonical_anchor":"new-no-turn-max-age-ms-retention-policy-field","heading":"Server can set a separate age limit for sessions with no turns","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/new-no-turn-max-age-ms-retention-policy-field","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Server can set a separate age limit for sessions with no turns\n\nClaude Code now reads a separate maximum age from the server for sessions with no turns, which otherwise matches the general age limit\n\n**Unclear.** What is removed or kept when this limit applies is not stated.\n\n**What**\n\nClaude Code receives a policy from the server that limits how long records are kept. It now reads a separate age limit, `no_turn_max_age_ms`, which appears to apply to sessions where no turn (one exchange with Claude) has happened yet. When the server does not send it, it is the same as the general age limit.\n\n**Why**\n\nThe server can now treat sessions with no turns differently from the rest. Unless it sends a different value, nothing changes.\n\n- Area: Elsewhere\n- Names: `no_turn_max_age_ms`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}