feat(integrations): support Cursor Agent CLI as non-interactive LLM backend by cerencamkiran · Pull Request #1149 · Tracer-Cloud/opensre

cerencamkiran · 2026-04-30T15:19:08Z

Summary

Adds support for Cursor Agent CLI as a subprocess-backed LLM provider using the existing LLMCLIAdapter interface.

This integration enables OpenSRE to use Cursor as a non-interactive, one-shot CLI backend, fully compatible with the Codex-style execution model.

Key Features

Non-interactive execution via agent --print
Supports stdin and argv prompt input
Requires explicit --trust for headless execution
Supports optional model override via CURSOR_MODEL
Authentication is handled exclusively via CLI (agent login / agent status)
No environment-based authentication is used
Compatible with subprocess.run (no TTY, no blocking)

Spike Findings (Cursor CLI behavior)

Binary name is agent (not cursor-agent)
Headless execution is supported via --print
Workspace trust must be explicitly enabled (--trust)
Free-tier accounts require --model auto
CLI exits cleanly with stdout → compatible with LLMCLIAdapter contract

Implementation

Added CursorAdapter in app/integrations/llm_cli/cursor.py
Implemented:
- detect() (CLI-based status probing only)
- build() (non-interactive invocation)
- parse() (stdout extraction)
- explain_failure() (error classification)
Registered provider in:
- app/integrations/llm_cli/registry.py
- app/config.py
Extended subprocess env forwarding:
- _SAFE_SUBPROCESS_ENV_PREFIXES += ("CURSOR_",)
Added onboarding support in:
- app/cli/wizard/config.py

detect() behavior

Returns:

True → authenticated
False → not authenticated
None → auth state unclear

Never raises exceptions and follows the CLIProbe contract.

Tests

Added full test coverage:

detect (CLI status only)
build
parse
explain_failure
registry integration
subprocess env forwarding

Results:

python -m pytest tests/integrations/llm_cli/
→ 29 passed

Static checks:

ruff check → passed
mypy → passed

Quick Start

agent login
opensre onboard
# Select: Cursor Agent CLI

opensre investigate

End-to-End Validation

Successfully verified full pipeline:

opensre onboard → Cursor Agent CLI selected
opensre investigate → completed successfully

Sample output:

Most likely: a database connectivity failure affecting `payments_etl`

Confirms Cursor CLI works end-to-end in OpenSRE investigation loop.

Demo (Headless Execution)

agent --print --trust --output-format text --model auto "Say hello"
# → Hello!

Cross-OS Notes

Tested on:

Windows (PowerShell)
WSL Ubuntu (primary runtime environment)

Notes:

Cursor CLI installed in WSL must be used from WSL for detection
Windows native environment may not detect agent binary
macOS not tested locally, but expected to work via official installer

Acceptance Criteria Coverage

Non-interactive CLI contract

Uses a single one-shot invocation (agent --print)
No REPL, no TTY, no blocking input
Fully compatible with subprocess.run

detect() behavior (3-state)

True → authenticated via CLI (agent status)
False → not authenticated
None → unclear / fallback
Never raises, follows CLIProbe contract

CLI-only authentication

No environment-based authentication
Authentication determined solely via CLI (agent status)

build() contract

Produces non-interactive invocation
Includes required flags: --print, --trust, --output-format text
Optional model override via CURSOR_MODEL

Subprocess env forwarding

Only forwards CURSOR_* variables
Verified via test coverage

Registry integration

Registered via CLI_PROVIDER_REGISTRY
Selectable via LLM_PROVIDER=cursor

End-to-end validation

opensre onboard
opensre investigate
Full test suite passing (29 tests)

Conclusion

Cursor CLI satisfies all requirements for a non-interactive LLM backend and integrates cleanly into the OpenSRE pipeline.

greptile-apps · 2026-04-30T15:22:21Z

Greptile Summary

This PR adds CursorAdapter as a new non-interactive CLI backend, following the same LLMCLIAdapter contract as the existing Codex adapter. The implementation is clean and well-tested, with correct wiring across config, registry, env forwarding, and the onboarding wizard.

Confidence Score: 5/5

Safe to merge; all remaining findings are P2 style/UX issues that do not affect correctness.

The integration follows the established adapter pattern, env forwarding is minimal and correct, and test coverage is thorough. The two P2 findings (misleading error message when stdout is empty on exit-0, and lack of Cursor-specific validation in the agent binary probe) are quality improvements but do not block functionality.

app/integrations/llm_cli/cursor.py — parse() error message and agent binary identity validation.

Important Files Changed

Filename	Overview
app/integrations/llm_cli/cursor.py	New CursorAdapter implementing the LLMCLIAdapter protocol; two minor issues: parse() delegates to explain_failure() with returncode=0 producing a confusing message, and the generic `agent` binary name may match unrelated system binaries without Cursor-specific validation.
app/integrations/llm_cli/runner.py	Added `"CURSOR_"` to `_SAFE_SUBPROCESS_ENV_PREFIXES` so that CURSOR_API_KEY, CURSOR_MODEL, and CURSOR_BIN are forwarded to the subprocess; clean, minimal, correct change.
app/integrations/llm_cli/registry.py	Registers `cursor` provider with `_cursor_factory` and `CURSOR_MODEL` env key; mirrors the codex pattern exactly.
app/config.py	Adds `"cursor"` to LLMProvider literal, `_normalize_provider` validator, and the no-API-key exemption list; stale inline comment omits cursor from its description.
app/cli/wizard/config.py	Adds CURSOR_MODELS tuple and ProviderOption for Cursor in SUPPORTED_PROVIDERS; follows the same pattern as codex.
tests/integrations/llm_cli/test_cursor_adapter.py	Comprehensive test coverage for detect(), build(), parse(), explain_failure(), registry integration, and subprocess env forwarding; all paths exercised including edge cases.

Sequence Diagram

sequenceDiagram
    participant CLI as opensre CLI
    participant Runner as CLIBackedLLMClient
    participant Adapter as CursorAdapter
    participant Proc as agent subprocess

    CLI->>Runner: invoke(prompt)
    Runner->>Adapter: detect()
    Adapter->>Proc: agent --version
    Proc-->>Adapter: version stdout
    Adapter->>Proc: agent status (if no CURSOR_API_KEY)
    Proc-->>Adapter: Logged in as ...
    Adapter-->>Runner: CLIProbe(installed=True, logged_in=True)
    Runner->>Adapter: build(prompt, model, workspace)
    Adapter-->>Runner: CLIInvocation(argv=[agent,--print,--trust,...], stdin=prompt)
    Runner->>Proc: subprocess.run(argv, env=filtered_env)
    Proc-->>Runner: stdout, returncode=0
    Runner->>Adapter: parse(stdout, stderr, returncode)
    Adapter-->>Runner: stripped answer
    Runner-->>CLI: LLMResponse(content=answer)

_{Reviews (1): Last reviewed commit: "feat: add Cursor CLI adapter (non-intera..." | Re-trigger Greptile}

greptile-apps · 2026-04-30T15:22:25Z

+    def parse(self, *, stdout: str, stderr: str, returncode: int) -> str:
+        result = (stdout or "").strip()
+        if not result:
+            raise RuntimeError(
+                self.explain_failure(stdout=stdout, stderr=stderr, returncode=returncode)
+                + " (empty output)"
+            )
+        return result


Misleading error message when stdout is empty on success

parse() delegates to explain_failure() even when returncode=0, so an empty-output success case produces the message "cursor agent exited with code 0. (empty output)". The phrase "exited with code 0" signals success to the reader while the surrounding context is an error, which is confusing. Consider a dedicated message when the exit code is 0 to avoid the contradiction.

greptile-apps · 2026-04-30T15:22:26Z

+    def _resolve_binary(self) -> str | None:
+        return resolve_cli_binary(
+            explicit_env_key="CURSOR_BIN",
+            binary_names=_candidate_binary_names("agent"),
+            fallback_paths=_default_cli_fallback_paths("agent"),
+        )


Generic binary name agent may resolve to an unrelated binary

_candidate_binary_names("agent") will match any executable called agent on the PATH (e.g. chef-agent, puppet-agent, or other common devops tools installed as agent). The detect() method only confirms the binary exits 0 on --version — it doesn't verify the output contains any Cursor-specific string. A false positive here sends the wrong binary to build() and fails at invocation time with a confusing error. Consider asserting that "cursor" appears in the --version output before treating the binary as the Cursor Agent CLI.

greptile-apps · 2026-04-30T15:22:27Z

+        if self.provider in ("ollama", "bedrock", "codex", "cursor"):
            return self  # ollama: local; bedrock: IAM; codex: `codex login` (CLI)


Inline comment doesn't mention cursor

The comment still only describes ollama, bedrock, and codex even though cursor was added to the same exemption. This will mislead future readers.

Suggested change

if self.provider in ("ollama", "bedrock", "codex", "cursor"):

return self # ollama: local; bedrock: IAM; codex: `codex login` (CLI)

if self.provider in ("ollama", "bedrock", "codex", "cursor"):

return self # ollama: local; bedrock: IAM; codex/cursor: CLI login

cerencamkiran · 2026-04-30T15:23:08Z

cerencamkiran · 2026-04-30T15:38:54Z

All P2 feedback addressed:

improved parse() handling for empty stdout on success
replaced string-based binary validation with version parsing (more robust)
updated config comment for clarity

All tests passing, no behavior changes.

muddlebee · 2026-05-01T09:36:50Z

+                detail="Binary found but does not appear to be Cursor Agent CLI.",
+            )
+
+        if os.environ.get("CURSOR_API_KEY"):


why this? the auth, models and everything should be handled from CLI side only and not something which should be configured here..

check in codex how its done https://github.com/Tracer-Cloud/opensre/blob/main/app/integrations/llm_cli/AGENTS.md#codex-env-quick-reference-instance-of-the-convention-above

and refer the above AGENTS.md the specs should strictly follow it.

I've removed env-based auth handling and aligned the adapter with the CLI-only contract.
Updated tests accordingly to ensure authentication is determined solely via the CLI (agent status).

muddlebee · 2026-05-01T09:37:35Z

some points from acceptance criteria still missing.

cerencamkiran · 2026-05-01T10:02:56Z

I've updated the PR description with a detailed acceptance criteria mapping and aligned the implementation with the CLI-only contract.

The remaining Windows CI failures look unrelated to the Cursor adapter. Both failures are in interactive_shell prompt session tests and fail with prompt_toolkit.output.win32.NoConsoleScreenBufferError.

The Cursor-specific tests are passing locally, and the full suite mostly passes except these Windows console-buffer failures.

Let me know if anything else should be clarified @muddlebee 🙏

Devesh36 · 2026-05-04T06:12:40Z

Hey @cerencamkiran resolve the conflicts over here

muddlebee · 2026-05-04T06:58:31Z

this is the conflict I guess

muddlebee · 2026-05-04T06:59:29Z

+            )
+
+        status_text = (status_proc.stdout + status_proc.stderr).strip()
+        if status_proc.returncode == 0 and "Logged in as" in status_text:


Not-logged-in detail still mentions CURSOR_API_KEY while the adapter documents CLI-only auth elsewhere. Drop the env-var hint here for consistency.

muddlebee · 2026-05-04T06:59:30Z

+            explicit_env_key="CURSOR_BIN",
+            binary_names=_candidate_binary_names("agent"),
+            fallback_paths=_default_cli_fallback_paths("agent"),
+        )


Version-regex gating reduces wrong-binary risk but any agent that prints a semver can still pass. Consider requiring a Cursor-specific substring in --version output (case-insensitive "cursor") before treating the binary as installed.

muddlebee · 2026-05-04T06:59:39Z

    "bedrock",
    "minimax",
    "codex",
+    "cursor",


Unrelated to this line: the branch removes the repository root .gitignore entirely in the latest commit. Restore .gitignore before merge.

muddlebee · 2026-05-04T06:59:45Z

        adapter_factory=_codex_adapter_factory,
    ),
+    ProviderOption(
+        value="cursor",


Wizard wires the provider; issue #1109 still expects .env.example entries for CURSOR_BIN and CURSOR_MODEL (mirroring CODEX). Add those commented lines in .env.example.

muddlebee · 2026-05-04T07:17:40Z

+            logged_in = None
+            detail = status_text or "Could not determine Cursor Agent auth status."
+
+        return CLIProbe(


Classify subscription auth from agent status first (current block). If logged_in is False or None and CURSOR_API_KEY is non-empty, return logged_in True with detail that notes API-key headless auth; only surface agent login when neither path applies. Extend tests for not-logged-in status plus key, unclear status plus key, and logged-in status ignoring the key.

muddlebee · 2026-05-04T07:19:31Z

@cerencamkiran this is P1 issue

cerencamkiran · 2026-05-04T11:03:49Z

Thanks for the feedback @muddlebee I’ve addressed the comments and aligned the auth handling with the current tests and CLI contract.

All tests are passing locally and in CI, and I’ve resolved the remaining conflicts.

muddlebee · 2026-05-04T12:18:07Z

@cerencamkiran why remove? .gitignore ? https://github.com/Tracer-Cloud/opensre/blob/main/.gitignore

--
I fixed that for you in the PR :)
0278ff3

PR tip had an empty .gitignore; restore Tracer-Cloud main contents.

muddlebee · 2026-05-04T12:25:28Z

Looks good overall I will just do some additional set of reviews :) thank you for your patience and efforts 🪄

cerencamkiran · 2026-05-04T12:28:59Z

@cerencamkiran why remove? .gitignore ? https://github.com/Tracer-Cloud/opensre/blob/main/.gitignore

-- I fixed that for you in the PR :) 0278ff3

That was accidental while resolving a merge conflict. Thanks a lot for fixing it. 🤗

cerencamkiran · 2026-05-04T12:30:37Z

Looks good overall I will just do some additional set of reviews :) thank you for your patience and efforts 🪄

Happy to address any further feedback @muddlebee thanks again for the review 🙂

github-actions · 2026-05-05T13:26:44Z

🎻 "The diff was clean, the tests did pass, the reviewer wept." That poem was about @cerencamkiran's PR. 🥹

👋 Join us on Discord - OpenSRE : hang out, contribute, or hunt for features and issues. Everyone's welcome.

muddlebee · 2026-05-05T13:26:49Z

@cerencamkiran thank you for the PR. I added some improvements in later PRs. :) feel free to check

Main moved while the previous merge was in flight: PR Tracer-Cloud#1149 added Cursor Agent CLI support touching the same prefix tuple, env-var docs, and provider-allowlist as this branch. Resolutions (all "combine both" merges): - subprocess_env.py: prefix tuple now includes both CURSOR_ and KIMI_ - app/config.py: provider early-return now includes both cursor and kimi - .env.example: keep both Cursor and Kimi env-var blocks

cerencamkiran added 2 commits April 30, 2026 18:17

feat: add Cursor CLI adapter (non-interactive)

f406bba

style: format Cursor CLI adapter

1c57ca1

greptile-apps Bot reviewed Apr 30, 2026

View reviewed changes

fix: address Cursor CLI review feedback

a849d42

muddlebee added the ci:windows label Apr 30, 2026

cerencamkiran added 2 commits May 1, 2026 12:31

fix: resolve CLI provider merge conflicts

59abf27

chore: ignore venv

e038278

muddlebee reviewed May 1, 2026

View reviewed changes

fix: align cursor adapter with CLI-only auth contract

71b5a20

muddlebee added the llm-cli Subprocess LLM CLI integration (LLMCLIAdapter / registry) label May 3, 2026

Delete .gitignore

a840080

muddlebee reviewed May 4, 2026

View reviewed changes

cerencamkiran and others added 5 commits May 4, 2026 12:10

fix: restore .gitignore

ef235c0

fix: address cursor auth fallback review feedback

e377ab8

Merge remote-tracking branch 'upstream/main' into feat/cursor-cli-1109

1f37240

Merge branch 'main' into feat/cursor-cli-1109

71d0743

style: format cursor adapter

c41110d

fix(git): restore .gitignore from main

0278ff3

PR tip had an empty .gitignore; restore Tracer-Cloud main contents.

muddlebee added 2 commits May 5, 2026 18:29

Merge branch 'main' into feat/cursor-cli-1109

c4adeb9

fix(llm_cli): tighten Cursor auth probe per AGENTS.md

727dbe8

muddlebee removed the ci:windows label May 5, 2026

fix(cli): map CLI auth failures to OpenSREError on investigate

925142c

muddlebee mentioned this pull request May 5, 2026

enhancement: extend CLI auth error handling beyond investigate #1309

Closed

3 tasks

muddlebee merged commit 69c6604 into Tracer-Cloud:main May 5, 2026
10 checks passed

yashksaini-coder mentioned this pull request May 5, 2026

feat(integrations): support Kimi Code CLI as non-interactive LLM backend #1139

Merged

2 tasks

		if self.provider in ("ollama", "bedrock", "codex", "cursor"):
		return self # ollama: local; bedrock: IAM; codex: `codex login` (CLI)

Conversation

cerencamkiran commented Apr 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Key Features

Spike Findings (Cursor CLI behavior)

Implementation

detect() behavior

Tests

Quick Start

End-to-End Validation

Demo (Headless Execution)

Cross-OS Notes

Acceptance Criteria Coverage

Non-interactive CLI contract

detect() behavior (3-state)

CLI-only authentication

build() contract

Subprocess env forwarding

Registry integration

End-to-end validation

Conclusion

Uh oh!

greptile-apps Bot commented Apr 30, 2026

Greptile Summary

Confidence Score: 5/5

Important Files Changed

Sequence Diagram

Uh oh!

greptile-apps Bot Apr 30, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot Apr 30, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot Apr 30, 2026

Choose a reason for hiding this comment

Uh oh!

cerencamkiran commented Apr 30, 2026

Uh oh!

cerencamkiran commented Apr 30, 2026

Uh oh!

muddlebee May 1, 2026

Choose a reason for hiding this comment

Uh oh!

cerencamkiran May 1, 2026

Choose a reason for hiding this comment

Uh oh!

muddlebee commented May 1, 2026

Uh oh!

cerencamkiran commented May 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Devesh36 commented May 4, 2026

Uh oh!

muddlebee commented May 4, 2026

Uh oh!

muddlebee May 4, 2026

Choose a reason for hiding this comment

Uh oh!

muddlebee May 4, 2026

Choose a reason for hiding this comment

Uh oh!

muddlebee May 4, 2026

Choose a reason for hiding this comment

Uh oh!

muddlebee May 4, 2026

Choose a reason for hiding this comment

Uh oh!

muddlebee May 4, 2026

Choose a reason for hiding this comment

Uh oh!

muddlebee commented May 4, 2026

Uh oh!

cerencamkiran commented May 4, 2026

Uh oh!

muddlebee commented May 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

muddlebee commented May 4, 2026

cerencamkiran commented Apr 30, 2026 •

edited

Loading

cerencamkiran commented May 1, 2026 •

edited

Loading

muddlebee commented May 4, 2026 •

edited

Loading