From 9d7eda9f069ca7ad05205a332c756d1b1272f7a5 Mon Sep 17 00:00:00 2001 From: chata <1399055+chata@users.noreply.github.com> Date: Sat, 26 Sep 2026 01:58:00 +0900 Subject: [PATCH 1/3] docs: announce that the project is no longer maintained --- README.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/README.md b/README.md index 2bf5a4b..bc1b8c5 100644 --- a/README.md +++ b/README.md @@ -4,6 +4,23 @@ [![CI](https://github.com/coo-quack/openclaw-cursor-cli/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/coo-quack/openclaw-cursor-cli/actions/workflows/ci.yml) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) +> [!WARNING] +> **This project is no longer maintained, and the repository is archived.** +> +> - OpenClaw 2026.9 stopped shipping the type definitions for +> `openclaw/plugin-sdk/cli-backend`, the subpath this plugin is built on, +> while still exporting its JavaScript. That reads as the subpath no longer +> being a public API, so following it would mean hand-writing types for an +> interface that can change without notice. +> - The 2026.9 CLI backend also requires `CURSOR_API_KEY` authentication +> before it spawns `cursor-agent`, which breaks this plugin's integration +> tests and changes how the plugin authenticates. +> - The maintainer no longer uses OpenClaw. +> +> The last release, 0.3.1, was tested against OpenClaw 2026.7.1. It does not +> work with OpenClaw 2026.9 or later, even though its `peerDependencies` +> declare `>=2026.6.0`. + **Use your Cursor subscription as an OpenClaw inference backend.** Grok, Claude, and GPT models through the `cursor-agent` CLI you already have — no extra API key, no separate bill. From 03038c29f97e42f8225beaccd5ed646f8fbabc2c Mon Sep 17 00:00:00 2001 From: chata <1399055+chata@users.noreply.github.com> Date: Sat, 26 Sep 2026 02:00:37 +0900 Subject: [PATCH 2/3] ci: add a workflow that deprecates the npm package --- .github/workflows/deprecate.yml | 65 +++++++++++++++++++++++++++++++++ 1 file changed, 65 insertions(+) create mode 100644 .github/workflows/deprecate.yml diff --git a/.github/workflows/deprecate.yml b/.github/workflows/deprecate.yml new file mode 100644 index 0000000..abff9f8 --- /dev/null +++ b/.github/workflows/deprecate.yml @@ -0,0 +1,65 @@ +name: Deprecate the package + +# The project is retired (see the README), so this marks every published +# version of the package as deprecated. It exists because the registry write +# needs either an interactive 2FA code or the granular token in Actions +# secrets, the same one `release.yml` publishes with. Adapted from +# sensitive-canary's deprecate.yml, but for the whole package rather than one +# version. + +on: + workflow_dispatch: + inputs: + message: + description: "What a user sees next to the package in `npm install` output" + required: true + type: string + +permissions: {} + +concurrency: + group: npm-deprecate + cancel-in-progress: false + +jobs: + deprecate: + runs-on: ubuntu-latest + timeout-minutes: 10 + permissions: {} + + steps: + - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0 + with: + node-version: "24.21.0" + registry-url: "https://registry.npmjs.org" + + # Read through `env:` rather than spliced in as `${{ }}`, so a message + # carrying a quote or a semicolon is not read as shell. + - name: Deprecate every version + env: + NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} + MESSAGE: ${{ inputs.message }} + run: | + set -uo pipefail + if [ -z "${MESSAGE//[[:space:]]/}" ]; then + # npm reads an empty message as "undeprecate". + echo "::error::the message is empty — that would undeprecate instead." + exit 1 + fi + npm deprecate "@coo-quack/openclaw-cursor-cli" "$MESSAGE" + + # npm accepting the write is not the same as the registry serving it. + - name: the registry serves the deprecation + run: | + set -uo pipefail + for attempt in 1 2 3 4 5; do + got=$(npm view "@coo-quack/openclaw-cursor-cli@latest" deprecated 2>/dev/null || true) + if [ -n "$got" ]; then + echo "deprecated: $got" + exit 0 + fi + echo "not visible yet (attempt $attempt), waiting" + sleep 10 + done + echo "::error::the package still reads as not deprecated." + exit 1 From 247bf345399dd93885cb64b748654e27889c14a8 Mon Sep 17 00:00:00 2001 From: chata <1399055+chata@users.noreply.github.com> Date: Sat, 26 Sep 2026 02:06:09 +0900 Subject: [PATCH 3/3] ci: drop the deprecate workflow; the package was deprecated from the npm website --- .github/workflows/deprecate.yml | 65 --------------------------------- 1 file changed, 65 deletions(-) delete mode 100644 .github/workflows/deprecate.yml diff --git a/.github/workflows/deprecate.yml b/.github/workflows/deprecate.yml deleted file mode 100644 index abff9f8..0000000 --- a/.github/workflows/deprecate.yml +++ /dev/null @@ -1,65 +0,0 @@ -name: Deprecate the package - -# The project is retired (see the README), so this marks every published -# version of the package as deprecated. It exists because the registry write -# needs either an interactive 2FA code or the granular token in Actions -# secrets, the same one `release.yml` publishes with. Adapted from -# sensitive-canary's deprecate.yml, but for the whole package rather than one -# version. - -on: - workflow_dispatch: - inputs: - message: - description: "What a user sees next to the package in `npm install` output" - required: true - type: string - -permissions: {} - -concurrency: - group: npm-deprecate - cancel-in-progress: false - -jobs: - deprecate: - runs-on: ubuntu-latest - timeout-minutes: 10 - permissions: {} - - steps: - - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0 - with: - node-version: "24.21.0" - registry-url: "https://registry.npmjs.org" - - # Read through `env:` rather than spliced in as `${{ }}`, so a message - # carrying a quote or a semicolon is not read as shell. - - name: Deprecate every version - env: - NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} - MESSAGE: ${{ inputs.message }} - run: | - set -uo pipefail - if [ -z "${MESSAGE//[[:space:]]/}" ]; then - # npm reads an empty message as "undeprecate". - echo "::error::the message is empty — that would undeprecate instead." - exit 1 - fi - npm deprecate "@coo-quack/openclaw-cursor-cli" "$MESSAGE" - - # npm accepting the write is not the same as the registry serving it. - - name: the registry serves the deprecation - run: | - set -uo pipefail - for attempt in 1 2 3 4 5; do - got=$(npm view "@coo-quack/openclaw-cursor-cli@latest" deprecated 2>/dev/null || true) - if [ -n "$got" ]; then - echo "deprecated: $got" - exit 0 - fi - echo "not visible yet (attempt $attempt), waiting" - sleep 10 - done - echo "::error::the package still reads as not deprecated." - exit 1