render-images-in-cursor

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Render Images in Cursor

在Cursor中渲染图片

Cursor chat renders an image reliably only when the file lives INSIDE the open workspace. Image tools often save to folders outside it (for example an assets folder under the Cursor projects directory) and claim the image "is already displayed" — the user then sees nothing, with no error. Inline chat rendering is also a newer, rollout-dependent Cursor feature, so always add the editor-tab fallback.

Cursor聊天仅当图片文件位于当前打开的工作区内时，才能可靠渲染图片。图片工具通常会将图片保存到工作区外的文件夹（例如Cursor项目目录下的assets文件夹），并声称图片“已显示”——但用户实际上看不到任何内容，也没有错误提示。聊天内联渲染也是Cursor的一项较新功能，依赖于版本推送，因此务必添加编辑器标签页作为备用方案。

Workflow

工作流程

Copy the image into the open workspace. Any workspace folder works; prefer the repo's temp folder:

bash

mkdir -p tmp/mockups
cp "$IMAGE_PATH" tmp/mockups/my-image.png

Embed it in the chat reply with plain markdown pointing at the in-workspace file, using its full absolute path:

markdown

![Short description](ABSOLUTE-WORKSPACE-PATH/tmp/mockups/my-image.png)

One embed per image, each on its own line, with a bold one-line label above it. Never trust an image tool's "already displayed" output — embed explicitly every time.

Also open each image as an editor tab — guaranteed visible even when inline chat rendering fails. With the cursor-app-control MCP server, call
```
open_resource
```
:

text

uri = file://ABSOLUTE-WORKSPACE-PATH/tmp/mockups/my-image.png

The file URI must point inside the workspace (or under the user's .cursor folder). Without that MCP server, run

cursor tmp/mockups/my-image.png

from the workspace root instead.

Verify with the user. Ask whether the images are visible. If inline rendering failed, the editor tabs from step 3 are the fallback — do not just resend the same markdown.

将图片复制到当前打开的工作区内。工作区内的任意文件夹均可；优先使用仓库的临时文件夹：

bash

mkdir -p tmp/mockups
cp "$IMAGE_PATH" tmp/mockups/my-image.png

在聊天回复中嵌入图片，使用指向工作区内文件的纯Markdown语法，需使用完整的绝对路径：

markdown

![简短描述](ABSOLUTE-WORKSPACE-PATH/tmp/mockups/my-image.png)

每张图片单独嵌入，各占一行，上方添加一行加粗的单行标签。永远不要信任图片工具的“已显示”输出——每次都要显式嵌入。

同时将每张图片在编辑器标签页中打开——即使聊天内联渲染失败，也能确保图片可见。借助cursor-app-control MCP server，调用
```
open_resource
```
：

text

uri = file://ABSOLUTE-WORKSPACE-PATH/tmp/mockups/my-image.png

文件URI必须指向工作区内（或用户的.cursor文件夹下）。如果没有该MCP server，可从工作区根目录运行

cursor tmp/mockups/my-image.png

替代。

向用户确认。询问用户是否能看到图片。如果内联渲染失败，步骤3中的编辑器标签页就是备用方案——不要只是重新发送相同的Markdown。

Failure modes

失效场景

Image saved outside the workspace: chat renders nothing, silently. Copy it into the workspace first (step 1) and embed the in-workspace path.
Markdown renders as a plain file link, not a picture: the user's Cursor build lacks inline chat images; rely on the editor tabs from step 3.
```
open_resource
```
rejects the URI: the file is outside the workspace; fix the path via step 1.
macOS
```
open
```
shows the image in Preview, outside Cursor — last resort only.

图片保存到工作区外：聊天界面无任何显示，无提示。先将图片复制到工作区内（步骤1），再嵌入工作区内的路径。
Markdown显示为纯文件链接而非图片：用户的Cursor版本不支持聊天内联图片；依赖步骤3的编辑器标签页。
```
open_resource
```
拒绝URI：文件位于工作区外；通过步骤1修正路径。
macOS
```
open
```
在Preview中打开图片（而非Cursor内）：仅作为最后手段。