fix(web): open agent images in expanded preview

[maria-rcks]

Agent-authored markdown images were inert while user attachments already opened the expanded preview. This routes both direct and signed workspace image sources through the same dialog, with mouse and keyboard activation. Verified with 62 focused web tests, targeted lint and typecheck, plus real-client checks at desktop and narrow viewport sizes. Built with gpt-5.6-sol through the Codex harness.

Before:

After:

---

Note

Low Risk
UI-only interaction wiring behind an optional callback; link-wrapped images are explicitly excluded to avoid breaking navigation.

Overview
Agent-authored markdown images can now open the same expanded image preview as user attachments, instead of staying non-interactive in assistant messages.

ChatMarkdown gains an optional onImageExpand callback. A shared expandableMarkdownImageProps helper wires click, Enter, and Space with button semantics (cursor-zoom-in, ARIA label) for both direct URL images and workspace file images loaded via signed asset URLs in ChatMarkdownWorkspaceImage.

MarkdownLinkContext marks link descendants so images inside anchors do not steal the link’s navigation—expand is disabled when an image is nested in a link. If onImageExpand is omitted, image rendering is unchanged.

The messages timeline passes ctx.onImageExpand into assistant ChatMarkdown so agent message images use the existing preview dialog.

^{Reviewed by Cursor Bugbot for commit 9b033f3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add expanded image preview support for ChatMarkdown images

• Adds an onImageExpand callback to ChatMarkdown and ChatMarkdownWorkspaceImage to trigger an expanded preview for markdown images.
• Images become interactive via click or Enter/Space keypress using the new expandableMarkdownImageProps utility, adding cursor-zoom-in styling.
• Uses a new MarkdownLinkContext to disable expansion for images nested inside markdown links.
• Threads the expansion handler from MessagesTimeline through AssistantTimelineRow.
• Behavioral Change: Images with an onImageExpand handler now render with role=button and tabIndex=0.

^{Macroscope summarized 9b033f3.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 7d53af26-d582-46ae-ab8b-f5f026585c4e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

_{Comment @coderabbitai help to get the list of available commands.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit e780d2a. Configure here.}

[macroscopeapp]

One finding: markdown images inside links get an interactive affordance that never activates. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the follow-up: the linked-image affordance I flagged earlier is now correctly suppressed via MarkdownLinkContext, so [![alt](img)](url) no longer renders a tab stop / role="button" / cursor-zoom-in on the nested image. One remaining gate: the new interaction contract is untested.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Approved at 9b033f3

Macroscope's review found this PR approvable — This is a localized web UI fix that wires assistant-rendered images into the existing expanded-preview flow, including workspace images and keyboard activation, without changing unrelated markdown behavior or product defaults. The remaining test-coverage concern is maintainability-oriented and does not indicate substantial runtime risk.

^{You can add or adjust custom eligibility rules. Learn more.}