{"version":"2.1.277","anchor":"session-inbox-relayed-messages-can-now-carry-attachments","canonical_anchor":"session-inbox-relayed-messages-can-now-carry-attachments","heading":"Session-inbox relayed messages can now carry attachments","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/session-inbox-relayed-messages-can-now-carry-attachments","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Session-inbox relayed messages can now carry attachments\n\nRelayed session-inbox messages can now include attachments\n\n**What**\n\nMessages relayed through the session inbox (used for things like Slack messages reaching a session) can now carry attachments. The message event builder accepts an optional attachments argument and includes it in the message data sent to the session. The `attachments` field has also been added to the list of fields treated as untrusted, alongside the existing `body`, `sender_display`, and `slack_permalink` fields.\n\n**Why**\n\nThis lets relayed messages carry file or media attachments rather than just text, while still treating that attachment data as untrusted input like the rest of the relayed message.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}