{"version":"2.1.293","anchor":"staging-path-tagged-fromchat-shared-index-too-large-bucket","canonical_anchor":"staging-path-tagged-fromchat-shared-index-too-large-bucket","heading":"Remote sessions mark the staging folder and report oversized shared indexes separately","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/staging-path-tagged-fromchat-shared-index-too-large-bucket","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Remote sessions mark the staging folder and report oversized shared indexes separately\n\nIn remote mode the staging folder is marked as coming from chat, and an oversized git shared index is reported as its own case\n\n**What**\n\nTwo small changes apply when Claude Code runs in remote mode or when `CLAUDE_STAGE_FILE_ROOT` is set:\n\n- The staging folder, a place where files are set aside before use, is now marked as coming from the chat.\n\n- A git shared index that is too large is now reported as its own case instead of being grouped with other shared index results.\n\n**Why**\n\nThese are bookkeeping changes for remote sessions and their reporting. Nothing here changes what a reader sees or does.\n\n- Area: Sessions\n- Names: `CLAUDE_STAGE_FILE_ROOT`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}