cursor-setup

Configure and verify the Cursor backend for Claude Code Harness environments.

3.1k|302|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/Chachamaru127/claude-code-harness --skill cursor-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cursor-setup
Source: https://github.com/Chachamaru127/claude-code-harness/tree/main/codex/.codex/skills/cursor-setup
Command: npx skills add https://github.com/Chachamaru127/claude-code-harness --skill cursor-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Switching Claude Code Harness to use Cursor as the implementation backend requires checking plugin readiness, locating the cursor-agent binary, and writing the right user- or project-scoped settings without accidentally changing distribution defaults. This Skill performs that setup and verification through the Harness helper scripts.

Core Features & Use Cases

  • Readiness check: Runs setup-cursor.sh --check, shows the resolved backend, and locates the cursor-agent binary in PATH or ~/.local/bin with symlink-safe detection.
  • Scoped default configuration: Sets Cursor as the implementation backend at user scope (--user-default) or project scope (--project-default) via set-impl-backend.sh.
  • Safe unset: Removes the Cursor default from either user or project scope after confirming which scope the user means.
  • Use Case: A developer wants their current repository to use Cursor for implementation work while keeping the distributed plugin default on Claude; they run cursor:setup --project-default and verify the resolved backend.

Quick Start

Ask the assistant to run cursor:setup --check to verify Cursor plugin and agent readiness in the current environment.

Frequently Asked Questions about cursor-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set Cursor as the default backend for Claude Code Harness?

Run cursor:setup --user-default to set Cursor at user scope, or cursor:setup --project-default to set it only for the current repository. Both commands use set-impl-backend.sh and then display the resolved configuration.

How do I check if the Cursor agent is ready to use?

Run cursor:setup --check. It runs setup-cursor.sh --check, shows the resolved backend, and locates the cursor-agent binary in PATH or ~/.local/bin, reporting its version if found.

Does cursor:setup change the distributed plugin defaults?

No. The distribution default remains opt-in with claude as the fallback. The skill only modifies local env or user settings when explicitly requested, never plugin manifests or shipped defaults.

Why does cursor:setup report cursor-agent not found?

The binary was not located in PATH or ~/.local/bin. The check resolves symlinks and only accepts paths containing a cursor-agent component, so generic agent binaries that do not resolve to Cursor are rejected.

How do I remove the Cursor backend default?

Run cursor:setup --unset. If the scope is unclear, the skill asks whether to target user or project scope, then runs set-impl-backend.sh --unset with the matching scope flag exactly once.