main.js · part 224

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

File contents and all parts · All files

Latency of str-replace operations in milliseconds

Number of times whitespace-insensitive fallback was used

Number of lines modified in str-replace operations

The absolute path to the file to modify

The text to replace

The text to replace it with (must be different from old_string)

Replace all occurrences of old_string (default false)

The path to the file to modify. Always specify the target file as the first argument. You can use either a relative path in the workspace or an absolute path.

The text to replace

The text to replace it with (must be different from old_string)

Replace all occurences of old_string (default false)

Performs exact string replacements in files.

Performs exact string replacements in files.

Usage:
- When editing text, ensure you preserve the exact indentation (tabs/spaces) as it appears before.
- ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required.
- Only use emojis if the user explicitly requests it. Avoid adding emojis to files unless asked.
- The edit will FAIL if old_string is not unique in the file. Either provide a larger string with more surrounding context to make it unique or use replace_all to change every instance of old_string.
- Use replace_all for replacing and renaming strings across the file. This parameter is useful if you want to rename a variable for instance.
- To create or overwrite a file, you should prefer the write tool.

Performs exact string replacements in files.

Usage:
- When editing text, ensure you preserve the exact indentation (tabs/spaces) as it appears before.
- Only use emojis if the user explicitly requests it. Avoid adding emojis to files unless asked.
- The edit will FAIL if old_string is not unique in the file. Either provide a larger string with more surrounding context to make it unique or use replace_all to change every instance of old_string.${r?.isComposer15?"\n- The edit will FAIL if path isn’t given as the first argument. Always provide path first.":""}
- Use replace_all for replacing and renaming strings across the file. This parameter is useful if you want to rename a variable for instance.
- Optional parameter: replace_all (boolean, default false) — if true, replaces all occurrences of old_string in the file.

If you want to create a new file, use the ${e} tool instead.

- The edit will FAIL if path isn’t given as the first argument. Always provide path first.

${r} ${1===r?"occurrence":"occurrences"} in file ${e} ${1===r?"has":"have"} been updated.

The file ${e} has been updated.

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

The absolute path to the file to modify

The contents to write to the file

The path to the file to modify. Always specify the target file as the first argument. You can use either a relative path in the workspace or an absolute path.

The contents of the file to write

Unknown error

Unknown error

Unknown error

File is not a text file (binary data)

File is not a text file (binary data)

Read permission denied

Read permission denied

Unhandled readResult.result: ${String(l.result)}

Wrote contents to ${u}

Writes a file to the local filesystem.

Usage:
- This tool will overwrite the existing file if there is one at the provided path.
- If this is an existing file, you MUST use the read_file tool first to read the file's contents.
- ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required.
- NEVER proactively create documentation files (*.md) or README files. Only create documentation files if explicitly requested by the User.

Writes a file to the local filesystem.

Writes a file to the local filesystem.

Usage:
- This tool will overwrite the existing file if there is one at the provided path.
- If this is an existing file, you MUST use the read_file tool first to read the file's contents.
- ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required.
- NEVER proactively create documentation files (*.md) or README files. Only create documentation files if explicitly requested by the User.
- The write will FAIL if path isn’t given as the first argument. Always provide path first.

Writes a file to the local filesystem.

Usage:
- This tool will overwrite the existing file if there is one at the provided path.
- ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required.
- NEVER proactively create documentation files (*.md) or README files. Only create documentation files if explicitly requested by the User.

The URL to fetch

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

Generate image write results by case and location

Generate image aborts by phase and normalized reason

Generate image tool execute outcomes

Generate image tool execute failures by stage

End-to-end generate image execute latency in milliseconds

Generate image tool render outcomes

Generate image invocations where the description was rejected as too short or suspicious

${e.abortReasonName??""} ${e.abortReasonMessage??""}

createImageGenerationConcurrencyLimiter: maxConcurrent must be a finite number >= 1, got ${e}

A detailed description of the image.

Optional filename for the generated image (e.g., 'diagram.png'). Do not include a directory path - the tool automatically handles where to save and how to display the image. If not provided, a timestamped filename will be generated.

Optional array of file paths to reference images as additional inputs.

Optional aspect ratio for the generated image. Supported values are "1:1", "4:3", "3:4", "16:9", and "9:16".

The image provider blocked this request under its content policy. This often happens when the description names trademarked characters, brands, or real people. Try describing the subject in your own words instead.

The image provider is rate limiting requests right now (status ${t}). Try again in a moment.