{"version":"2.1.280","anchor":"new-optional-chained-field-in-a-syncsession-schema","canonical_anchor":"new-optional-chained-field-in-a-syncsession-schema","heading":"New optional \"chained\" field in a sync\/session schema","tier":"internal","area":"Session Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-optional-chained-field-in-a-syncsession-schema","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New optional \"chained\" field in a sync\/session schema\n\nSync\/session data now includes an optional \"chained\" field\n\n**Unclear.** The finding does not say what the `chained` field represents or how it affects session syncing.\n\n**What**\n\nA data structure used for syncing session state (which already tracked `indexCommit`, `worktreeCommit`, and `bundle`) gained a new optional field called `chained`, with a fallback value if it can't be determined.\n\n**Why**\n\nThis is internal state used by Claude Code's sync mechanism; the finding does not describe what behavior it enables for users.\n\n- Area: Session Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}