main.js · part 258

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

File contents and all parts · All files

${t.label}: confirmed but failed to trash the source

${e.label}: failed to trash the copy being replaced

${e.label}: failed to clean up a partial copy

Move skill to store

Move skill out of store

${t.label}: destination path is inside an existing skill

${t.label}: copy threw

Move skill to store

Move skill out of store

${e} requires relativePaths, a list of non-empty strings

Skill store move: overwrite prompt failed

${e} requires a non-empty skillFilePath

You are in the user's home directory—the starting point, not a project workspace. Handle **general tasks** here: questions, quick file/system exploration, one-off commands, and anything that isn't really tied to a single codebase. Use your judgment.

When the work belongs in a **project workspace**, infer or confirm the folder (recent paths, ~/Projects/, ~/Developer/, ~/repos/, and what the user said). If it's **clearly one existing project**, **always** use the `cursor-app-control` MCP's `move_agent_to_root` **before** you start making changes—edits, new files, installs, commits, or other project-scoped work—as soon as the path is known. Do that work only **after** the move; don't begin from home and relocate later. Working inside the project beats staying on home. If **which project or path is unclear**, use the ask question tool first. If **no suitable project exists**, help them create one, then call `move_agent_to_root` **before** any substantive project work, as soon as the directory exists.

## Questions About Cursor

When users ask how to use Cursor, configure settings, or have questions about Cursor features, use the cursor-guide skill to provide accurate, up-to-date answers.

## Creating New Projects

When a user wants to build something, help them get set up in a new project:

1. Use the ask question tool to confirm the project name. Suggest a sensible default based on what they described. Include a brief "any preferences for setup?" option—if they care about directory layout, git, or boilerplate they can say so; otherwise use sensible defaults.
2. Create the directory (prefer ~/Projects/ or ~/Developer/ if either exists, otherwise ~/), initialize git, and immediately call `move_agent_to_root` to move into the new project. Do this as soon as the folder exists—**before** making changes (scaffolding, installs, or anything else). Do not start project work from home and move afterward. Moving first gives you full workspace access for everything that follows.
3. Continue scaffolding starter files, installing dependencies, and completing any remaining setup inside the project workspace.

Keep setup frictionless by default—handle git, structure, and boilerplate without forcing decisions on things they may not care about. If they state preferences, respect them and go as deep as they want.

Home workspace guidance

Unhandled log level: ${r}

Unhandled log level: ${e}

 ${JSON.stringify(s)}

Unhandled log level: ${r}

${e.message}
${e.stack??""}

Object expected

Object not disposable

An error was suppressed during disposal

Event loop delay in milliseconds

Minimum event loop delay in milliseconds

Maximum event loop delay in milliseconds

Mean event loop delay in milliseconds

V8 heap used memory in megabytes

V8 heap total memory in megabytes

Resident set size memory in megabytes

External memory usage in megabytes

ArrayBuffers memory usage in megabytes

CPU user time percentage

CPU system time percentage

Event-loop delay measurement is already running

Event-loop delay measurement is not running

Excessive ripgrep invocations (agent-exec): ${e} spawns in ${n.windowMs}ms

Most recent ripgrep spawns from the agent-exec paths (agent grep/glob tool + ripwalk) before the storm threshold was crossed. No raw query text or paths are included.

[ripgrep-monitor] reported storm: ${e} spawns in ${n.windowMs}ms (top=${l})

[ripgrep-monitor] report failed: ${String(e)}

[ripgrep-monitor] enabled (window=${n.windowMs}ms threshold=${n.threshold} maxRecords=${n.maxRecords} report=${n.reportToSentry})

MCP plugin census

[cursor-agent-exec] Failed to get imported external plugins:

[cursor-agent-exec] Failed to get cursor third-party plugins:

[cursor-agent-exec] Failed to get effective user plugins for installed list:

[cursor-agent-exec] Failed to resolve project plugins for installed list:

Direct GitHub plugin installs are no longer supported. Use a marketplace instead.

Invalid local plugin variables key: ${e}

[cc-marketplace-import] ${e}

No workspace path available for project plugin installation

No workspace path available for project plugin removal

Failed to resolve installed plugins for component metadata

[primitive-authorship] git authorship failed: ${String(e)}

Cursor Plugins

[pluginsSubsystem] ${t}

[${s}] [${e}] ${t}

Unhandled plugin metrics log level: ${e}

[cursor-agent-exec] Failed to log plugin metrics:

Failed to get effective user plugins

[cursor-agent-exec] Ignoring project plugin with invalid gitUrl in .cursor/settings.json: key=${JSON.stringify(e)} gitUrl=${JSON.stringify(r)}

[cursor-agent-exec] Failed to resolve project plugins: