{"version":"2.1.288","anchor":"session-lifetime-can-come-from-a-tenant-value-not-only-the","canonical_anchor":"session-lifetime-can-come-from-a-tenant-value-not-only-the","heading":"Remote session time limits can now come from a per-tenant value","tier":"internal","area":"Sessions","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/session-lifetime-can-come-from-a-tenant-value-not-only-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Remote session time limits can now come from a per-tenant value\n\nA remote session's time limit can now come from a value set for its tenant, not only from the `CLAUDE_CODE_REMOTE` flag setting\n\n**Unclear.** It is not clear what decides whether the limit comes from the tenant or the flag.\n\n**What**\n\nRemote sessions run Claude Code on a machine other than yours and have a maximum lifetime. Claude Code now first checks where that limit comes from:\n\n- If it comes from somewhere other than the flag, Claude Code uses a value set for the tenant, meaning the account or workspace the session runs under.\n\n- Otherwise it falls back to the earlier flag-based value, which applies when `CLAUDE_CODE_REMOTE` is set.\n\nPreviously the limit came only from the flag. When the tenant value is in use and the last full check happened very close to the limit, Claude Code now treats the remaining time as zero instead of leaving it unset.\n\n**Why**\n\nRemote session time limits can now differ per tenant instead of being fixed by one flag.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}