main.js · part 282

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

File contents and all parts · All files

cannot represent tool call arguments of type ${typeof t} as a JSON object or raw text

[File: ${e.name??"unnamed"}]

data:${"string"==typeof t&&""!==t.trim()?t:B};base64,${Buffer.from(e).toString("base64")}

use strict

PiBashExecArgs|1 command 9|2 timeout 1?

PiBashExecResult|1 success #0 result|2 error #1 result

PiBashExecSuccess|1 output 9|2 truncation #0?|3 full_output_path 9?

PiBashExecError|1 error 9|2 truncation #0?|3 full_output_path 9?

use strict

PiFindExecArgs|1 pattern 9|2 path 9?|3 limit 5?

PiFindExecResult|1 success #0 result|2 error #1 result

PiFindExecSuccess|1 output 9|2 truncation #0?|3 result_limit_reached 13?

PiFindExecError|1 error 9

use strict

use strict

WebFetchAllowlistPrecheckArgs|1 url 9|2 tool_call_id 9?

WebFetchAllowlistPrecheckResult|1 allowlisted 8

use strict

Invalid URL protocol: the URL must start with `http:` or `https:`.

Invalid URL: The URL argument must be a non-null object.

Invalid URL protocol: the URL must start with `http:` or `https:`.

Invalid URL: port must be a valid integer or a string representation of an integer.

Invalid URL path: the path must be a string or null/undefined.

Invalid URL pathname: the pathname must be a string or null/undefined.

Invalid URL hostname: the hostname must be a string or null/undefined.

Invalid URL origin: the origin must be a string or null/undefined.

invalid url

handler must be an object

invalid onConnect method

invalid onError method

invalid onBodySent method

invalid onUpgrade method

invalid onHeaders method

invalid onData method

invalid onComplete method

Query params cannot be passed when url already contains "?" or "#".

The operation was aborted

use strict

use strict

use strict

Application Support

Could not determine the current user home directory for agent store path resolution

Unsupported agent store platform: ${t.platform}

Agent store base must be absolute: ${e}

Agent id must be a single safe path segment: ${e}

Mount key must be an agent store source id, agent store id, or store-<digest> share id: ${e}

Refusing to use symlinked agent store path: ${e}

Refusing to use symlinked agent store path: ${s}

Agent store path is not a directory: ${s}

Refusing to create ${n} outside trusted base ${s}

NT AUTHORITY\SYSTEM

Could not verify ACL for agent store path: ${e}

Refusing agent store path with unexpected ACL entry: ${t}

Agent store parent must not be group/world writable: ${e}

Refusing to use symlinked agent store path: ${e}

Agent store path is not a directory: ${e}

Agent store path is owned by uid ${t.uid}, expected ${s}: ${e}

Agent store path must not be group/world accessible: ${e}

Could not determine current uid for agent store path validation

Trusted directory does not exist: ${e}