OpenPlanr in Cursor

In Cursor, OpenPlanr's skills arrive as project rules. You use a skill by mentioning its rule in chat, and Cursor can also apply a rule when your request matches the rule's description. Skills and the openplanr CLI add no model calls or telemetry.

Install

Cursor installs per project, so run the setup step from Install and set up OpenPlanr inside your repository and choose Cursor with project scope. Setup shows exactly what it will write before it writes anything, then adds thin .mdc discovery rules under .cursor/rules/openplanr/.

The repository must be a Git repository or an initialized OpenPlanr project. User scope is not supported for Cursor.

Restart Cursor after setup so it loads the new rules.

Use a skill

Mention the skill's rule in chat with your request. Each rule is named after its skill with a planr- prefix, and you mention it with an @ sign. When a skill needs a decision from you, it asks in the chat.

Set Commands for to Cursor, in the page header or in the navigation menu on a phone, and every skill command in these docs shows the rule to mention in Cursor.

Let Cursor see every skill

Generate OpenPlanr's rule files for Cursor:

openplanr rules generate --target cursor

This writes OpenPlanr's .mdc rule files into .cursor/rules/.

When something goes wrong

• E_PROJECT_CONTEXT_REQUIRED. Change into a Git repository or an initialized OpenPlanr project before you set up Cursor.
• A rule is missing. Run openplanr doctor --json, which lists every managed installation, then restart Cursor.
• You want to remove it. openplanr runtime remove cursor deletes only the files OpenPlanr wrote and still recognizes. Modified or unknown files are reported and left in place.

More fixes are in Troubleshooting, and the host matrix shows what differs between agents.