Skip to content
Back to search

vanyangyang

Vanyangyang's developer tools, including Cursor Bridge and Grok Build Supervisor.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 15 Nov 2026. Its scripts were only partly scanned.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Vanyangyang/cursor-bridge with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Vanyangyang/cursor-bridge'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/vanyangyang--cursor-bridge/badge.svg)](/listings/vanyangyang--cursor-bridge)

HTML

<a href="/listings/vanyangyang--cursor-bridge"><img src="/api/listings/vanyangyang--cursor-bridge/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

> [!IMPORTANT] > **Prerequisite for the default `cli` route:** Install Cursor CLI in PowerShell with `irm 'https://cursor.com/install?win32=true' | iex` and run `cursor-agent login` (full guide: [Migrating from 6.x to 7.0.0](#migrate-to-7-0)). Prefer desktop Cursor IDE without CLI? Switch persistently with `/cce ide` after installing the plugin.

1. Install Cursor Bridge in your AI client

Commands are grouped by the AI client you already chat with:

Codex (recommended)

codex plugin marketplace add Vanyangyang/cursor-bridge --ref main
codex plugin add cursor-bridge@vanyangyang

Claude Code

claude plugin marketplace add Vanyangyang/cursor-bridge
claude plugin install cursor-bridge@vanyangyang

Grok Build

grok plugin marketplace add Vanyangyang/cursor-bridge
grok plugin install Vanyangyang/cursor-bridge --trust
grok plugin enable cursor-bridge

(`grok plugin install Vanyangyang/cursor-bridge --trust` also works directly.)

Pi

pi install npm:pi-cursor-bridge

<a id="other-mcp-hosts"></a>

Other MCP-capable AI clients

Give this prompt to the AI client you are already using:

Read https://github.com/Vanyangyang/cursor-bridge/blob/main/docs/ai-install.md completely. Install Cursor Bridge into this AI client. Follow every step. Report against the completion standard at the end. Use only the dedicated generic npm package named in the playbook. Do not invent a marketplace plugin, do not use a Pi package, and do not publish anything.

The playbook routes Codex, Claude Code, Grok, and Pi back to their first-class marketplace commands, and instructs any other MCP host to install `vanyangyang-cursor-bridge` into `%LOCALAPPDATA%\cursor-bridge\npm`. It tells the AI client where the bundle and skills landed so this AI client can register them, restart, and initialize the workspace. I do not treat that path as a first-class client and have not live-tested it.

2. Restart or reload your AI client

Restart Codex and start a new task, restart Claude Code or run `/reload-plugins`, reload Grok via `/plugins` or a new session, restart Pi, or restart your generic MCP host. Open sessions do not hot-load newly installed MCP tools or skills.

3. Configure explicit CCE model, check CLI readiness, and initialize your workspace

Account CLI requires an explicit named model and reasoning effort (`Auto` and `default` are rejected rather than silently selected). Tell your agent or set it once persistently:

Set my CCE default model to grok-4.6-fast with medium effort, verify with /cce doctor, and initialize CCE workspace to C:\absolute\path\to\project

- **Pi** automatically binds the directory where Pi was started; pass a new absolute path whenever you want to switch workspaces. - **If `cursor_init` returns `ready: false` (`cli-unavailable`, `cli-auth-required`, `cli-model-required`, `cli-model-unavailable`, or `cli-provider-unavailable`):** Your workspace binding is still saved (`bindingPersisted: true`), and the response includes `errorCode`, `availableModelsSample` (when available), and the exact `nextStep`. Fix the prerequisite (for example `cursor-agent login` or `cursor_model`) and re-run `cursor_init` or `/cce doctor`. To switch back to Cursor IDE/Agents instead, run `/cce ide`.

4. Ask a real project question

Who owns this state, and what is the complete path from save loading to runtime use and save write-back?

> [!TIP] > **Recommended on Windows 11: minimal runtime (when using IDE/Agents or `cursor_do`)** > > When routing CCE through `ide` or running `cursor_do`, say “Switch CCE to minimal mode.” Cursor, its project index, Agent DOM, and task queue keep running in the background while top-level Windows windows stay hidden. Cursor 3.23.12 hidden CCE is verified in both UI types; hidden mode verifies the current model and effort (change them in `normal` mode first if the chat uses `Auto`). >

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 27 lines
  1. {
  2. "name": "vanyangyang",
  3. "description": "Vanyangyang's developer tools, including Cursor Bridge and Grok Build Supervisor.",
  4. "owner": {
  5. "name": "Vanyangyang"
  6. },
  7. "plugins": [
  8. {
  9. "name": "cursor-bridge",
  10. "source": ".",
  11. "description": "Primary CLI-first Cursor Context Engine (isolated ACP with explicit model verification) and optional Cursor IDE/Agents execution (Cursor 3.23.12 IDE baseline); see COMPATIBILITY.md for verified runtime paths.",
  12. "version": "7.0.0",
  13. "author": {
  14. "name": "Vanyangyang"
  15. }
  16. },
  17. {
  18. "name": "grok-build-supervisor",
  19. "source": "./plugins/grok-build-supervisor",
  20. "description": "Persistent Grok Build Leader and ACP supervision with structured progress, context-efficient cursor polling, long-result artifacts, verified local-proxy initialization, and a visible Windows Terminal TUI.",
  21. "version": "0.4.3",
  22. "author": {
  23. "name": "Vanyangyang"
  24. }
  25. }
  26. ]
  27. }
README.md · README · 365 lines · 3 findings marked
  1. <p align="center">
  2. <a href="https://github.com/Vanyangyang/cursor-bridge/commits/main"><img alt="Long-term maintenance commitment" src="https://img.shields.io/badge/LONG--TERM_MAINTENANCE-COMMITTED-8B5CF6?style=for-the-badge&amp;logo=git&amp;logoColor=white" /></a>
  3. <a href="https://cursor.com/changelog"><img alt="Tracking the latest Cursor releases" src="https://img.shields.io/badge/CURSOR_RELEASES-STAYING_IN_SYNC-00C7B7?style=for-the-badge&amp;logo=cursor&amp;logoColor=white" /></a>
  4. </p>
  5. <p align="center">If Cursor Bridge helps your workflow, star the repo.</p>
  6. <p align="center"><sub><strong>Compatibility:</strong> Cursor Bridge tracks the latest Cursor releases. For older Cursor releases, check <a href="./COMPATIBILITY.md">compatibility and update history</a> and switch to an archived release if one matches; archived releases receive no further updates.</sub></p>
  7. # Cursor Bridge
  8. [简体中文](./README.zh-CN.md) · [Changelog](./CHANGELOG.md) · [Compatibility](./COMPATIBILITY.md) · [AI install](./docs/ai-install.md) · [Releases](https://github.com/Vanyangyang/cursor-bridge/releases) · [Issues](https://github.com/Vanyangyang/cursor-bridge/issues)
  9. [![Release](https://img.shields.io/github/v/release/Vanyangyang/cursor-bridge?style=flat-square&logo=github)](https://github.com/Vanyangyang/cursor-bridge/releases)
  10. [![Stars](https://img.shields.io/github/stars/Vanyangyang/cursor-bridge?style=flat-square&logo=github)](https://github.com/Vanyangyang/cursor-bridge)
  11. [![Node.js](https://img.shields.io/badge/node-%3E%3D18-339933?style=flat-square&logo=nodedotjs&logoColor=white)](https://nodejs.org/)
  12. [![MCP](https://img.shields.io/badge/MCP-server-6D4AFF?style=flat-square)](https://modelcontextprotocol.io/)
  13. [![License](https://img.shields.io/github/license/Vanyangyang/cursor-bridge?style=flat-square)](./LICENSE)
  14. > [!WARNING]
  15. > **Windows primary support:** Cursor Bridge's live-tested runtime and end-to-end acceptance target **Windows**. macOS and Linux have unit and protocol smoke coverage (`macos-basic` CI) for CLI/MCP paths, not full live OS acceptance.
  16. Cursor Bridge connects your coding agent (**Codex**, **Claude Code**, **Grok Build**, **Pi**, or any MCP-capable host) to **Cursor Context Engine (CCE)**—and optionally to bounded `cursor_do` Agent tasks—with verifiable `path:line` evidence.
  17. Starting in **Cursor Bridge 7.0.0**, **CCE CLI (`cli`)** is the **primary maintenance route and fresh-install default**. Existing saved `cce-source.json` selections are preserved intact across upgrades, while upgrades without an existing `cce-source.json` (such as migrating from 6.0.x or never running `/cce` before) adopt `cli` by default; Cursor IDE/Agents over CDP (`ide`) remains available as an explicit fallback source. See [Migrating from 6.x to 7.0.0](#migrate-to-7-0) for exact CLI download and required configuration steps.
  18. > [!IMPORTANT]
  19. > **One-time Windows migration:** If the installed Cursor Bridge version is 5.3.6 or earlier, save your work before the first upgrade to 5.4.0 or any later release, then follow [Update an existing installation](#windows-update-migration) to clean up old-cache processes once. Later updates use the normal flow.
  20. ## What changed in 7.0.0
  21. - **CCE CLI is now the primary route and fresh-install default (`cli`):** No Cursor IDE window needs to be launched for CCE queries. Existing upgrades never overwrite a previously saved `cce-source.json`, while upgrades without one adopt `cli` automatically.
  22. - **High-speed isolated CLI pipeline:**
  23. - **Private MCP isolation (`CURSOR_DATA_DIR` / `mcp-disabled.json`):** Disables external/host MCP startup overhead inside CCE CLI child processes (set `CURSOR_BRIDGE_CCE_CLI_MCP=native` to opt out).
  24. - **Cached official preflight (`CURSOR_BRIDGE_CLI_INSPECT_TTL_MS=300000`):** Deduplicates concurrent CLI metadata inspections and invalidates automatically on launcher/identity/model/source changes or errors.
  25. - **Warm persistent single-root ACP sessions (`cursor-cli-acp.mjs`):** Reuses an authenticated Ask-mode ACP session with strict two-step model/effort/fast/`mode="ask"` read-back checks before sending prompts, cleanly falling back to `--print` on cold starts or capability mismatches before dispatch.
  26. - **Independent concurrency lane (`CURSOR_BRIDGE_CCE_CLI_CONCURRENCY=3`):** Runs up to 3 CLI CCE queries concurrently without blocking IDE FIFO locks.
  27. - **Reliable CLI diagnostics and recoverable initialization:**
  28. - `cursor_cce(action="doctor")` / `/cce doctor` runs non-mutating launcher, auth/models, explicit model selection, local provider preload, and workspace readiness checks.
  29. - `cursor_init` in CLI mode validates launcher + model readiness upfront and returns structured recoverable states (`cli-unavailable`, `cli-auth-required`, `cli-model-required` with `availableModelsSample`, `cli-model-unavailable`, `cli-provider-unavailable`) with actionable `nextStep` instead of leaving opaque failures.
  30. - **Hardened installation & CI verification (`npm run verify`):** Deterministic `scripts/verify-install.mjs`, end-to-end stdio CLI/ACP smoke (`npm run smoke:cli`), bundle freshness verification, and fail-closed `CURSOR_EXE` isolation in tests so offline test runs never spawn your desktop Cursor instance.
  31. <a id="migrate-to-7-0"></a>
  32. ## Migrating from 6.x to 7.0.0 (Cursor CLI download & required setup)
  33. ### Who needs to migrate and how to keep IDE
  34. - **Fresh installs and 6.x upgrades without an existing `cce-source.json`:** Starting in 7.0.0, CCE defaults to `cli` (Cursor Agent CLI). Complete the 3 steps below to install/sign in to Cursor CLI and configure your named model. If you only want desktop Cursor IDE/Agents for now, run `/cce ide` once (or `cursor_cce(action="set", source="ide")`) after upgrading to persist `ide` in `%APPDATA%\cursor-bridge\cce-source.json`.
  35. - **Upgrades with an existing `%APPDATA%\cursor-bridge\cce-source.json`:** Your saved choice (`cli` or `ide`) is preserved across upgrades. If you used early 6.1/6.2 `cli`, run `/cce doctor` once after updating to verify launcher, auth, and model selection.
  36. ### Step 1: Download and install the official Cursor CLI (`cursor-agent`)
  37. Run the official installer in a **new terminal**:
  38. - **Windows PowerShell:**
  39. ```powershell
  40. irm 'https://cursor.com/install?win32=true' | iex
  41. ```
  42. - **macOS / Linux:**
  43. ```bash
  44. curl https://cursor.com/install -fsS | bash
    • Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
    • Line 65 on GitHub
  45. ```
  46. Reopen your terminal (and restart your AI client so `PATH` refreshes), then verify:
  47. ```powershell
  48. cursor-agent --version
  49. ```
  50. > On Windows the installer places the CLI under `%LOCALAPPDATA%\cursor-agent` by default. Cursor Bridge probes `%LOCALAPPDATA%\cursor-agent`, `%USERPROFILE%\.local\bin`, `%APPDATA%\cursor-agent`, and `PATH` automatically, or you can pin an absolute launcher path with `CURSOR_BRIDGE_CLI_PATH`.
  51. ### Step 2: Sign in and inspect available models
  52. ```powershell
  53. cursor-agent login
  54. cursor-agent status
  55. cursor-agent models
  56. ```
  57. - Complete authentication in the prompt/browser. For non-interactive environments, export `CURSOR_API_KEY` (or see [`docs/cce-cli-provider.md`](./docs/cce-cli-provider.md) for the experimental own-key `agent-local` Responses route).
  58. - Confirm `cursor-agent models` prints explicit named model variants (such as `grok-4.6-medium-fast`).
  59. ### Step 3: Required Cursor Bridge configuration (`cursor_model`, doctor, and init)
  60. 1. **Set an explicit named model and effort (`Auto` and `default` are rejected):**
  61. Run `cursor_model(action="set", target="cce", model="grok-4.6-fast", effort="medium")` (or another named model/effort shown by `cursor-agent models`; persisted in `%APPDATA%\cursor-bridge\model-preferences.json`).
  62. 2. **Run `/cce doctor`:**
  63. Execute `/cce doctor` or `cursor_cce(action="doctor")` and confirm `ready: true` / `status: "ready"`.
  64. 3. **Initialize your project workspace:**
  65. Run `cursor_init(path="C:\\absolute\\path\\to\\project")` to persist the workspace binding and start background Ask-mode ACP warmup.
  66. > [!TIP]
  67. > To return CCE to desktop Cursor IDE (`ide`), or when delegating edits through desktop `cursor_do`, run `/cce ide` (`cursor_cce(action="set", source="ide")`). Both sources share your workspace binding and `cursor_model` defaults across restarts.
  68. ## What is CCE?
  69. Cursor Context Engine (CCE) exposes Cursor's project index, semantic retrieval, exact search, reference tracing, and Agent exploration over MCP. Ask a project architecture or ownership question once; Bridge returns compact `path:line` evidence (`CCE_SEARCH_RESULT`), separating verified call chains from similarity or gaps instead of dumping raw search noise into your main Agent context.
  70. CCE and `cursor_do` also accept optional `request_context` (`{"sender":"model","source":"mixed"}`) to record whether the prompt originated from the user or the driving model. Cursor Bridge does not bypass or manage your Cursor subscription; billing, quotas, and BYOK settings stay inside your signed-in Cursor CLI/account or your explicit local `cli_provider`.
  71. > [!NOTE]
  72. > **Historical IDE/Agents acceptance & current pairing:** The last full IDE CDP acceptance remains **Windows 11 + Cursor 3.23.12** (**Grok 4.7/high**, verified across **IDE and Agents Window**, `minimal` and `normal` runtime modes). See [Compatibility and update history](./COMPATIBILITY.md) and the [patch verification scope](./docs/cursor-6.0.8-model-picker-verification.md) for scoped details and evidence boundaries.
  73. ## Quick start
  74. > [!IMPORTANT]
  75. > **Prerequisite for the default `cli` route:** Install Cursor CLI in PowerShell with `irm 'https://cursor.com/install?win32=true' | iex` and run `cursor-agent login` (full guide: [Migrating from 6.x to 7.0.0](#migrate-to-7-0)). Prefer desktop Cursor IDE without CLI? Switch persistently with `/cce ide` after installing the plugin.
  76. ### 1. Install Cursor Bridge in your AI client
  77. Commands are grouped by the AI client you already chat with:
  78. #### Codex (recommended)
  79. ```bash
  80. codex plugin marketplace add Vanyangyang/cursor-bridge --ref main
  81. codex plugin add cursor-bridge@vanyangyang
  82. ```
  83. #### Claude Code
  84. ```bash
  85. claude plugin marketplace add Vanyangyang/cursor-bridge
  86. claude plugin install cursor-bridge@vanyangyang
  87. ```
  88. #### Grok Build
  89. ```bash
  90. grok plugin marketplace add Vanyangyang/cursor-bridge
  91. grok plugin install Vanyangyang/cursor-bridge --trust
  92. grok plugin enable cursor-bridge
  93. ```
  94. (`grok plugin install Vanyangyang/cursor-bridge --trust` also works directly.)
  95. #### Pi
  96. ```bash
  97. pi install npm:pi-cursor-bridge
  98. ```
  99. <a id="other-mcp-hosts"></a>
  100. #### Other MCP-capable AI clients
  101. Give this prompt to the AI client you are already using:
  102. ```text
  103. Read https://github.com/Vanyangyang/cursor-bridge/blob/main/docs/ai-install.md completely. Install Cursor Bridge into this AI client. Follow every step. Report against the completion standard at the end. Use only the dedicated generic npm package named in the playbook. Do not invent a marketplace plugin, do not use a Pi package, and do not publish anything.
  104. ```
  105. The playbook routes Codex, Claude Code, Grok, and Pi back to their first-class marketplace commands, and instructs any other MCP host to install `vanyangyang-cursor-bridge` into `%LOCALAPPDATA%\cursor-bridge\npm`. It tells the AI client where the bundle and skills landed so this AI client can register them, restart, and initialize the workspace. I do not treat that path as a first-class client and have not live-tested it.
  106. ### 2. Restart or reload your AI client
  107. Restart Codex and start a new task, restart Claude Code or run `/reload-plugins`, reload Grok via `/plugins` or a new session, restart Pi, or restart your generic MCP host. Open sessions do not hot-load newly installed MCP tools or skills.
  108. ### 3. Configure explicit CCE model, check CLI readiness, and initialize your workspace
  109. Account CLI requires an explicit named model and reasoning effort (`Auto` and `default` are rejected rather than silently selected). Tell your agent or set it once persistently:
  110. ```text
  111. Set my CCE default model to grok-4.6-fast with medium effort, verify with /cce doctor, and initialize CCE workspace to C:\absolute\path\to\project
  112. ```
  113. - **Pi** automatically binds the directory where Pi was started; pass a new absolute path whenever you want to switch workspaces.
  114. - **If `cursor_init` returns `ready: false` (`cli-unavailable`, `cli-auth-required`, `cli-model-required`, `cli-model-unavailable`, or `cli-provider-unavailable`):** Your workspace binding is still saved (`bindingPersisted: true`), and the response includes `errorCode`, `availableModelsSample` (when available), and the exact `nextStep`. Fix the prerequisite (for example `cursor-agent login` or `cursor_model`) and re-run `cursor_init` or `/cce doctor`. To switch back to Cursor IDE/Agents instead, run `/cce ide`.
  115. ### 4. Ask a real project question
  116. ```text
  117. Who owns this state, and what is the complete path from save loading to runtime use and save write-back?
  118. ```
  119. > [!TIP]
  120. > **Recommended on Windows 11: minimal runtime (when using IDE/Agents or `cursor_do`)**
  121. >
  122. > When routing CCE through `ide` or running `cursor_do`, say “Switch CCE to minimal mode.” Cursor, its project index, Agent DOM, and task queue keep running in the background while top-level Windows windows stay hidden. Cursor 3.23.12 hidden CCE is verified in both UI types; hidden mode verifies the current model and effort (change them in `normal` mode first if the chat uses `Auto`).
  123. >
  124. > **Trade-off:** while minimal mode is active, manually opening Cursor reuses the guarded single-instance process and stays hidden. When you need the Cursor UI again, say “Switch CCE to normal mode.”
  125. ## Compatibility
  126. See [Compatibility and update history](./COMPATIBILITY.md) and [Releases](https://github.com/Vanyangyang/cursor-bridge/releases) for current compatibility pairings, evidence scopes, and archived versions.
  127. First-class live-tested AI clients are **Codex**, **Claude Code**, **Grok Build**, and **Pi**. Generic MCP hosts use [`docs/ai-install.md`](./docs/ai-install.md) (`docs/ai-install.md`) without first-class marketplace updates.
  128. ## Choose and diagnose the CCE source
  129. Fresh installations default to **`cli`** (Cursor Agent CLI). Existing `cce-source.json` preferences are preserved intact on upgrade. Neither source silently falls back to the other on failure.
  130. | Command / Call | Effect |
  131. |---|---|
  132. | `/cce cli` · `cursor_cce(action="set", source="cli")` | Use local Cursor Agent CLI (fresh-install default). |
  133. | `/cce ide` · `cursor_cce(action="set", source="ide")` | Use Cursor IDE/Agents via CDP. |
  134. | `/cce doctor` · `cursor_cce(action="doctor")` | Non-mutating readiness check (launcher, auth/models, `cursor_model`, preload, ACP, workspace). |
  135. | `/cce` · `cursor_cce(action="show")` | Show the saved source, config file path, and optional `cli_provider` summary. |
  136. Hosts may namespace slash commands (for example `/cursor-bridge:cce doctor`), and the packaged `cce` skill supports the same requests in natural language. Both sources share `workspace_path` verification, `cursor_model` defaults, and `CCE_SEARCH_RESULT` formatting:
  137. - **Account CLI (default on `cli`):** Uses signed-in `cursor-agent` / `agent` in Read-Only Ask mode. Single-root workspaces prewarm and reuse a persistent ACP session after strict parameterized config read-back checks; cold starts, capability mismatches, `CURSOR_BRIDGE_CCE_CLI_ACP=off`, and multi-root `.code-workspace` targets use one-shot `--print`. Up to `3` CLI CCE tasks run concurrently (`CURSOR_BRIDGE_CCE_CLI_CONCURRENCY`), independent of IDE UI locks.
  138. - **Own-key CLI (`agent-local`):** Optional configuration via `cursor_cce(action="set", source="cli", cli_provider={kind:"openai-responses", node_path, entrypoint, base_url, api_key_file})`. Uses Cursor's official `agent-local` build with an adjacent preload helper (prechecked before dispatch) and reads your API key directly from the local credential file—never paste secrets into prompts or MCP arguments. Switching `/cce ide` and `/cce cli` preserves `cli_provider` (`cli_provider=null` clears it). See [`docs/cce-cli-provider.md`](./docs/cce-cli-provider.md).
  139. - **Cursor IDE / Agents (`ide`):** Requires Cursor desktop UI (with optional `minimal` mode on Windows 11). Required if you use `cursor_do` delegation (`CURSOR_BRIDGE_DELEGATION=on`).
  140. ## MCP tools
  141. | Tool | What it does |
  142. |---|---|
  143. | `cursor_init` | Persists the workspace binding and verifies CLI/model readiness (`cli`) or CDP connectivity (`ide`). Returns structured recoverable status if CLI setup is incomplete. |
  144. | `cursor_context_engine` | Read-only project understanding from one natural-language `query`; supports `workspace_path` assertion. |
  145. | `cursor_do` | Submits a bounded Cursor Agent task via IDE/Agents (disabled/hidden when `CURSOR_BRIDGE_DELEGATION=off`). Background mode returns a compact receipt; collect full reply via `cursor_status(task_id, detail="result")`. |
  146. | `cursor_model` | Shows, sets, or resets persistent model and effort defaults independently for `cce`, `cursor_do`, or `both`. |
  147. | `cursor_cce` | `show`, `set` (`cli` / `ide`, optional `cli_provider`), or `doctor` (read-only CLI/model/workspace readiness diagnostic). |
  148. | `cursor_status` | Compact by default; reports CLI metadata/concurrency or CDP connection, workspace binding, runtime/model defaults, and tasks (`detail="result"` or `detail="full"`). |
  149. | `cursor_runtime` | Switches IDE presentation between `normal` and Windows 11-tested `minimal` mode. |
  150. | `cursor_task_control` | Targeted `reap`, `cancel`, or explicitly acknowledged `abandon` recovery. |
  151. Pass `workspace_path` on `cursor_context_engine` and `cursor_do` whenever your host knows the target project directory. On pre-send `WORKSPACE_CONFIRMATION_REQUIRED`, `WORKSPACE_INITIALIZATION_REQUIRED`, or `WORKSPACE_MISMATCH`, verify `cursor_status` is idle, run `cursor_init` for the intended path, verify `ready`, and retry once.
  152. > [!WARNING]
  153. > Cursor is an Agent, not an OS filesystem sandbox. CCE enforces Ask mode in ACP and strongly prompts read-only investigation, but consequential anchors and edits should always be verified locally.
  154. ## Reliability and verification
  155. For local validation or after modifying source code or bundles:
  156. ```bash
  157. npm run build # Rebuild all 5 committed ESM bundles (Bridge, preload, supervisor, Grok companion)
  158. npm test # Run isolated test suite (scripts/test.mjs strips host CURSOR_BRIDGE_* env pollution)
  159. npm run smoke:mcp # Real stdio MCP protocol & admission gate smoke test (cache-shaped cwd)
  160. npm run smoke:cli # End-to-end CLI init, doctor, model verification & ACP smoke test (fake CLI harness)
  161. npm run verify:install # Validate bundle manifests, versions, supervisor materialization, and staged npm/Pi bundles
  162. npm run verify # Run the full build + test + smoke:mcp + smoke:cli + verify:install pipeline
  163. ```
  164. <a id="windows-update-migration"></a>
  165. ## Update Cursor Bridge
  166. Cursor Bridge 5.4.0 and later use the normal update commands below. If the currently installed version is 5.3.6 or earlier, complete the [one-time Windows migration](#one-time-windows-migration) first, then return to these commands.
  167. Codex:
  168. ```bash
  169. codex plugin marketplace upgrade vanyangyang
  170. codex plugin add cursor-bridge@vanyangyang
  171. ```
  172. Claude Code:
  173. ```bash
  174. claude plugin marketplace update vanyangyang
  175. claude plugin update cursor-bridge@vanyangyang
  176. ```
  177. Grok Build:
  178. ```bash
  179. grok plugin marketplace update cursor-bridge
  180. grok plugin update cursor-bridge
  181. ```
  182. Pi:
  183. ```bash
  184. pi update npm:pi-cursor-bridge
  185. ```
  186. Other MCP-capable AI clients: ask the current AI to re-read the [AI install playbook](./docs/ai-install.md) and update `vanyangyang-cursor-bridge` to the version pinned in [`docs/ai-install.manifest.json`](./docs/ai-install.manifest.json), then restart this AI client.
  187. After updating, start a new Codex task, restart Claude Code or run `/reload-plugins`, reload Grok through `/plugins` or start a new Grok session, restart Pi, or restart the current AI client.
  188. > [!NOTE]
  189. > **Upgrading from 6.x to 7.0.0:** If no `%APPDATA%\cursor-bridge\cce-source.json` was saved previously, 7.0.0 activates `cli` automatically. Follow [Migrating from 6.x to 7.0.0](#migrate-to-7-0) to install/log in to Cursor CLI, set `cursor_model`, and run `/cce doctor`—or run `/cce ide` once to stay on desktop IDE.
  190. If Codex reports `marketplace 'vanyangyang' is not configured as a Git marketplace`, run `codex plugin marketplace add Vanyangyang/cursor-bridge --ref main` once, then retry the Codex commands above.
  191. <a id="one-time-windows-migration"></a>
  192. ### One-time Windows migration from Cursor Bridge 5.3.6 or earlier
  193. > [!WARNING]
  194. > **Only the first Windows upgrade from Cursor Bridge 5.3.6 or earlier needs this cleanup.** Old plugin processes can keep a versioned cache directory open and block replacement. Do not change ACLs or delete the plugin cache.
  195. > [!TIP]
  196. > **Recommended: copy this to your local coding Agent:** “I saved my work. First check the installed Cursor Bridge version. Only if it is 5.3.6 or earlier, inspect processes whose command lines load `cursor-lifecycle-supervisor.mjs` or `dist/cursor-bridge.mjs` from the AI client's versioned plugin cache. Treat every instance under `%LOCALAPPDATA%\cursor-bridge\lifecycle\runtime\` as the new persistent runtime and do not stop it. After verifying the exact old-cache path and ownership, stop only those old-cache processes without asking again; do not mass-stop Node or PowerShell, change ACLs, delete caches, or touch unrelated processes. The current task's old Cursor Bridge MCP may disconnect when its old adapter stops; that is expected. Then update Cursor Bridge to the latest version using the current AI client's normal marketplace command, reload the AI client, and report the installed version, marketplace source, and any old-cache process that remains.”
  197. After this one-time migration, later updates do not need special process cleanup.
  198. <details>
  199. <summary><strong>How CCE searches and returns evidence</strong></summary>
  200. `query` carries one focused natural-language project question; optional `workspace_path` asserts the target project before admission.
  201. ```text
  202. CCE_SEARCH_RESULT
  203. intent: <normalized intent>
  204. coverage: <focused|extended> | <why this depth was sufficient>
  205. evidence:
  206. - path/to/file.ts:42-67 | symbolOrAnchor | verified relevance or relationship | reference
  207. gaps: none
  208. confidence: high
  209. ```
  210. The installed `cce-routing` skill routes unfamiliar architectural or cross-module questions to CCE while keeping known-file reads, builds, tests, logs, and Git commands on native tools.
  211. </details>
  212. <details>
  213. <summary><strong>Workspace, Cursor UI, and IDE lifecycle behavior (`ide` / `cursor_do`)</strong></summary>
  214. - Multiple MCP adapters share one user-level lifecycle supervisor materialized into `%LOCALAPPDATA%\cursor-bridge\lifecycle\runtime\`, keeping CDP connection management outside versioned plugin caches.
  215. - In `ide` mode or `cursor_do`, Bridge prefers an open Agents Window for the matching repository and falls back to workbench without creating work in `Home`.
  216. - If Cursor is already running without `--remote-debugging-port`, `cursor_init` preserves the workspace binding and returns `close_cursor_and_retry` instead of force-killing Cursor.
  217. - Full session/recovery contracts live in [`docs/CURSOR_SESSION_CONTRACT.md`](./docs/CURSOR_SESSION_CONTRACT.md).
  218. </details>
  219. <details>
  220. <summary><strong>Environment variables and source overrides</strong></summary>
  221. | Variable | Default | Description |
  222. |---|---|---|
  223. | `CURSOR_BRIDGE_CLI_PATH` | auto-discovered | Absolute path to `cursor-agent` / `agent` launcher. |
  224. | `CURSOR_BRIDGE_CLI_INSPECT_TTL_MS` | `300000` | Official CLI preflight cache TTL in ms (`0` disables caching). |
  225. | `CURSOR_BRIDGE_CCE_CLI_MCP` | unset (`isolated`) | Set to `native` to disable private `CURSOR_DATA_DIR` MCP isolation. |
  226. | `CURSOR_BRIDGE_CCE_CLI_ACP` | `on` | Set to `off` to disable persistent ACP sessions and use one-shot `--print`. |
  227. | `CURSOR_BRIDGE_CCE_CLI_ACP_IDLE_MS` | `900000` | Idle recycle timeout in ms for warm ACP processes. |
  228. | `CURSOR_BRIDGE_CCE_CLI_ACP_MAX_AGE_MS` | `3600000` | Maximum lifetime in ms before rotating a warm ACP process. |
  229. | `CURSOR_BRIDGE_CCE_CLI_ACP_FAIL_TTL_MS` | `300000` | Capability-failure cache TTL in ms per CLI identity (`0` disables). |
  230. | `CURSOR_BRIDGE_CCE_CLI_CONCURRENCY` | `3` | Concurrent execution slots on the CLI CCE lane (`1`–`8`). |
  231. | `CURSOR_BRIDGE_DELEGATION` | `on` | Set to `off` to disable and hide `cursor_do`. |
  232. | `CURSOR_BRIDGE_CDP_PORT` | `9223` | Cursor IDE remote-debugging port (`ide` / `cursor_do`). |
  233. | `CURSOR_BRIDGE_TIMEOUT` | `300000` | Search timeout in milliseconds. |
  234. | `CURSOR_BRIDGE_NO_AUTOLAUNCH` | unset | Set to `1` to skip IDE startup prewarming. |
  235. | `CURSOR_BRIDGE_RUNTIME_MODE` | `normal` | Initial IDE window mode (`normal` or `minimal`). |
  236. | `CURSOR_EXE` | auto-detected | Override Cursor IDE executable path (fails closed if set to a missing path). |
  237. </details>
  238. <details>
  239. <summary><strong>Companion plugin: Grok Build Supervisor (maintenance-only)</strong></summary>
  240. This repository also still contains the standalone **Grok Build Supervisor** plugin (`0.4.3`) in maintenance-only mode. Existing packages (`grok-build-supervisor`, `pi-grok-build-supervisor`, `vanyangyang-grok-build-supervisor`) remain intact so existing setups keep working, while active development prioritizes Cursor Bridge and CCE CLI.
  241. See the companion documentation if you already use it: [English](./plugins/grok-build-supervisor/README.md) · [简体中文](./plugins/grok-build-supervisor/README.zh-CN.md).
  242. </details>
  243. ## Friends
  244. - [LINUX DO](https://linux.do)
  245. ## License
  246. [MIT](./LICENSE)
  247. ## Star History
  248. [![Cursor Bridge Star History](https://raw.githubusercontent.com/Vanyangyang/cursor-bridge/main/assets/star-history.svg?v=78d133dcb77a)](https://github.com/Vanyangyang/cursor-bridge)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.