main.js · part 230

60 text occurrences from desktop/Cursor.app/Contents/Resources/app/extensions/cursor-agent-exec/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

View an image on the local filesystem. This tool can only view IMAGE files. For normal file reads use the Shell tool.

- Lines in the output are numbered starting at 1, using following format: LINE_NUMBER|LINE_CONTENT

- Omit offset and limit to read the entire file.
- Provide offset and limit to read a specific line range (especially for long files).

- You can optionally specify a line offset and limit (especially handy for long files), but it's recommended to read the whole file by not providing these parameters.

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:
${a}
${i?`${o}.\n`:""}- 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:
${a}
${i?`${o}\n`:""}- 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:
${a}
${i?`${o}\n`:""}- 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.
${i?`${o}\n`:""}- 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: ${e}

The absolute path of the image to view.

Model accessed agent transcript path

Cannot read binary files of type ${e}

Read called with offset or limit

Using cached PDF text content

Converted PDF binary to text content

Unknown output type

Read operation rejected

File not found

Permission denied

Path is not a valid file to read

Unknown error

Cannot hydrate blobs for tool Read: no blob store available

Failed to hydrate blob ${r} for tool Read

Unknown error

Read image file: ${t}

File is empty.

File content (${r.value.fileSize} characters) exceeds maximum allowed characters (100000 characters).
Please use offset and limit parameters to read specific portions of the file, or use the 'grep' tool to search for specific content.

Unknown error: no output

Content blob not hydrated for render: ${t} (path: ${r.value.path})

${o}

${t}

${o}

${s}

${w}

${g}

${w}

${y}

Image blob not hydrated for render: ${o} (path: ${n})

Unknown error: no output case

Unhandled output case: ${e}

Error: ${r.value.errorMessage}

Unknown error

Unhandled result case: ${r}

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.

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.

ReadLints called with offset or limit

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

ReadLintsTool aborted

Failed to get diagnostics for ${r}: 

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

File not found

Permission denied

Unknown error

ReadLintsTool error message

Failed to get diagnostics for ${r}: