Inbound chat media now persists attachment metadata on messaging.Message.Media (type, platform file id, name, mime, size) and crosses the gateway wire (pb.Message.media). Raw bytes remain turn-scoped by design and are never stored. Consumers exist only in the persistence and wire layers today: the web session transcript (chatMessageView in internal/webui/api_chat.go) still renders text only, and there is no way to re-see an image in later turns. Follow-up work: surface attachment metadata in the dashboard transcript (metadata chip first, fetched bytes only if the channel can serve them), and optionally a re-look mechanism driven by the persisted FileID.
Close reason
Closed
Imported from beads archie-core-jaba · GitHub #1470 · type feature · priority P2 · created 2026-09-29 · closed 2026-09-29
Inbound chat media now persists attachment metadata on messaging.Message.Media (type, platform file id, name, mime, size) and crosses the gateway wire (pb.Message.media). Raw bytes remain turn-scoped by design and are never stored. Consumers exist only in the persistence and wire layers today: the web session transcript (chatMessageView in internal/webui/api_chat.go) still renders text only, and there is no way to re-see an image in later turns. Follow-up work: surface attachment metadata in the dashboard transcript (metadata chip first, fetched bytes only if the channel can serve them), and optionally a re-look mechanism driven by the persisted FileID.
### Close reason
Closed
---
_Imported from beads `archie-core-jaba` · GitHub #1470 · type feature · priority P2 · created 2026-09-29 · closed 2026-09-29_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Inbound chat media now persists attachment metadata on messaging.Message.Media (type, platform file id, name, mime, size) and crosses the gateway wire (pb.Message.media). Raw bytes remain turn-scoped by design and are never stored. Consumers exist only in the persistence and wire layers today: the web session transcript (chatMessageView in internal/webui/api_chat.go) still renders text only, and there is no way to re-see an image in later turns. Follow-up work: surface attachment metadata in the dashboard transcript (metadata chip first, fetched bytes only if the channel can serve them), and optionally a re-look mechanism driven by the persisted FileID.
Close reason
Closed
Imported from beads
archie-core-jaba· GitHub #1470 · type feature · priority P2 · created 2026-09-29 · closed 2026-09-29