Skip to content

nanocoai/nanoclaw / .claude/skills/add-cursor

add-cursor

Flagged

Use Cursor (local Agent SDK) as a full agent provider — planning, tool orchestration, MCP tools, session resume — alongside or instead of Claude. Cursor-account sign-in or API key, held by the credential gateway. Per-group via `ncl groups config update --provider cursor`. Distinct from using Cursor as a cloud agent (those run on Cursor VMs and are not this provider).

# Remove the Cursor agent provider

Reverses every change `/add-cursor` makes and returns every group to the default provider. Safe to run when partially installed — skip any step whose target is already absent.

## 1. Switch cursor groups back to the default

List groups still on cursor and switch each one (each group's `memory/` tree stays on disk and readable; run `/migrate-memory` per group if its memory should carry back to Claude — see [docs/provider-migration.md](../../docs/provider-migration.md)):

```bash
ncl groups list
# for each group whose config shows provider=cursor:
ncl groups config update --id <group-id> --provider claude
ncl groups restart --id <group-id>
```

If a group's config also sets a Cursor model (for example `composer-2.5`), add `--model <model>` with a model the new provider accepts to that update; Claude cannot run a Cursor model name.

If `.env` has `DEFAULT_AGENT_PROVIDER=cursor`, change that key to `claude` (or another installed provider) now, so groups created after the restart do not pick the removed provider.

## 2. Delete the barrel imports

Delete (do not comment out) the `import './cursor.js';` line from each of:

- `src/providers/index.ts`
- `src/provider-contracts/index.ts`
- `container/agent-runner/src/providers/index.ts`
- `container/agent-runner/src/provider-contracts/index.ts`
- `setup/providers/index.ts`

## 3. Delete every copied file

```bash
rm -f src/providers/cursor.ts \
      src/providers/cursor-registration.test.ts \
      src/providers/cursor-host-contribution.test.ts \
      src/provider-contracts/cursor.ts \
      container/agent-runner/src/providers/cursor.ts \
      container/agent-runner/src/providers/cursor-auth.ts \
      container/agent-runner/src/providers/cursor-hook.ts \
      container/agent-runner/src/providers/cursor-gateway-probe.ts \
      container/agent-runner/src/providers/cursor-registration.test.ts \
      container/agent-runner/src/providers/cursor.factory.test.ts \
      container/agent-runner/src/providers/cursor-auth.test.ts \
      container/agent-runner/src/providers/cursor-hook.test.ts \
      container/agent-runner/src/providers/cursor.poll-loop.test.ts \
      container/agent-runner/src/providers/cursor.conformance.test.ts \
      container/agent-runner/src/providers/cursor.gateway-proxy.test.ts \
      container/agent-runner/src/provider-contracts/cursor.ts \
      setup/providers/cursor.ts \
      setup/providers/cursor.test.ts \
      setup/providers/cursor-registration.test.ts
```

Leave `container/agent-runner/src/provider-contracts/exchange-archive.ts` in place: it is core's shared exchange archive, not a skill file.

This skill itself (`.claude/skills/add-cursor/`) stays — it ships with trunk so the provider can be re-added later.

## 4. Remove the agent-runner dependency

```bash
cd container/agent-runner && bun remove @cursor/sdk && cd -
```

Do **not** edit `container/cli-tools.json` — this skill never added a CLI there.

## 5. Gateway credentials (optional)

The `Cursor` (`api2.cursor.sh/auth/exchange_user_api_key`) and `Cursor models` (`api.cursor.com/v1/models`) entries in the credential gateway grant nothing once the provider is gone. They are user data: remove them through your gateway's own tools only if the operator asks.

## 6. Per-group state (optional)

Each cursor group keeps its Cursor agent store, hooks, and self-authored skills under `data/v2-sessions/<group-id>/.cursor-shared/` and its skill links under `groups/<folder>/.cursor/`. Delete them only if the group will never return to cursor.

## 7. Rebuild and verify

```bash
pnpm run build
pnpm exec tsc -p container/agent-runner/tsconfig.json --noEmit
./container/build.sh build
pnpm test
cd container/agent-runner && bun test
```

All suites green and `ncl groups list` showing no cursor groups means the removal is complete. Restart the service (`launchctl kickstart -k gui/$(id -u)/<label>` on macOS, `systemctl --user restart <unit>` on Linux).
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall