daemon.cjs · part 325

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

File contents and all parts · All files

The file ${path53} has been updated.

${occurrencesModified} ${occurrenceLabel} in file ${path53} ${verb} been updated.

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.

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

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.${pathOrderLine}
- 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 ${writeToolName} tool instead.

use strict

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

Total str-replace operations

Successful str-replace operations

Failed str-replace operations

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)

use strict

use strict

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(readResult.result)}

Wrote contents to ${path53}

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.

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.

Writes a file to the local filesystem.

use strict

The URL to fetch

Unhandled finish stage: ${exhaustiveCheck}

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

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

Successfully generated image at: ${result.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: ${result.result.value.error}

An unknown error occurred.

 (code=${providerCode})

Image generation request rejected by provider