daemon.cjs · part 339

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

File contents and all parts · All files

Reads a file from the local filesystem. This tool can also read image files when called with the appropriate path. Formats supported: jpeg/jpg, png, gif, webp.

Reads a file from the local filesystem. You can access any file directly by using this tool.
If the User provides a path to a file assume that path is valid. It is okay to read a file that does not exist; an error will be returned.

Usage:
${offsetLimitUsageLines}
${shouldDescribeLineNumbers ? `${lineNumbersLine}.
` : ""}- You have the capability to call multiple tools in a single response. It is always better to speculatively read multiple files as a batch that are potentially useful.
- If you read a file that exists but has empty contents you will receive 'File is empty.'.

Reads a file from the local filesystem. You can access any file directly by using this tool.
If the User provides a path to a file assume that path is valid. It is okay to read a file that does not exist; an error will be returned.

Usage:
${offsetLimitUsageLines}
${shouldDescribeLineNumbers ? `${lineNumbersLine}
` : ""}- You have the capability to call multiple tools in a single response. It is always better to speculatively read multiple files as a batch that are potentially useful.
- If you read a file that exists but has empty contents you will receive 'File is empty.'

Image Support:
- This tool can also read image files when called with the appropriate path.
- Supported image formats: jpeg/jpg, png, gif, webp.

Reads a file from the local filesystem. You can access any file directly by using this tool.
If the User provides a path to a file assume that path is valid. It is okay to read a file that does not exist; an error will be returned.

Usage:
${offsetLimitUsageLines}
${shouldDescribeLineNumbers ? `${lineNumbersLine}
` : ""}- You have the capability to call multiple tools in a single response. It is always better to speculatively read multiple files as a batch that are potentially useful.
- If you read a file that exists but has empty contents you will receive 'File is empty.'

Image Support:
- This tool can also read image files when called with the appropriate path.
- Supported image formats: jpeg/jpg, png, gif, webp.

PDF Support:
- PDF files are converted into text content automatically (subject to the same character limits as other files).

Reads a file from the local filesystem. You can access any file directly by using this tool.
If the User provides a path to a file assume that path is valid. It is okay to read a file that does not exist; an error will be returned.

Usage:
- For partial file reads, use the line_range parameter with [start_line, end_line] format (1-indexed, inclusive). Example: [100, 150] reads lines 100 through 150.
- It's recommended to read the whole file by not providing line_range, unless the file is too large.
${shouldDescribeLineNumbers ? `${lineNumbersLine}
` : ""}- You have the capability to call multiple tools in a single response. It is always better to speculatively read multiple files as a batch that are potentially useful.
- If you read a file that exists but has empty contents you will receive 'File is empty.'

Image Support:
- This tool can also read image files when called with the appropriate path.
- Supported image formats: jpeg/jpg, png, gif, webp.

PDF Support:
- PDF files are converted into text content automatically (subject to the same character limits as other files).

Unhandled version: ${_exhaustive}

The absolute path of the image to view.

use strict

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

Optional. An array of paths to files or directories to read linter errors for. You can use either relative paths in the workspace or absolute paths. If provided, returns diagnostics for the specified files/directories only. If not provided, returns diagnostics for all files in the workspace.

Lints marked "stale" were computed on an older version of the file, and may be outdated.

ReadLints called with offset or limit

Failed to get diagnostics for ${path53}: Request timed out after 10 seconds

ReadLintsTool aborted

Failed to get diagnostics for ${path53}: 

Rejected - ${result2.result.value.reason}

File not found

Permission denied

Unknown error

ReadLintsTool error message

Failed to get diagnostics for ${path53}: 

Request timed out after 10 seconds

ReadLintsTool error

No diagnostics found for the specified paths

No linter errors found.

${fileDiag.path} (${fileDiag.diagnosticsCount} error${fileDiag.diagnosticsCount > 1 ? "s" : ""}):

  [${severity}] ${linePrefix}${diag.range?.start?.line ?? 0}:${diag.range?.start?.column ?? 0} - ${diag.message}${diag.source ? ` (${diag.source})` : ""}${staleSuffix}

 (${diag.source})

Found ${value.totalDiagnostics} linter error${value.totalDiagnostics > 1 ? "s" : ""} in ${value.totalFiles} file${value.totalFiles > 1 ? "s" : ""}:${output.join("\n")}

Error: ${result.value.errorMessage}

Unknown error

Unhandled result case: ${_exhaustiveCheck}

Read and display linter errors from the current workspace. You can provide paths to specific files or directories, or omit the argument to get diagnostics for all files.

Read linter warnings/errors. Only includes IDE diagnostics, which can occasionally be outdated. Optional paths array limits scope. Skip for unchanged files and ignore issues that existed before your changes.

Read and display linter errors from the current workspace. You can provide paths to specific files or directories, or omit the argument to get diagnostics for all files.

- If a file path is provided, returns diagnostics for that file only
- If a directory path is provided, returns diagnostics for all files within that directory
- If no path is provided, returns diagnostics for all files in the workspace
- This tool can return linter errors that were already present before your edits, so avoid calling it with a very wide scope of files
- NEVER call this tool on a file unless you've edited it or are about to edit it

Check for linter errors after substantive edits.

Error recording CI findings: ${result.result.value.error}

Unknown CI investigation findings result

Unhandled result case: ${String(_exhaustive)}

use strict

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

One entry per failing CI check investigated. checkName and detailsUrl must match the check identity from the prompt verbatim.

Optional cross-check summary when multiple checks were investigated in one turn.

Recorded CI investigation findings for the Checks panel.

Record structured CI investigation results for the Checks panel after subagent investigation completes. Call once per investigation turn with one finding per failing check and an optional overall summary. Does not modify the repo or storage; findings are read from this tool call by the UI.

${index + 1}. [${source}] "${hit.title}" (id: ${hit.conversationId}, updated: ${updatedAt})

   snippet: ${hit.snippet}

No matching conversations found.

Found ${success.hits.length} conversation${success.hits.length === 1 ? "" : "s"}:

Additional matches were omitted because the result limit was reached.

The conversation search index is rebuilding; results may be incomplete.

Search stopped early; partial results were returned.