{"version":"2.1.280","anchor":"new-readslinks-field-in-agent-generation-record-schema","canonical_anchor":"new-readslinks-field-in-agent-generation-record-schema","heading":"New readsLinks field in agent generation record schema","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-readslinks-field-in-agent-generation-record-schema","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New readsLinks field in agent generation record schema\n\nNew readsLinks field added to agent generation-tracking data\n\n**Unclear.** The finding doesn't say what readsLinks represents or how it affects the comparison outcome.\n\n**What**\n\nA data structure used to track an agent's generation and sync state, which already had fields like `unshipped` and `basedOn`, now has an optional `readsLinks` boolean field. It's read to help decide provenance (where a piece of data came from) when comparing state between peers.\n\n**Why**\n\nThis is an internal bookkeeping addition that helps Claude Code determine the origin of synced agent data more precisely.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}