Two follow-ups from the transcript-attachment lane (feat(webui): show attachment metadata in the session transcript), neither of which is a rendering bug in itself.
LATENT DOUBLE LABEL. A Telegram attachment is stored with the channel note already in Text ("[photo]\n"), so once a media-carrying message is rendered the transcript shows the chip [photo] AND the note in the body. The note exists for the MODEL history (stored history is text-only, so the note is what a later turn reads) and must not change. The fix is display-side: when a message has media, drop a leading bracketed note line from the rendered text. Not visible today only because of item 2.
SESSIONS WITH MEDIA ARE UNREACHABLE. /api/chat/sessions and /api/chat/sessions/{id}/messages refuse any session whose platform is not "web", and the browser inbound decode attaches no media, so no media-carrying session can currently be listed in the dashboard. Wiring that up means deciding whether Telegram conversations belong in the dashboard chat panel at all -- a product decision, not a rendering fix, which is why the lane left it.
Reference: internal/webui/api_chat.go chatMediaView (type, file name, mime, size, width, height, duration, url -- deliberately no file id, no bytes, no host path), ui/src/chat/attachment.ts mediaLabel/mediaDetail, ui/src/chat/ChatAttachment.vue.
Imported from beads archie-core-ykrp · GitHub #1387 · type task · priority P3 · created 2026-09-29
Two follow-ups from the transcript-attachment lane (feat(webui): show attachment metadata in the session transcript), neither of which is a rendering bug in itself.
1. LATENT DOUBLE LABEL. A Telegram attachment is stored with the channel note already in Text ("[photo]\n<caption>"), so once a media-carrying message is rendered the transcript shows the chip [photo] AND the note in the body. The note exists for the MODEL history (stored history is text-only, so the note is what a later turn reads) and must not change. The fix is display-side: when a message has media, drop a leading bracketed note line from the rendered text. Not visible today only because of item 2.
2. SESSIONS WITH MEDIA ARE UNREACHABLE. /api/chat/sessions and /api/chat/sessions/{id}/messages refuse any session whose platform is not "web", and the browser inbound decode attaches no media, so no media-carrying session can currently be listed in the dashboard. Wiring that up means deciding whether Telegram conversations belong in the dashboard chat panel at all -- a product decision, not a rendering fix, which is why the lane left it.
Reference: internal/webui/api_chat.go chatMediaView (type, file name, mime, size, width, height, duration, url -- deliberately no file id, no bytes, no host path), ui/src/chat/attachment.ts mediaLabel/mediaDetail, ui/src/chat/ChatAttachment.vue.
---
_Imported from beads `archie-core-ykrp` · GitHub #1387 · type task · priority P3 · created 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.
Two follow-ups from the transcript-attachment lane (feat(webui): show attachment metadata in the session transcript), neither of which is a rendering bug in itself.
LATENT DOUBLE LABEL. A Telegram attachment is stored with the channel note already in Text ("[photo]\n"), so once a media-carrying message is rendered the transcript shows the chip [photo] AND the note in the body. The note exists for the MODEL history (stored history is text-only, so the note is what a later turn reads) and must not change. The fix is display-side: when a message has media, drop a leading bracketed note line from the rendered text. Not visible today only because of item 2.
SESSIONS WITH MEDIA ARE UNREACHABLE. /api/chat/sessions and /api/chat/sessions/{id}/messages refuse any session whose platform is not "web", and the browser inbound decode attaches no media, so no media-carrying session can currently be listed in the dashboard. Wiring that up means deciding whether Telegram conversations belong in the dashboard chat panel at all -- a product decision, not a rendering fix, which is why the lane left it.
Reference: internal/webui/api_chat.go chatMediaView (type, file name, mime, size, width, height, duration, url -- deliberately no file id, no bytes, no host path), ui/src/chat/attachment.ts mediaLabel/mediaDetail, ui/src/chat/ChatAttachment.vue.
Imported from beads
archie-core-ykrp· GitHub #1387 · type task · priority P3 · created 2026-09-29