provider-cursor
/provider-cursor
Śledzi i utrzymuje kontrakt z zewnętrznym Cursor Agent CLI przy nowych wydaniach i zmianach flag, trybów, sesji oraz punktu wejścia ACP; źródłem mechanicznym jest src/upstream-contracts.ts.
- Autor
- verivus-oss ↗
- Repozytorium
- llm-cli-gateway ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 09.09.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 3
Brak sygnałów. Repozytorium zmienione 09.09.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Śledzi i utrzymuje kontrakt z zewnętrznym Cursor Agent CLI przy nowych wydaniach i zmianach flag, trybów, sesji oraz punktu wejścia ACP; źródłem mechanicznym jest src/upstream-contracts.ts.
Oryginalny opis (EN)
Track and maintain the upstream Cursor Agent CLI contract. Use when Cursor ships a CLI release, when a `cursor-agent` flag, execution mode, session command, ACP entrypoint, or subcommand changes, or when an upstream scan flags drift. Process guidance only: `src/upstream-contracts.ts` is the mechanical source of truth.
Jak działa
- Identity
- Gateway use
- Scan for upstream change
- Update procedure
- Cursor-specific notes
Podgląd SKILL.md
---
name: provider-cursor
description: "Track and maintain the upstream Cursor Agent CLI contract. Use when Cursor ships a CLI release, when a `cursor-agent` flag, execution mode, session command, ACP entrypoint, or subcommand changes, or when an upstream scan flags drift. Process guidance only: `src/upstream-contracts.ts` is the mechanical source of truth."
metadata:
author: verivus-oss
version: "1.0"
---
# Provider: Cursor Agent CLI
Keep the gateway's Cursor (`cursor-agent`) integration aligned with the upstream
CLI. This skill does not define argv or environment behaviour. The single
mechanical source of truth is `UPSTREAM_CLI_CONTRACTS.cursor` in
`src/upstream-contracts.ts`, enforced by `validateUpstreamCliArgs` and
`validateUpstreamCliEnv`. Do not re-encode flags, execution modes, ACP rules,
or session rules here or in TOML.
## Identity
| Field | Value |
| ------------------- | ----------------------------------------------------------------------------- |
| CliType | `cursor` |
| Executable | `cursor-agent` |
| Distribution | Cursor Agent vendor distribution |
| CLI docs | https://cursor.com/cli |
| ACP docs | https://cursor.com/docs/cli/acp |
| Parameter reference | https://cursor.com/docs/cli/reference/parameters |
| Watch categories | `flags`, `subcommands`, `session-resume`, `execution-modes`, `acp-entrypoint` |
These values mirror `UPSTREAM_CLI_CONTRACTS.cursor.upstreamMetadata` and
`docs/upstream/provider-sources.dag.toml` (`[providers.cursor]`). The TypeScript
metadata is authoritative; the TOML is scanner input only.
## Gateway use
1. Discover the live gateway surface before relying on Cursor-specific controls:
```
provider_tool_capabilities({cli:"cursor"})
```
For a cached read-only resource, use `provider-tools://cursor`.
2. Use `cursor_request` for normal work and `cursor_request_async` for
long-running work. Sync calls may auto-defer; poll `llm_job_status` and fetch
with `llm_job_result` when that happens.
3. Omit `model` unless the caller explicitly requests one. Use only controls
reported by `provider_tool_capabilities`, especially execution mode, sandbox,
workspace, and session controls. Cursor must use
`approvalStrategy:"legacy"`: it rejects `mcp_managed` before launch because
ambient MCP configuration cannot be isolated, and `approvalPolicy` has no
effect.
4. Keep provider-owned MCP configuration separate from gateway metadata. Do not
assume every Cursor CLI control is safe to expose through a request.
5. Cursor accepts flat `prompt` only, not `promptParts`. `workingDir` selects
the child process cwd on `transport:"cli"`, as it does for every other
provider. It is CLI-only: `transport:"acp"` rejects it in
`rejectUnsupportedCursorAcpParams` alongside `addDir`, because the ACP route
resolves its own scope and would otherwise discard it silently. Its
`workspace`
field is separate and selects a local target directory, registered alias, or
provider-native `.code-workspace` file. A directory/alias establishes child
cwd; a workspace file remains a native argument and is not misused as
`spawn.cwd`. Because both inputs can name a cwd, `resolveCursorWorkingDir`
rejects an absolute workspace path that disagrees with `workingDir` instead
of ranking them; identical values are admitted. Verify the
target before reviewing concurrent repositories. An unregistered relative
value remains a provider-native saved-workspace name and is passed through
verbatim, never resolved against the gateway process cwd. Use an absolute
path when selecting an unregistered local directory as child cwd.
6. Use a real resumable Cursor chat only when the response reports it as
resumable. Gateway bookkeeping IDs are not automatically valid Cursor chat
IDs. Continuation remains provider-native under legacy. A cwd-scoped
`resumeLatest` needs a stable selected target.
7. Native ACP is capability-gated. It rejects `approvalStrategy:"mcp_managed"`
and any `approvalPolicy`, as does the Cursor CLI gateway path. Probe
`cursor-agent acp --help` when validating the installed entrypoint.
8. An unscoped CLI child uses a fresh neutral temporary cwd, not the gateway
repository. Cursor's argv-bound prompt rejects oversized UTF-8 input as
non-retryable `input_too_large`; the gateway never truncates it. All other
caller-controlled argv values are admitted in their final encoded form
before spawn. Embedded NUL bytes return non-retryable `invalid_input`
without exposing the rejected value.
### Full-access review handoff
For a user-authorized exhaustive review that needs full provider permissions and
native MCP access, do not infer the launch controls from this maintenance guide.
Follow `multi-llm-review`'s full-access protocol, inspect the current request
schema and live capability response, and use a fresh target-checkout
`node dist/index.js --transport=stdio` gateway rather than a global process.
Reapply the grant on every new job, preserve native MCP configuration without a
pretend gateway allowlist, send the corrective-program report and exact
diff/file identity, set no caller caps, and honor a user-required 90-second
progress cadence. The reviewer must independently inspect code, docs, tests,
and commands before it can approve.
## Scan for upstream change
```bash
npm run upstream:scan -- --provider cursor
npm run upstream:scan -- --live --provider cursor --fail-on-critical
npm run upstream:scan -- --provider cursor --probe-installed --fail-on-critical
npm run upstream:scan -- --live --provider cursor --probe-installed --write-snapshot --write-report
```
A failed source fetch is advisory unless `--fail-on-critical` is passed. Use the
installed help probe as the primary signal for rapidly changing command surface.
## Update procedure
1. Edit `UPSTREAM_CLI_CONTRACTS.cursor` in `src/upstream-contracts.ts`: flags,
arities, enums, execution modes, session rules, ACP probe commands, and
catalogued subcommands belong there.
2. Add conformance fixtures that prove every new accept and reject behavior.
3. If a source URL or watch category changes, update TypeScript metadata first,
then mirror it in `docs/upstream/provider-sources.dag.toml`.
4. Verify with `npm run build`, `npm run upstream:contracts`, and targeted
provider tests before the full suite.
## Cursor-specific notes
- Tested against `cursor-agent 2026.09.02-c22c1a3`.
- Root commands include authentication, MCP, worker, update, chat/session, and
rule-management surfaces. Catalog them with an explicit risk and exposure tier
before exposing any of them through gateway admin or request tools.
- Keep destructive or interactive commands, including worker startup and any
session mutation, catalog-only unless an approval-gated product surface is
deliberately added.
Pliki w paczce (2)
- SKILL.md 7 KB
- agents/openai.yaml 1 KB
Wersje
W bazie nie ma innych skilli o nazwie provider-cursor.
Migawka bazy z 13.11.2026 · wersja paczki 5fda4abfce34 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100provider-devin
Śledzi i utrzymuje kontrakt z zewnętrznym Devin CLI przy nowych wydaniach i zmianach flag, trybów uprawnień, punktu wejścia ACP oraz podpoleceń; źródłem mechanicznym jest src/upstream-contracts.ts. - 100provider-claude
Śledzi i utrzymuje kontrakt z zewnętrznym Claude Code CLI przy nowych wydaniach i zmianach flag, wyjścia, uprawnień oraz podpoleceń; źródłem mechanicznym jest src/upstream-contracts.ts. - 95upgrade-claude-adapter
Synchronizuje fork @anthropic-ai/claude-agent-acp z nowszym wydaniem upstream: podbija SDK, przenosi poprawki i obsługę nowych wiadomości, zachowuje rozbieżności forka, weryfikuje i aktualizuje UPSTREAM.md. - 85cursor-agent
Uruchamia lokalne CLI cursor-agent albo zmienia jego instalację, logowanie i podłączone narzędzia, gdy użytkownik o to poprosi. - 100acp-runner
Pokazuje, jak sterować kiro-cli acp z Node.js: start sesji, strumieniowy prompt, anulowanie i obsługa uprawnień. - 100cursor-delegate
Deleguje zadania kodowania do Cursor Agent CLI (cursor-agent) tylko na wyraźną prośbę użytkownika, a przegląd i wdrożenie zostają po stronie orkiestratora.