Cursor integration

Install a resolved plugin into Cursor:

agentrig plugin install cursor agentrig/agentrig.core-committer --scope personal

This copies each generated plugin into ~/.cursor/plugins/local/. Reload Cursor after installing. Refs resolve to the latest installable registry version by default; add @<version> only for an explicit reproducibility or rollback pin.

Install project-local Cursor plugins

agentrig plugin install cursor georg/georg.ts-master-plugin --scope workspace

This copies each generated plugin into <cwd>/.cursor/plugins/local/. Workspace scope is an AgentRig project-local convention so the plugin stays inside the repo instead of your global Cursor profile.

If you omit --scope, auto resolves Cursor installs to personal.

Uninstall Cursor plugins

agentrig plugin uninstall cursor agentrig/agentrig.core-committer

Uninstall is safe by default:

• AgentRig removes only files tracked in its install ledger
• modified plugin files are kept instead of being deleted
• workspace installs are removed from .cursor/plugins/local/ inside the repo
• personal installs are removed from ~/.cursor/plugins/local/
• install records include the concrete resolved version and registry snapshot digest

Generated provider files

AgentRig copies portable skills, translates mcp.json, and maps supported ai.agentrig components into Cursor's native plugin layout. It also generates CURSOR.md and rules/agentrig-provider.mdc pointers back to canonical plugin.json metadata and skills/*/SKILL.md instructions. Generated provider files are outputs; do not add Cursor target mappings to the source manifest.

Best practices

• Keep Cursor-specific files isolated in a plugin.
• Install third-party plugins through explicit registry aliases such as georg/georg.ts-master-plugin.
• Use --scope workspace when you want the Cursor plugin to stay repo-local and easy to remove with the project.