Bug Report: Local plugins with symlinks don't load in Cursor

Bug Report: Local plugins with symlinks don't load in Cursor

Summary

Plugins installed in ~/.cursor/plugins/local/ via symlinks are not loaded by Cursor. The same plugins work when copied (real directories) instead of symlinked.

Environment

• OS: macOS (darwin)
• Cursor: Latest
• Plugin location: ~/.cursor/plugins/local/<plugin-name>/

Steps to reproduce

1. Create a valid Cursor plugin with .cursor-plugin/plugin.json, agents/, skills/, commands/.
2. Symlink it to ~/.cursor/plugins/local/my-plugin:

   ln -sf /path/to/my-plugin ~/.cursor/plugins/local/my-plugin
   

3. Reload Cursor window (Cmd+Shift+P → Reload Window).
4. Result: Plugin does not appear or load (generic icon, "Imported" label, commands/skills unavailable).

Expected behavior

Plugin loads and works like marketplace plugins (custom icon, commands, skills, agents available).

Actual behavior

Plugin does not load. Components (agents, skills, commands) are not discovered or available.

Workaround

Copy the plugin instead of symlinking:

cp -R /path/to/my-plugin ~/.cursor/plugins/local/my-plugin

After copying, the plugin loads correctly.

Impact

• Local development workflows that use symlinks to keep plugins in sync with a repo are broken.
• Users must copy on every update instead of symlinking once.

References

• Cursor docs: plugins go in ~/.cursor/plugins/local/<plugin-name>/
• create-plugin skill: "Default: ~/.cursor/plugins/local//"
• No documentation states that symlinks are unsupported.

No implementation files or tests are named. First reproduce the issue with a symlinked plugin and compare it with a copied plugin, then locate the local-plugin discovery and loading entry point. Done means a valid plugin symlinked under ~/.cursor/plugins/local/ loads with its icon, commands, skills, and agents available.