{"version":"2.1.269","anchor":"message-history-schema-gains-attached-by-field","canonical_anchor":"message-history-schema-gains-attached-by-field","heading":"Message-history schema gains attached_by field","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/message-history-schema-gains-attached-by-field","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Message-history schema gains attached_by field\n\nMessage-history schema gains an optional attached_by: \"server\" field\n\n**Unclear.** What content or feature actually sets attached_by, and how it is used once present, is not stated.\n\n**What**\n\nThe schema Claude Code uses for chat\/session messages (which already includes fields like `id`, `in_reply_to`, and `author`) now accepts an optional `attached_by` field, whose only currently allowed value is `\"server\"`.\n\n**Why**\n\nThis appears to let a message record note that something in it was attached by the server rather than by the user or the model, which could support features that add server-side content to a message after the fact, though the finding does not say what specifically uses this field.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}