daemon.cjs · part 246

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

File contents and all parts · All files

Permission denied: ${result.value.error}

Unknown error

Unhandled result case: ${_exhaustiveCheck}

use strict

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

Permission denied: ${error3}

Permission denied: ${error3}

MCP server does not exist: ${serverIdentifier}

MCP server does not exist: ${serverIdentifier}

MCP server does not exist: ${serverIdentifier}. ${readServerDefReminder}

MCP tool does not exist: server=${serverIdentifier}, tool=${toolName}

MCP tool does not exist: ${toolName}

Error in call_mcp_tool: ${errorMessage3} without reading the tool definition

Tool execution error

Tool execution error

Blocked by Auto-review

Auto-review blocked this autonomous

<system_reminder>
${SMART_MODE_MCP_BLOCKED_AUTONOMOUS_REMINDER_LEAD} tool call. Decide now between two paths: (1) if a genuinely safer, lower-privilege, authorized path satisfies the request, use it; (2) if this blocked action is still necessary and the user should approve it, immediately retry the exact same call_mcp_tool call with requestSmartModeApproval set to true AND smartModeBlockReason set to the exact block reason text above. That retry is what shows the native approval card; stopping here leaves the user with no approval UI. Do not change the tool arguments or use an escalated variant when retrying for approval. Trying a different anonymous public file host, pastebin, disposable transfer link, or similar courier is NOT path (1) — that is the same unauthorized data-exposure crossing — so for that class prefer path (2) or ask the user, do not shop for another intermediary.
</system_reminder>

<system_reminder>
${SMART_MODE_MCP_BLOCKED_AUTONOMOUS_REMINDER_LEAD} MCP tool call. Decide now between two paths: (1) if a genuinely safer, lower-privilege, authorized path satisfies the request, use it; (2) if this blocked action is still necessary and the user should approve it, immediately retry the exact same CallDynamicTool call with mcpDetails.requestSmartModeApproval set to true AND mcpDetails.smartModeBlockReason set to the exact block reason text above. Preserve mcpDetails.description from the blocked call. That retry is what shows the native approval card; stopping here leaves the user with no approval UI. Do not change the tool arguments or use an escalated variant when retrying for approval. Trying a different anonymous public file host, pastebin, disposable transfer link, or similar courier is NOT path (1) — that is the same unauthorized data-exposure crossing — so for that class prefer path (2) or ask the user, do not shop for another intermediary.
</system_reminder>

Smart Mode preflight rejected the MCP call

MCP tool call

The MCP server rejected these arguments as invalid. Before retrying, inspect this MCP tool's input schema/tool definition and rebuild the arguments from that schema.

Tool execution error

Arguments to pass to the tool, as described by the tool descriptor.

Arguments to pass to the MCP tool, as described in the tool descriptor.

Identifier of the MCP server hosting the tool.

Name of the MCP tool to invoke.

Dynamic namespace hosting the tool, e.g. an MCP server.

Name of the tool to invoke.

Short plain-language description of what this call will do. One sentence naming the outcome and where it applies (channel, page, file, or service) when known. Do not include tool names, argument keys, or JSON.

Set to true when immediately retrying the exact same MCP call after Auto-review blocks it and you decide the user should approve it through the native approval card.

Provide the exact block reason returned by Auto-review in the prior rejection. Required when requestSmartModeApproval is true so the approval card shows the original classifier reason without re-running the classifier.

When true, the tool's result is written to a file under agent-tools/ in the workspace instead of being returned inline, regardless of its size; the result then reports the file path, size, and line count. Use it when you expect a large result that you want to read selectively or pass on to another tool by path. System reminders attached to the call are still returned inline.

MCP-specific call metadata. Set this only when invoking a tool from an external MCP namespace; omit it for first-party tools in the cursor namespace.

Missing required ${missingIdentity.length === 1 ? "field" : "fields"}: ${missingIdentity.join(", ")}. Re-issue the call with the tool's identity set; `arguments` alone does not identify the tool.

Failed to parse arguments string as JSON object. Re-issue the call with `arguments` as a JSON object literal rather than a quoted string.

Use ${resolvedGetMcpToolsToolName} to discover available ${useDynamicToolNamespaces ? "namespaces" : "servers"}.

Tool ${toolName} was not found. Use ${resolvedGetMcpToolsToolName} to discover available ${useDynamicToolNamespaces ? "namespaces" : "servers"} and their tools.

MCP file system options are required for CallMcpTool

Interactive MCP authentication is only available in the Cursor desktop IDE.

Interactive MCP authentication is only available in the Cursor desktop IDE.

Interactive MCP authentication is not available in this agent environment. Ask the user to authenticate the MCP server in the Cursor desktop IDE, then retry.

"${args.server}" is a built-in Cursor server that does not use interactive authentication.

${nonAuthenticatableMessage} If its tools are failing, the failure is not an authentication problem; read the tool error and address that instead.

Tool "${args.toolName}" on "${args.server}" is not available in this agent context.

${blockedMessage} It speaks to the end user on the parent agent's behalf and is reserved for the parent agent. Include anything you want communicated in your final response instead.

Built-in tool dispatch via CallDynamicTool

No built-in tools are available ${useDynamicToolNamespaces ? "in namespace" : "on server"} "${args.server}".

in namespace

on server

Built-in tool "${args.toolName}" not found ${useDynamicToolNamespaces ? "in namespace" : "on server"} "${args.server}". Available tools: ${availableTools.join(", ")}. Use ${resolvedGetMcpToolsToolName} to discover their schemas.

in namespace

on server

Dynamic tool execution failed

MCP tool call

You called this tool without first discovering its schema via ${resolvedGetMcpToolsToolName}. For future calls, call ${resolvedGetMcpToolsToolName} with {"${useDynamicToolNamespaces ? "namespace" : "server"}":"${args.server}","toolName":"${args.toolName}"} before calling ${name17}.