main.js · part 230

60 text occurrences from desktop/Cursor.app/Contents/Resources/app/extensions/cursor-agent-host/dist/main.js, part 230. Every entry preserves the shipped literal and its saved verdict or selection reason.

File contents and all parts · All files

Failed to save generated image: ${r}

rejected (reason=${e})

Failed to save generated image: ${r}

Failed to find tool call context

No space left on device

Failed to save generated image: ${r}

Failed to save generated image: ${r}

Failed to save generated image: ${r}

unknown result case

Failed to save generated image: ${r}

unhandled case: ${String(e.case)}

Failed to save generated image: ${r}

[generate-image] write failed

[generate-image] write success

Unhandled version: ${e}

Generate an image file from a text description.

STRICT INVOCATION RULES (must follow):
- Only use this tool when the user explicitly asks for an image. Do not generate images "just to be helpful".
- Do not use this tool for data heavy visualizations such as charts, plots, tables.

General guidelines:
- Provide a concrete description first: subject(s), layout, style, colors, text (if any), and constraints.
- If the user requests an aspect ratio, set `aspect_ratio` to one of "1:1", "4:3", "3:4", "16:9", or "9:16".
- If the user provides reference images, include them in `reference_image_paths`.
- Do not repeat generated images as Markdown in your response; the client displays tool-generated images automatically.

Examples that should call this tool:
- user: "Generate an app icon for a note-taking app, minimal flat vector style." (explicitly requests an image asset)
- user: "Make a UI mockup of a settings screen with a dark mode toggle." (explicitly requests a UI mockup)
- user: "Generate an asset of a game character with a sword." (explicitly requests a visual asset)

Examples that should not call this tool:
- user: "Create a plan to refactor this module." (planning request; respond in text or mermaid diagram)
- user: "Generate a chart of sales and revenue using data.csv." (data visualization; generate via code)

Unhandled version: ${e}

GenerateImage is not available for the current selected model. If important to generate an image (e.g. the user asked for it), then ask the user to switch models.

[generate-image] short/suspicious prompt rejected

Image generation was not performed — the tool call appears to be unintended. Do not retry or call GenerateImage again unless the user explicitly asks for an image.

[generate-image] no project folder available to save the generated image

generate_image needs a workspace/project folder so it has somewhere to save the PNG. Open a folder or run from a workspace, then try again.

[generate-image] aborted

Unhandled finish stage: ${e}

Successfully generated image. Display it in your response using:
<img src="${e}" alt="Generated image" />

Successfully generated image at: ${e}
Always use this absolute path when referring to the image. Do not repeat this image as a Markdown reference; it is already displayed to the user.

Failed to generate image: no image data returned

Successfully generated image at: ${e}
Always use this absolute path when referring to the image. Do not repeat this image as a Markdown reference; it is already displayed to the user.

Successfully generated image at: ${e.result.value.filePath}
Always use this absolute path when referring to the image. Do not repeat this image as a Markdown reference; it is already displayed to the user.

Failed to generate image, error: ${e.result.value.error}

An unknown error occurred.

PR code tour reads are unavailable in this session.

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

Natural-language instructions for regenerating the PR code tour, such as 'make it shorter' or 'focus on review risks'. Do not combine with markdown or artifactPath.

COMPLETE revision id to edit in place. Required for replace, section patch, and attach. From <pr_code_tour_context> or GetPrCodeTour.

Replacement markdown for the whole tour, or the new section body when heading is also set.

ATX heading text or slug of the target section. With markdown: replace that section only. With artifactPath: attach the media into that file-anchored section (defaults to the last file-anchored section).

Media artifact to attach to the revision as visible, playable step media: an image (png/jpeg/gif/webp) or a recording (.mp4/.webm), given as a workspace artifact path (e.g. /opt/cursor/artifacts/demo.mp4) or an artifact URL this agent owns. Images must already be uploaded (walkthrough artifacts upload when referenced in a response or PR body). Recordings upload from the VM on attach, so a recording saved under the artifacts directory can be attached right after it is captured. Provide with revisionId. The attach fails with an actionable error rather than storing media a reader cannot see.

Optional alt text for an attached artifact; rendered as the media's caption.

Optional commit-subset base SHA. Provide together with headSha to generate the tour from the baseSha..headSha range instead of the full PR diff.

Optional commit-subset head SHA. Provide together with baseSha to generate the tour from the baseSha..headSha range instead of the full PR diff.

Revision id to seed regeneration from (see <pr_code_tour_context>). Ignored for in-place edits.

Commit SHAs selecting a subset of the pull request's commits. When set, the subset selection takes effect for tour regeneration; omit or pass an empty list for the full diff.

Verbatim user prompt that takes effect for tour regeneration, kept distinct from agent-authored feedback.

Edit the PR code tour for the active PR. Replace markdown, patch a section by heading, attach an image or recording artifact (recordings upload from the VM on attach; the media lands as visible, playable media in a file-anchored section), or regenerate from feedback. In-place edits key by revisionId from <pr_code_tour_context> or GetPrCodeTour; GetPrCodeTour reads the write back. Pass feedback alone to regenerate. Pass baseSha and headSha together to scope regeneration to a commit range.

baseSha and headSha must be provided together to scope the tour to a commit range

cannot mix feedback with markdown or artifactPath

cannot mix markdown with artifactPath

provide feedback, or revisionId plus markdown or artifactPath

Commit-subset tours require server-side regeneration; omit baseSha and headSha to record a full-PR tour update

In-place PR code tour edits require server-side revision storage; use feedback to regenerate when server editing is unavailable.

Tour update recorded. Open the PR Review Tour tab to stream and save the new revision.

Error updating PR code tour: ${e.result.value.error}

Unknown PR code tour update result

Unhandled result case: ${String(t)}

Object expected.