Cursor Extension

The CodeLoop Cursor extension is the fastest way to enable always-on activation. On the first time it sees a workspace, it writes the CodeLoop rule to <workspace>/.cursor/rules/codeloop.mdc — Cursor's documented project-rule mechanism — so the verify / diagnose / gate loop fires automatically without you editing settings or pasting anything.

Install (recommended path)

Run this once and restart Cursor:

npx codeloop@latest install-cursor-extension

The CLI ships the latest extension VSIX bundled inside the npm tarball, so you get the same fixed build the team is running — no marketplace dependency, no GitHub release lookup. Requires codeloop@0.1.22 or newer.

What the extension does

• Writes <workspace>/.cursor/rules/codeloop.mdc with proper MDC frontmatter (alwaysApply: true) so every agent turn picks it up. Project rules win over User Rules in Cursor's precedence order, so this is strictly stronger than a manual paste.
• Idempotent — re-runs are a no-op when the file already matches; drift (a newer rule version on disk) is silently corrected. Sibling *.mdc rules in the same directory are never touched.
• When no folder is open in Cursor, falls back to a single informational toast offering Copy Rule / Open Settings / Don't show again. The dismissal is remembered in globalState, so you never see the prompt again on that machine.
• Surfaces a CodeLoop: Run Doctor command in the command palette that opens a terminal and runs npx codeloop doctor.

Known issue: cursor.rules.userRules is not a registered configuration

If you see a warning toast "CodeLoop could not write Cursor User Rules automatically (Unable to write to User Settings because cursor.rules.userRules is not a registered configuration.)" on every Cursor startup, you have the broken 0.1.0 marketplace build installed. The fix is one command:

npx codeloop@latest install-cursor-extension

Then quit Cursor (Cmd-Q on macOS, fully exit on Windows / Linux — not just close the window) and reopen. The CLI force-installs 0.1.1 over the broken version with cursor --install-extension --force, the warning will not return, and you will see .cursor/rules/codeloop.mdc appear in your workspace the first time you open a folder.

Verify the install

Run codeloop doctor from your terminal — every check in the Always-on activation section should be green:

• ~/.cursor/mcp.json contains a codeloop server entry.
• The CodeLoop Cursor extension is installed (run cursor --list-extensions | grep codeloop — expect codelooptech.codeloop-cursor-extension).
• Your workspace has .cursor/rules/codeloop.mdc (after the first Cursor open).
• Your project has .codeloop/config.json (run npx codeloop init if missing).

Settings & commands

The extension surfaces these commands in the command palette (Cmd/Ctrl+Shift+P, prefix "CodeLoop"):

Two settings live under Cursor > Settings > Extensions > CodeLoop:

• codeloop.autoInstallRule (default true) — auto-write the project rule on Cursor startup.
• codeloop.userRulePath (default empty) — override the snippet source path (defaults to ~/.cursor/codeloop-user-rule.md, written by codeloop init --global).

Telemetry

The extension itself sends zero telemetry. Any usage events come from the MCP server it registers, and they obey the same privacy contract documented in Security & data handling (counters only, never source / screenshots / logs).

Updating the extension

The marketplace listing currently serves the broken 0.1.0. Until the new version is published, the canonical update path is:

npx codeloop@latest install-cursor-extension

Each codeloop CLI release ships the latest packaged VSIX in assets/, so a CLI update is also an extension update.

Related

• Cursor setup (manual path, uses User Rules)
• Quick Start
• Troubleshooting
• Cross-OS Runbook
• Security & data handling