clarify background and image parity

Author: eimexdev

CONTEXT.md

@@ -13,7 +13,9 @@ T3 Agent is the working name for a rich Hermes-native conversation surface and g
 - Coding, project, workspace, and specialized sidebar integrations are later capabilities. Existing T3 Code implementations should initially be hidden rather than treated as the core product.
 - V1 targets Discord-like Hermes gateway parity before notification work: Hermes slash commands, streaming and interruption, approvals, clarifications, reconnect/restart recovery, and other core conversational gateway behavior must work end to end.
 - Gateway-visible commands come from Hermes' command/skill/plugin registry. T3 Agent provides searchable `/` autocomplete and forwards the selected command and arguments unchanged; Hermes remains the command implementation.
+- V1 background-agent support is command-level parity (`/background`, `/agents`, queue/steer, and result delivery). A dedicated background-agent visualizer is not required; T3 Agent can inherit or adapt T3 Code's planned upstream visualizer later.
 - Discord-specific rich formatting and live voice-channel mechanics are not parity requirements. T3 Agent uses its native rich conversation renderer.
+- Images are a V1 gateway capability in both directions. Hermes image results should use structured attachments rendered inline on web and mobile rather than depending only on Markdown image URLs.
 - Voice-message recording/upload and Hermes transcription are the first post-v1 capability. Outbound Hermes TTS is separate and may follow it.
 - Notifications and T3 Connect rollout follow gateway parity rather than compensating for an incomplete interactive surface.
 

docs/research/hermes-gateway-feature-inventory.md

@@ -72,12 +72,16 @@ Discord embeds, buttons, emoji status, guild roles, mention rules, forum creatio
 - [ ] Send/cancel/interrupt, busy-message queue/steer behavior, and `/stop` semantics.
 - [ ] Pass every gateway-visible slash command and arguments unchanged; autocomplete is generated from Hermes commands/skills/plugins.
 - [ ] Structured dangerous-command approvals, slash confirmations, clarifications, model picker, reasoning/fast choices, typed fallbacks, authorization, and expiry.
-- [ ] Images and arbitrary file attachments in both directions, including safe caching and visible delivery failures.
+- [ ] Images and arbitrary file attachments in both directions, including safe caching and visible delivery failures. Render Hermes image results inline from structured attachments on web and mobile rather than relying only on Markdown image URLs.
 - [ ] Proactive background/cron delivery into the correct existing or newly created thread, including continuable `attach_to_session` behavior.
 - [ ] `/restart` end to end: drain, reconnect, restore the same thread/session, notify success, and suppress duplicate processing.
 - [ ] Durable turn state and explicit retryable/terminal errors; replay/ack sequence prevents duplicate messages after reconnect.
 - [ ] Show active Hermes profile/provider/model read-only; model changes continue through `/model` initially.
 - [ ] Owner-only authentication for v1.
 - [ ] Exclude Discord-specific rich formatting, guild/role/mention policy, forum mechanics, reactions, and live voice-channel participation.
+- [ ] Treat background-agent support as command and delivery parity in v1; defer a dedicated task visualizer and inherit/adapt the planned upstream T3 Code implementation when useful.
 - [ ] Immediate post-v1: native voice-message record/upload → Hermes transcription; then optional Hermes TTS/audio reply.
 
+### Current T3 image-rendering seam
+
+T3 already has a structured image-attachment contract and preserves attachments on both user and assistant messages. Mobile renders attachments inline for both roles. Web renders user attachments inline and can render image URLs embedded in Markdown, but its assistant timeline currently does not render the structured attachments already present on assistant messages. Hermes outbound images therefore require a small web rendering addition, not a new attachment protocol or storage design.