fix(web): render markdown images from workspace files

[colonelpanic8]

What Changed

ChatMarkdown had no img renderer, so a markdown image whose source is a local path fell through to a bare <img src="docs/shots/portrait.png">. Local sources now resolve through the same signed workspace-asset URL that the file preview panel already uses.

• apps/web/src/components/ChatMarkdown.tsx — new img component. A source that resolves to a workspace file (relative to the thread cwd, absolute, or file://) is rendered from assets.createUrl({_tag: "workspace-file", …}). Remote http(s) sources pass through untouched.
• Sources the environment will not sign — outside the workspace root, deleted, not a previewable image type — degrade to the existing file chip rather than a broken image.
• Loaded images are click-to-open in the file preview, wrapped in a <button aria-label="Preview …"> following the pattern already used for annotation crops in MessagesTimeline.
• apps/web/src/index.css — .chat-markdown-image sizing (max 100% wide, 32rem tall, contained, bordered) and a loading placeholder. There was no image styling at all before.

Also lifted the duplicated file-chip label construction out of the a renderer into markdownFileLinkLabel so the image fallback builds the same label.

Why

The web origin only serves the client bundle. An unknown path falls through to the SPA handler in apps/server/src/http.ts, which answers with index.html — so every local-path image decoded as HTML and rendered as the broken-image icon. Only http(s) sources could ever have worked.

This matters because agents write these. Ask one to summarize UI work and it produces ![portrait pip](docs/shots/portrait.png) pointing at screenshots it just captured in the workspace; every one of them rendered broken.

The asset endpoint is the right lever rather than a new file-serving route: it already signs short-lived, claim-scoped URLs, already restricts to files inside the thread's workspace root, and already gates on previewable image types. The fix reuses that boundary instead of widening it, which is why an out-of-workspace path degrades to a chip instead of loading.

UI Changes

Before — a message with four workspace screenshots, all broken:

After — same message, same files:

Verification

New apps/web/src/components/ChatMarkdown.test.tsx covers the four cases: relative path, absolute path, refused asset (falls back to the chip), and remote URL (untouched). Confirmed the tests fail against the unmodified component — the baseline output is literally <img src="docs/shots/docked.png">.

cd apps/web && tsgo --noEmit
vp test run --project unit src/components/ChatMarkdown.test.tsx \
src/components/chat/MessagesTimeline.test.tsx src/markdown-list-indentation.test.tsx
vp lint apps/web/src/components/ChatMarkdown.tsx apps/web/src/components/ChatMarkdown.test.tsx
vp fmt --check apps/web/src/components/ChatMarkdown.tsx apps/web/src/index.css

Integrated web pass through test-t3-app: isolated dev environment, real project, the message above sent and rendered in the controlled browser. All four images load from /api/assets/…; a missing file renders the chip; a remote URL is passed through unchanged.

Not addressed here, to keep this focused: mobile's NativeMarkdownImage passes the raw href to <Image source={{uri}}> and has the same defect, but it needs async resolution on a different render path.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes — n/a, no motion

---

Note

Low Risk
Scoped to chat markdown rendering and reuses existing signed-asset boundaries; adds tests and a small link-parser guard.

Overview
Chat markdown workspace image paths no longer render as broken <img> tags pointing at filesystem paths. A new img renderer resolves relative, absolute, and file:// sources through useAssetUrlState (signed workspace-file URLs), leaves http(s) URLs unchanged, and shows a file chip when signing fails or the path is not a previewable image type.

MarkdownWorkspaceImage handles loading placeholders, onError fallback, and optional click-to-open in the file preview panel. File-chip labels are shared via markdownFileLinkLabel. resolveMarkdownFileLinkMeta now ignores protocol-relative (//…) URLs so they are not treated as workspace files. CSS adds .chat-markdown-image and a loading placeholder. ChatMarkdown.test.tsx covers the four main cases.

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

Note

Render workspace image files inline in chat markdown

• Adds a MarkdownWorkspaceImage component in ChatMarkdown.tsx that resolves local workspace image paths to signed asset URLs and renders them as <img> elements with lazy loading.
• Non-previewable local image paths fall back to a file chip (MarkdownFileLink); remote http(s) and protocol-relative URLs are left unchanged.
• Adds a guard in markdown-links.ts to prevent protocol-relative URLs (//...) from being treated as workspace file paths.
• Adds CSS in index.css for .chat-markdown-image and .chat-markdown-image-placeholder to constrain size and apply consistent visual styling.
• Adds cwd to the markdownComponentsuseMemo dependency array so image/link resolution updates when the working directory changes.

^{Macroscope summarized 9296530.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new user-facing functionality (rendering workspace images in markdown via signed asset URLs) rather than fixing existing behavior. The author is a first-time contributor to this repository. New features warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[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: aae71ecb-40d5-4931-a584-788e65e6b786

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{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 5f85c61. Configure here.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Workspace image rendering already shipped in #6433.

[colonelpanic8]

What Changed

ChatMarkdown had no img renderer, so a markdown image whose source is a local path fell through to a bare <img src="docs/shots/portrait.png">. Local sources now resolve through the same signed workspace-asset URL that the file preview panel already uses.

• apps/web/src/components/ChatMarkdown.tsx — new img component. A source that resolves to a workspace file (relative to the thread cwd, absolute, or file://) is rendered from assets.createUrl({_tag: "workspace-file", …}). Remote http(s) sources pass through untouched.
• Sources the environment will not sign — outside the workspace root, deleted, not a previewable image type — degrade to the existing file chip rather than a broken image.
• Loaded images are click-to-open in the file preview, wrapped in a <button aria-label="Preview …"> following the pattern already used for annotation crops in MessagesTimeline.
• apps/web/src/index.css — .chat-markdown-image sizing (max 100% wide, 32rem tall, contained, bordered) and a loading placeholder. There was no image styling at all before.

Also lifted the duplicated file-chip label construction out of the a renderer into markdownFileLinkLabel so the image fallback builds the same label.

Why

The web origin only serves the client bundle. An unknown path falls through to the SPA handler in apps/server/src/http.ts, which answers with index.html — so every local-path image decoded as HTML and rendered as the broken-image icon. Only http(s) sources could ever have worked.

This matters because agents write these. Ask one to summarize UI work and it produces ![portrait pip](docs/shots/portrait.png) pointing at screenshots it just captured in the workspace; every one of them rendered broken.

The asset endpoint is the right lever rather than a new file-serving route: it already signs short-lived, claim-scoped URLs, already restricts to files inside the thread's workspace root, and already gates on previewable image types. The fix reuses that boundary instead of widening it, which is why an out-of-workspace path degrades to a chip instead of loading.

UI Changes

Before — a message with four workspace screenshots, all broken:

After — same message, same files:

Verification

New apps/web/src/components/ChatMarkdown.test.tsx covers the four cases: relative path, absolute path, refused asset (falls back to the chip), and remote URL (untouched). Confirmed the tests fail against the unmodified component — the baseline output is literally <img src="docs/shots/docked.png">.

cd apps/web && tsgo --noEmit
vp test run --project unit src/components/ChatMarkdown.test.tsx \
src/components/chat/MessagesTimeline.test.tsx src/markdown-list-indentation.test.tsx
vp lint apps/web/src/components/ChatMarkdown.tsx apps/web/src/components/ChatMarkdown.test.tsx
vp fmt --check apps/web/src/components/ChatMarkdown.tsx apps/web/src/index.css

Integrated web pass through test-t3-app: isolated dev environment, real project, the message above sent and rendered in the controlled browser. All four images load from /api/assets/…; a missing file renders the chip; a remote URL is passed through unchanged.

Not addressed here, to keep this focused: mobile's NativeMarkdownImage passes the raw href to <Image source={{uri}}> and has the same defect, but it needs async resolution on a different render path.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes — n/a, no motion

---

Note

Low Risk
Scoped to chat markdown rendering and reuses existing signed-asset boundaries; adds tests and a small link-parser guard.

Overview
Chat markdown workspace image paths no longer render as broken <img> tags pointing at filesystem paths. A new img renderer resolves relative, absolute, and file:// sources through useAssetUrlState (signed workspace-file URLs), leaves http(s) URLs unchanged, and shows a file chip when signing fails or the path is not a previewable image type.

MarkdownWorkspaceImage handles loading placeholders, onError fallback, and optional click-to-open in the file preview panel. File-chip labels are shared via markdownFileLinkLabel. resolveMarkdownFileLinkMeta now ignores protocol-relative (//…) URLs so they are not treated as workspace files. CSS adds .chat-markdown-image and a loading placeholder. ChatMarkdown.test.tsx covers the four main cases.

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

Note

Render workspace image files inline in chat markdown

• Adds a MarkdownWorkspaceImage component in ChatMarkdown.tsx that resolves local workspace image paths to signed asset URLs and renders them as <img> elements with lazy loading.
• Non-previewable local image paths fall back to a file chip (MarkdownFileLink); remote http(s) and protocol-relative URLs are left unchanged.
• Adds a guard in markdown-links.ts to prevent protocol-relative URLs (//...) from being treated as workspace file paths.
• Adds CSS in index.css for .chat-markdown-image and .chat-markdown-image-placeholder to constrain size and apply consistent visual styling.
• Adds cwd to the markdownComponentsuseMemo dependency array so image/link resolution updates when the working directory changes.

^{Macroscope summarized 9296530.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new user-facing functionality (rendering workspace images in markdown via signed asset URLs) rather than fixing existing behavior. The author is a first-time contributor to this repository. New features warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[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: aae71ecb-40d5-4931-a584-788e65e6b786

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{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 5f85c61. Configure here.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Workspace image rendering already shipped in #6433.

[colonelpanic8]

What Changed

ChatMarkdown had no img renderer, so a markdown image whose source is a local path fell through to a bare <img src="docs/shots/portrait.png">. Local sources now resolve through the same signed workspace-asset URL that the file preview panel already uses.

• apps/web/src/components/ChatMarkdown.tsx — new img component. A source that resolves to a workspace file (relative to the thread cwd, absolute, or file://) is rendered from assets.createUrl({_tag: "workspace-file", …}). Remote http(s) sources pass through untouched.
• Sources the environment will not sign — outside the workspace root, deleted, not a previewable image type — degrade to the existing file chip rather than a broken image.
• Loaded images are click-to-open in the file preview, wrapped in a <button aria-label="Preview …"> following the pattern already used for annotation crops in MessagesTimeline.
• apps/web/src/index.css — .chat-markdown-image sizing (max 100% wide, 32rem tall, contained, bordered) and a loading placeholder. There was no image styling at all before.

Also lifted the duplicated file-chip label construction out of the a renderer into markdownFileLinkLabel so the image fallback builds the same label.

Why

The web origin only serves the client bundle. An unknown path falls through to the SPA handler in apps/server/src/http.ts, which answers with index.html — so every local-path image decoded as HTML and rendered as the broken-image icon. Only http(s) sources could ever have worked.

This matters because agents write these. Ask one to summarize UI work and it produces ![portrait pip](docs/shots/portrait.png) pointing at screenshots it just captured in the workspace; every one of them rendered broken.

The asset endpoint is the right lever rather than a new file-serving route: it already signs short-lived, claim-scoped URLs, already restricts to files inside the thread's workspace root, and already gates on previewable image types. The fix reuses that boundary instead of widening it, which is why an out-of-workspace path degrades to a chip instead of loading.

UI Changes

Before — a message with four workspace screenshots, all broken:

After — same message, same files:

Verification

New apps/web/src/components/ChatMarkdown.test.tsx covers the four cases: relative path, absolute path, refused asset (falls back to the chip), and remote URL (untouched). Confirmed the tests fail against the unmodified component — the baseline output is literally <img src="docs/shots/docked.png">.

cd apps/web && tsgo --noEmit
vp test run --project unit src/components/ChatMarkdown.test.tsx \
src/components/chat/MessagesTimeline.test.tsx src/markdown-list-indentation.test.tsx
vp lint apps/web/src/components/ChatMarkdown.tsx apps/web/src/components/ChatMarkdown.test.tsx
vp fmt --check apps/web/src/components/ChatMarkdown.tsx apps/web/src/index.css

Integrated web pass through test-t3-app: isolated dev environment, real project, the message above sent and rendered in the controlled browser. All four images load from /api/assets/…; a missing file renders the chip; a remote URL is passed through unchanged.

Not addressed here, to keep this focused: mobile's NativeMarkdownImage passes the raw href to <Image source={{uri}}> and has the same defect, but it needs async resolution on a different render path.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes — n/a, no motion

---

Note

Low Risk
Scoped to chat markdown rendering and reuses existing signed-asset boundaries; adds tests and a small link-parser guard.

Overview
Chat markdown workspace image paths no longer render as broken <img> tags pointing at filesystem paths. A new img renderer resolves relative, absolute, and file:// sources through useAssetUrlState (signed workspace-file URLs), leaves http(s) URLs unchanged, and shows a file chip when signing fails or the path is not a previewable image type.

MarkdownWorkspaceImage handles loading placeholders, onError fallback, and optional click-to-open in the file preview panel. File-chip labels are shared via markdownFileLinkLabel. resolveMarkdownFileLinkMeta now ignores protocol-relative (//…) URLs so they are not treated as workspace files. CSS adds .chat-markdown-image and a loading placeholder. ChatMarkdown.test.tsx covers the four main cases.

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

Note

Render workspace image files inline in chat markdown

• Adds a MarkdownWorkspaceImage component in ChatMarkdown.tsx that resolves local workspace image paths to signed asset URLs and renders them as <img> elements with lazy loading.
• Non-previewable local image paths fall back to a file chip (MarkdownFileLink); remote http(s) and protocol-relative URLs are left unchanged.
• Adds a guard in markdown-links.ts to prevent protocol-relative URLs (//...) from being treated as workspace file paths.
• Adds CSS in index.css for .chat-markdown-image and .chat-markdown-image-placeholder to constrain size and apply consistent visual styling.
• Adds cwd to the markdownComponentsuseMemo dependency array so image/link resolution updates when the working directory changes.

^{Macroscope summarized 9296530.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new user-facing functionality (rendering workspace images in markdown via signed asset URLs) rather than fixing existing behavior. The author is a first-time contributor to this repository. New features warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[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: aae71ecb-40d5-4931-a584-788e65e6b786

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{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 5f85c61. Configure here.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Workspace image rendering already shipped in #6433.

[colonelpanic8]

What Changed

ChatMarkdown had no img renderer, so a markdown image whose source is a local path fell through to a bare <img src="docs/shots/portrait.png">. Local sources now resolve through the same signed workspace-asset URL that the file preview panel already uses.

• apps/web/src/components/ChatMarkdown.tsx — new img component. A source that resolves to a workspace file (relative to the thread cwd, absolute, or file://) is rendered from assets.createUrl({_tag: "workspace-file", …}). Remote http(s) sources pass through untouched.
• Sources the environment will not sign — outside the workspace root, deleted, not a previewable image type — degrade to the existing file chip rather than a broken image.
• Loaded images are click-to-open in the file preview, wrapped in a <button aria-label="Preview …"> following the pattern already used for annotation crops in MessagesTimeline.
• apps/web/src/index.css — .chat-markdown-image sizing (max 100% wide, 32rem tall, contained, bordered) and a loading placeholder. There was no image styling at all before.

Also lifted the duplicated file-chip label construction out of the a renderer into markdownFileLinkLabel so the image fallback builds the same label.

Why

The web origin only serves the client bundle. An unknown path falls through to the SPA handler in apps/server/src/http.ts, which answers with index.html — so every local-path image decoded as HTML and rendered as the broken-image icon. Only http(s) sources could ever have worked.

This matters because agents write these. Ask one to summarize UI work and it produces ![portrait pip](docs/shots/portrait.png) pointing at screenshots it just captured in the workspace; every one of them rendered broken.

The asset endpoint is the right lever rather than a new file-serving route: it already signs short-lived, claim-scoped URLs, already restricts to files inside the thread's workspace root, and already gates on previewable image types. The fix reuses that boundary instead of widening it, which is why an out-of-workspace path degrades to a chip instead of loading.

UI Changes

Before — a message with four workspace screenshots, all broken:

After — same message, same files:

Verification

New apps/web/src/components/ChatMarkdown.test.tsx covers the four cases: relative path, absolute path, refused asset (falls back to the chip), and remote URL (untouched). Confirmed the tests fail against the unmodified component — the baseline output is literally <img src="docs/shots/docked.png">.

cd apps/web && tsgo --noEmit
vp test run --project unit src/components/ChatMarkdown.test.tsx \
src/components/chat/MessagesTimeline.test.tsx src/markdown-list-indentation.test.tsx
vp lint apps/web/src/components/ChatMarkdown.tsx apps/web/src/components/ChatMarkdown.test.tsx
vp fmt --check apps/web/src/components/ChatMarkdown.tsx apps/web/src/index.css

Integrated web pass through test-t3-app: isolated dev environment, real project, the message above sent and rendered in the controlled browser. All four images load from /api/assets/…; a missing file renders the chip; a remote URL is passed through unchanged.

Not addressed here, to keep this focused: mobile's NativeMarkdownImage passes the raw href to <Image source={{uri}}> and has the same defect, but it needs async resolution on a different render path.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes — n/a, no motion

---

Note

Low Risk
Scoped to chat markdown rendering and reuses existing signed-asset boundaries; adds tests and a small link-parser guard.

Overview
Chat markdown workspace image paths no longer render as broken <img> tags pointing at filesystem paths. A new img renderer resolves relative, absolute, and file:// sources through useAssetUrlState (signed workspace-file URLs), leaves http(s) URLs unchanged, and shows a file chip when signing fails or the path is not a previewable image type.

MarkdownWorkspaceImage handles loading placeholders, onError fallback, and optional click-to-open in the file preview panel. File-chip labels are shared via markdownFileLinkLabel. resolveMarkdownFileLinkMeta now ignores protocol-relative (//…) URLs so they are not treated as workspace files. CSS adds .chat-markdown-image and a loading placeholder. ChatMarkdown.test.tsx covers the four main cases.

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

Note

Render workspace image files inline in chat markdown

• Adds a MarkdownWorkspaceImage component in ChatMarkdown.tsx that resolves local workspace image paths to signed asset URLs and renders them as <img> elements with lazy loading.
• Non-previewable local image paths fall back to a file chip (MarkdownFileLink); remote http(s) and protocol-relative URLs are left unchanged.
• Adds a guard in markdown-links.ts to prevent protocol-relative URLs (//...) from being treated as workspace file paths.
• Adds CSS in index.css for .chat-markdown-image and .chat-markdown-image-placeholder to constrain size and apply consistent visual styling.
• Adds cwd to the markdownComponentsuseMemo dependency array so image/link resolution updates when the working directory changes.

^{Macroscope summarized 9296530.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new user-facing functionality (rendering workspace images in markdown via signed asset URLs) rather than fixing existing behavior. The author is a first-time contributor to this repository. New features warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[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: aae71ecb-40d5-4931-a584-788e65e6b786

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{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 5f85c61. Configure here.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Workspace image rendering already shipped in #6433.

[colonelpanic8]

What Changed

ChatMarkdown had no img renderer, so a markdown image whose source is a local path fell through to a bare <img src="docs/shots/portrait.png">. Local sources now resolve through the same signed workspace-asset URL that the file preview panel already uses.

• apps/web/src/components/ChatMarkdown.tsx — new img component. A source that resolves to a workspace file (relative to the thread cwd, absolute, or file://) is rendered from assets.createUrl({_tag: "workspace-file", …}). Remote http(s) sources pass through untouched.
• Sources the environment will not sign — outside the workspace root, deleted, not a previewable image type — degrade to the existing file chip rather than a broken image.
• Loaded images are click-to-open in the file preview, wrapped in a <button aria-label="Preview …"> following the pattern already used for annotation crops in MessagesTimeline.
• apps/web/src/index.css — .chat-markdown-image sizing (max 100% wide, 32rem tall, contained, bordered) and a loading placeholder. There was no image styling at all before.

Also lifted the duplicated file-chip label construction out of the a renderer into markdownFileLinkLabel so the image fallback builds the same label.

Why

The web origin only serves the client bundle. An unknown path falls through to the SPA handler in apps/server/src/http.ts, which answers with index.html — so every local-path image decoded as HTML and rendered as the broken-image icon. Only http(s) sources could ever have worked.

This matters because agents write these. Ask one to summarize UI work and it produces ![portrait pip](docs/shots/portrait.png) pointing at screenshots it just captured in the workspace; every one of them rendered broken.

The asset endpoint is the right lever rather than a new file-serving route: it already signs short-lived, claim-scoped URLs, already restricts to files inside the thread's workspace root, and already gates on previewable image types. The fix reuses that boundary instead of widening it, which is why an out-of-workspace path degrades to a chip instead of loading.

UI Changes

Before — a message with four workspace screenshots, all broken:

After — same message, same files:

Verification

New apps/web/src/components/ChatMarkdown.test.tsx covers the four cases: relative path, absolute path, refused asset (falls back to the chip), and remote URL (untouched). Confirmed the tests fail against the unmodified component — the baseline output is literally <img src="docs/shots/docked.png">.

cd apps/web && tsgo --noEmit
vp test run --project unit src/components/ChatMarkdown.test.tsx \
src/components/chat/MessagesTimeline.test.tsx src/markdown-list-indentation.test.tsx
vp lint apps/web/src/components/ChatMarkdown.tsx apps/web/src/components/ChatMarkdown.test.tsx
vp fmt --check apps/web/src/components/ChatMarkdown.tsx apps/web/src/index.css

Integrated web pass through test-t3-app: isolated dev environment, real project, the message above sent and rendered in the controlled browser. All four images load from /api/assets/…; a missing file renders the chip; a remote URL is passed through unchanged.

Not addressed here, to keep this focused: mobile's NativeMarkdownImage passes the raw href to <Image source={{uri}}> and has the same defect, but it needs async resolution on a different render path.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes — n/a, no motion

---

Note

Low Risk
Scoped to chat markdown rendering and reuses existing signed-asset boundaries; adds tests and a small link-parser guard.

Overview
Chat markdown workspace image paths no longer render as broken <img> tags pointing at filesystem paths. A new img renderer resolves relative, absolute, and file:// sources through useAssetUrlState (signed workspace-file URLs), leaves http(s) URLs unchanged, and shows a file chip when signing fails or the path is not a previewable image type.

MarkdownWorkspaceImage handles loading placeholders, onError fallback, and optional click-to-open in the file preview panel. File-chip labels are shared via markdownFileLinkLabel. resolveMarkdownFileLinkMeta now ignores protocol-relative (//…) URLs so they are not treated as workspace files. CSS adds .chat-markdown-image and a loading placeholder. ChatMarkdown.test.tsx covers the four main cases.

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

Note

Render workspace image files inline in chat markdown

• Adds a MarkdownWorkspaceImage component in ChatMarkdown.tsx that resolves local workspace image paths to signed asset URLs and renders them as <img> elements with lazy loading.
• Non-previewable local image paths fall back to a file chip (MarkdownFileLink); remote http(s) and protocol-relative URLs are left unchanged.
• Adds a guard in markdown-links.ts to prevent protocol-relative URLs (//...) from being treated as workspace file paths.
• Adds CSS in index.css for .chat-markdown-image and .chat-markdown-image-placeholder to constrain size and apply consistent visual styling.
• Adds cwd to the markdownComponentsuseMemo dependency array so image/link resolution updates when the working directory changes.

^{Macroscope summarized 9296530.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new user-facing functionality (rendering workspace images in markdown via signed asset URLs) rather than fixing existing behavior. The author is a first-time contributor to this repository. New features warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[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: aae71ecb-40d5-4931-a584-788e65e6b786

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{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 5f85c61. Configure here.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Workspace image rendering already shipped in #6433.

[colonelpanic8]

What Changed

ChatMarkdown had no img renderer, so a markdown image whose source is a local path fell through to a bare <img src="docs/shots/portrait.png">. Local sources now resolve through the same signed workspace-asset URL that the file preview panel already uses.

• apps/web/src/components/ChatMarkdown.tsx — new img component. A source that resolves to a workspace file (relative to the thread cwd, absolute, or file://) is rendered from assets.createUrl({_tag: "workspace-file", …}). Remote http(s) sources pass through untouched.
• Sources the environment will not sign — outside the workspace root, deleted, not a previewable image type — degrade to the existing file chip rather than a broken image.
• Loaded images are click-to-open in the file preview, wrapped in a <button aria-label="Preview …"> following the pattern already used for annotation crops in MessagesTimeline.
• apps/web/src/index.css — .chat-markdown-image sizing (max 100% wide, 32rem tall, contained, bordered) and a loading placeholder. There was no image styling at all before.

Also lifted the duplicated file-chip label construction out of the a renderer into markdownFileLinkLabel so the image fallback builds the same label.

Why

The web origin only serves the client bundle. An unknown path falls through to the SPA handler in apps/server/src/http.ts, which answers with index.html — so every local-path image decoded as HTML and rendered as the broken-image icon. Only http(s) sources could ever have worked.

This matters because agents write these. Ask one to summarize UI work and it produces ![portrait pip](docs/shots/portrait.png) pointing at screenshots it just captured in the workspace; every one of them rendered broken.

The asset endpoint is the right lever rather than a new file-serving route: it already signs short-lived, claim-scoped URLs, already restricts to files inside the thread's workspace root, and already gates on previewable image types. The fix reuses that boundary instead of widening it, which is why an out-of-workspace path degrades to a chip instead of loading.

UI Changes

Before — a message with four workspace screenshots, all broken:

After — same message, same files:

Verification

New apps/web/src/components/ChatMarkdown.test.tsx covers the four cases: relative path, absolute path, refused asset (falls back to the chip), and remote URL (untouched). Confirmed the tests fail against the unmodified component — the baseline output is literally <img src="docs/shots/docked.png">.

cd apps/web && tsgo --noEmit
vp test run --project unit src/components/ChatMarkdown.test.tsx \
src/components/chat/MessagesTimeline.test.tsx src/markdown-list-indentation.test.tsx
vp lint apps/web/src/components/ChatMarkdown.tsx apps/web/src/components/ChatMarkdown.test.tsx
vp fmt --check apps/web/src/components/ChatMarkdown.tsx apps/web/src/index.css

Integrated web pass through test-t3-app: isolated dev environment, real project, the message above sent and rendered in the controlled browser. All four images load from /api/assets/…; a missing file renders the chip; a remote URL is passed through unchanged.

Not addressed here, to keep this focused: mobile's NativeMarkdownImage passes the raw href to <Image source={{uri}}> and has the same defect, but it needs async resolution on a different render path.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes — n/a, no motion

---

Note

Low Risk
Scoped to chat markdown rendering and reuses existing signed-asset boundaries; adds tests and a small link-parser guard.

Overview
Chat markdown workspace image paths no longer render as broken <img> tags pointing at filesystem paths. A new img renderer resolves relative, absolute, and file:// sources through useAssetUrlState (signed workspace-file URLs), leaves http(s) URLs unchanged, and shows a file chip when signing fails or the path is not a previewable image type.

MarkdownWorkspaceImage handles loading placeholders, onError fallback, and optional click-to-open in the file preview panel. File-chip labels are shared via markdownFileLinkLabel. resolveMarkdownFileLinkMeta now ignores protocol-relative (//…) URLs so they are not treated as workspace files. CSS adds .chat-markdown-image and a loading placeholder. ChatMarkdown.test.tsx covers the four main cases.

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

Note

Render workspace image files inline in chat markdown

• Adds a MarkdownWorkspaceImage component in ChatMarkdown.tsx that resolves local workspace image paths to signed asset URLs and renders them as <img> elements with lazy loading.
• Non-previewable local image paths fall back to a file chip (MarkdownFileLink); remote http(s) and protocol-relative URLs are left unchanged.
• Adds a guard in markdown-links.ts to prevent protocol-relative URLs (//...) from being treated as workspace file paths.
• Adds CSS in index.css for .chat-markdown-image and .chat-markdown-image-placeholder to constrain size and apply consistent visual styling.
• Adds cwd to the markdownComponentsuseMemo dependency array so image/link resolution updates when the working directory changes.

^{Macroscope summarized 9296530.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new user-facing functionality (rendering workspace images in markdown via signed asset URLs) rather than fixing existing behavior. The author is a first-time contributor to this repository. New features warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[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: aae71ecb-40d5-4931-a584-788e65e6b786

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{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 5f85c61. Configure here.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Workspace image rendering already shipped in #6433.

[colonelpanic8]

What Changed

ChatMarkdown had no img renderer, so a markdown image whose source is a local path fell through to a bare <img src="docs/shots/portrait.png">. Local sources now resolve through the same signed workspace-asset URL that the file preview panel already uses.

• apps/web/src/components/ChatMarkdown.tsx — new img component. A source that resolves to a workspace file (relative to the thread cwd, absolute, or file://) is rendered from assets.createUrl({_tag: "workspace-file", …}). Remote http(s) sources pass through untouched.
• Sources the environment will not sign — outside the workspace root, deleted, not a previewable image type — degrade to the existing file chip rather than a broken image.
• Loaded images are click-to-open in the file preview, wrapped in a <button aria-label="Preview …"> following the pattern already used for annotation crops in MessagesTimeline.
• apps/web/src/index.css — .chat-markdown-image sizing (max 100% wide, 32rem tall, contained, bordered) and a loading placeholder. There was no image styling at all before.

Also lifted the duplicated file-chip label construction out of the a renderer into markdownFileLinkLabel so the image fallback builds the same label.

Why

The web origin only serves the client bundle. An unknown path falls through to the SPA handler in apps/server/src/http.ts, which answers with index.html — so every local-path image decoded as HTML and rendered as the broken-image icon. Only http(s) sources could ever have worked.

This matters because agents write these. Ask one to summarize UI work and it produces ![portrait pip](docs/shots/portrait.png) pointing at screenshots it just captured in the workspace; every one of them rendered broken.

The asset endpoint is the right lever rather than a new file-serving route: it already signs short-lived, claim-scoped URLs, already restricts to files inside the thread's workspace root, and already gates on previewable image types. The fix reuses that boundary instead of widening it, which is why an out-of-workspace path degrades to a chip instead of loading.

UI Changes

Before — a message with four workspace screenshots, all broken:

After — same message, same files:

Verification

New apps/web/src/components/ChatMarkdown.test.tsx covers the four cases: relative path, absolute path, refused asset (falls back to the chip), and remote URL (untouched). Confirmed the tests fail against the unmodified component — the baseline output is literally <img src="docs/shots/docked.png">.

cd apps/web && tsgo --noEmit
vp test run --project unit src/components/ChatMarkdown.test.tsx \
src/components/chat/MessagesTimeline.test.tsx src/markdown-list-indentation.test.tsx
vp lint apps/web/src/components/ChatMarkdown.tsx apps/web/src/components/ChatMarkdown.test.tsx
vp fmt --check apps/web/src/components/ChatMarkdown.tsx apps/web/src/index.css

Integrated web pass through test-t3-app: isolated dev environment, real project, the message above sent and rendered in the controlled browser. All four images load from /api/assets/…; a missing file renders the chip; a remote URL is passed through unchanged.

Not addressed here, to keep this focused: mobile's NativeMarkdownImage passes the raw href to <Image source={{uri}}> and has the same defect, but it needs async resolution on a different render path.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes — n/a, no motion

---

Note

Low Risk
Scoped to chat markdown rendering and reuses existing signed-asset boundaries; adds tests and a small link-parser guard.

Overview
Chat markdown workspace image paths no longer render as broken <img> tags pointing at filesystem paths. A new img renderer resolves relative, absolute, and file:// sources through useAssetUrlState (signed workspace-file URLs), leaves http(s) URLs unchanged, and shows a file chip when signing fails or the path is not a previewable image type.

MarkdownWorkspaceImage handles loading placeholders, onError fallback, and optional click-to-open in the file preview panel. File-chip labels are shared via markdownFileLinkLabel. resolveMarkdownFileLinkMeta now ignores protocol-relative (//…) URLs so they are not treated as workspace files. CSS adds .chat-markdown-image and a loading placeholder. ChatMarkdown.test.tsx covers the four main cases.

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

Note

Render workspace image files inline in chat markdown

• Adds a MarkdownWorkspaceImage component in ChatMarkdown.tsx that resolves local workspace image paths to signed asset URLs and renders them as <img> elements with lazy loading.
• Non-previewable local image paths fall back to a file chip (MarkdownFileLink); remote http(s) and protocol-relative URLs are left unchanged.
• Adds a guard in markdown-links.ts to prevent protocol-relative URLs (//...) from being treated as workspace file paths.
• Adds CSS in index.css for .chat-markdown-image and .chat-markdown-image-placeholder to constrain size and apply consistent visual styling.
• Adds cwd to the markdownComponentsuseMemo dependency array so image/link resolution updates when the working directory changes.

^{Macroscope summarized 9296530.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new user-facing functionality (rendering workspace images in markdown via signed asset URLs) rather than fixing existing behavior. The author is a first-time contributor to this repository. New features warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[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: aae71ecb-40d5-4931-a584-788e65e6b786

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{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 5f85c61. Configure here.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Workspace image rendering already shipped in #6433.

[colonelpanic8]

What Changed

ChatMarkdown had no img renderer, so a markdown image whose source is a local path fell through to a bare <img src="docs/shots/portrait.png">. Local sources now resolve through the same signed workspace-asset URL that the file preview panel already uses.

• apps/web/src/components/ChatMarkdown.tsx — new img component. A source that resolves to a workspace file (relative to the thread cwd, absolute, or file://) is rendered from assets.createUrl({_tag: "workspace-file", …}). Remote http(s) sources pass through untouched.
• Sources the environment will not sign — outside the workspace root, deleted, not a previewable image type — degrade to the existing file chip rather than a broken image.
• Loaded images are click-to-open in the file preview, wrapped in a <button aria-label="Preview …"> following the pattern already used for annotation crops in MessagesTimeline.
• apps/web/src/index.css — .chat-markdown-image sizing (max 100% wide, 32rem tall, contained, bordered) and a loading placeholder. There was no image styling at all before.

Also lifted the duplicated file-chip label construction out of the a renderer into markdownFileLinkLabel so the image fallback builds the same label.

Why

The web origin only serves the client bundle. An unknown path falls through to the SPA handler in apps/server/src/http.ts, which answers with index.html — so every local-path image decoded as HTML and rendered as the broken-image icon. Only http(s) sources could ever have worked.

This matters because agents write these. Ask one to summarize UI work and it produces ![portrait pip](docs/shots/portrait.png) pointing at screenshots it just captured in the workspace; every one of them rendered broken.

The asset endpoint is the right lever rather than a new file-serving route: it already signs short-lived, claim-scoped URLs, already restricts to files inside the thread's workspace root, and already gates on previewable image types. The fix reuses that boundary instead of widening it, which is why an out-of-workspace path degrades to a chip instead of loading.

UI Changes

Before — a message with four workspace screenshots, all broken:

After — same message, same files:

Verification

New apps/web/src/components/ChatMarkdown.test.tsx covers the four cases: relative path, absolute path, refused asset (falls back to the chip), and remote URL (untouched). Confirmed the tests fail against the unmodified component — the baseline output is literally <img src="docs/shots/docked.png">.

cd apps/web && tsgo --noEmit
vp test run --project unit src/components/ChatMarkdown.test.tsx \
src/components/chat/MessagesTimeline.test.tsx src/markdown-list-indentation.test.tsx
vp lint apps/web/src/components/ChatMarkdown.tsx apps/web/src/components/ChatMarkdown.test.tsx
vp fmt --check apps/web/src/components/ChatMarkdown.tsx apps/web/src/index.css

Integrated web pass through test-t3-app: isolated dev environment, real project, the message above sent and rendered in the controlled browser. All four images load from /api/assets/…; a missing file renders the chip; a remote URL is passed through unchanged.

Not addressed here, to keep this focused: mobile's NativeMarkdownImage passes the raw href to <Image source={{uri}}> and has the same defect, but it needs async resolution on a different render path.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes — n/a, no motion

---

Note

Low Risk
Scoped to chat markdown rendering and reuses existing signed-asset boundaries; adds tests and a small link-parser guard.

Overview
Chat markdown workspace image paths no longer render as broken <img> tags pointing at filesystem paths. A new img renderer resolves relative, absolute, and file:// sources through useAssetUrlState (signed workspace-file URLs), leaves http(s) URLs unchanged, and shows a file chip when signing fails or the path is not a previewable image type.

MarkdownWorkspaceImage handles loading placeholders, onError fallback, and optional click-to-open in the file preview panel. File-chip labels are shared via markdownFileLinkLabel. resolveMarkdownFileLinkMeta now ignores protocol-relative (//…) URLs so they are not treated as workspace files. CSS adds .chat-markdown-image and a loading placeholder. ChatMarkdown.test.tsx covers the four main cases.

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

Note

Render workspace image files inline in chat markdown

• Adds a MarkdownWorkspaceImage component in ChatMarkdown.tsx that resolves local workspace image paths to signed asset URLs and renders them as <img> elements with lazy loading.
• Non-previewable local image paths fall back to a file chip (MarkdownFileLink); remote http(s) and protocol-relative URLs are left unchanged.
• Adds a guard in markdown-links.ts to prevent protocol-relative URLs (//...) from being treated as workspace file paths.
• Adds CSS in index.css for .chat-markdown-image and .chat-markdown-image-placeholder to constrain size and apply consistent visual styling.
• Adds cwd to the markdownComponentsuseMemo dependency array so image/link resolution updates when the working directory changes.

^{Macroscope summarized 9296530.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new user-facing functionality (rendering workspace images in markdown via signed asset URLs) rather than fixing existing behavior. The author is a first-time contributor to this repository. New features warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[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: aae71ecb-40d5-4931-a584-788e65e6b786

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{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 5f85c61. Configure here.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Workspace image rendering already shipped in #6433.