Skip to content

[Feature]: Show images the agent references in its reply inline in Chat, including on remote Orca servers #27316

Open

Description

@mmarabel

Problem or use case

When an agent in the structured Chat view creates or edits an image and points to it in its reply, Orca shows only a text link. In my case a Codex chat running on a paired remote Orca server edited an image and replied with "Done … Download the edited image". To see the result I had to click through to an editor tab or copy the file off the server.

Images the agent sends as image parts already render as thumbnails, read from the machine the chat runs on. Images it names in the reply text don't:

  • A markdown link to an image file ([edited image](/path/out.png)) stays a plain link.
  • A markdown image with a file path (![edited](/path/out.png)) is handed to a plain <img> as-is. Nothing reads it through the chat's host, so on a paired server or SSH host the file can't load on the desktop.

Where this happens (read on main at ddcbb78013):

  • src/renderer/src/components/sidebar/comment-markdown-element-renderers.tsx:309: the document-variant img renderer that Chat replies use passes src straight to <img>.
  • src/renderer/src/components/sidebar/CommentMarkdown.tsx:64: the URL transform keeps path-style src values unchanged; nothing routes them to the chat's host.
  • src/renderer/src/components/native-chat/NativeChatAssistantMessageRow.tsx:68: image blocks, by contrast, go through NativeChatImageAttachments with the chat's runtime context.

#26103 listed this as a deliberate v1 limit: "Local images by path are not inlined".

Proposed solution

In structured Chat replies, when a markdown image points to a file path, show it as a thumbnail read from the machine that owns the chat, using the same read path image attachments already use (useLocalImageSrc and the runtime file preview). Clicking opens the existing image lightbox.

  • Cover local chats, chats on a paired remote Orca server, and direct SSH workspaces where the read is supported.
  • Optionally, a plain link whose target is an image file (png, jpg, gif, webp) could show the same thumbnail under the link, since agents often write "Download the image" rather than ![]().
  • Keep the current safety rules: no fetching http(s) image URLs the agent picked, only files on the chat's host, the existing size limit, and fall back to today's link when the read fails or the path is refused.

Alternatives or additional context

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions