Repository navigation
Description
Summary
Orca does not recognize a running Cursor Agent CLI session when it is started manually from a normal PowerShell terminal on Windows. The Cursor TUI is active and responsive inside an Orca-managed worktree, but the worktree sidebar shows no Cursor icon or agent status and Orca reports an empty agent list.
This is a concrete failure in Orca's existing Cursor CLI detection, distinct from the broader Cursor support request in #7766.
Environment
- OS: Windows
- Orca: 1.4.135
- Cursor Agent: 2026.07.09-a3815c0
- Project/group:
Ai-economics - Worktree:
Deck - Shell: PowerShell
Steps to reproduce
-
Open an Orca-managed worktree.
-
Create or use its normal terminal tab, which starts as vanilla PowerShell.
-
Launch Cursor Agent with either:
cursor-agentor its installed alias:
agent
-
Submit a prompt and confirm that Cursor Agent responds.
-
Inspect the worktree row in the Orca sidebar or run
orca worktree ps --json.
Actual behavior
- Cursor Agent is visibly running and responding in the terminal.
- The terminal title remains
Windows PowerShell. - The worktree has one live terminal.
- Orca reports
agents: []. - No Cursor logo or agent status appears beneath the worktree in the sidebar.
Observed process tree:
powershell.exe
+-- node.exe ...\cursor-agent\versions\2026.07.09-a3815c0\index.js
+-- node.exe ...\index.js worker-server
Expected behavior
Starting a supported agent CLI manually in a terminal should be enough for Orca to identify it:
Ai-economics
+-- Deck
+-- Cursor Agent working
Users should not have to launch the agent through a special Orca picker for basic detection. The normal UX is to open a worktree terminal, run an agent command, and have Orca recognize the resulting session automatically.
Root cause
The installed Orca configuration declares Cursor as:
cursor: {
detectCmd: 'cursor-agent',
launchCmd: 'cursor-agent',
expectedProcess: 'cursor-agent',
promptInjectionMode: 'argv',
preflightTrust: 'cursor'
}On Windows, however, the current Cursor launchers are wrapper scripts. They ultimately execute a versioned Node runtime:
%LOCALAPPDATA%\cursor-agent\versions\<version>\node.exe
%LOCALAPPDATA%\cursor-agent\versions\<version>\index.js
Testing Orca's installed process recognizer directly gives:
"cursor-agent" -> cursor
"agent" -> no match
"node.exe ...\cursor-agent\...\index.js" -> no match
"node.exe ...\index.js worker-server" -> no match
Orca already special-cases Node script entrypoints for some other providers, but the equivalent map does not include Cursor. The fallback paths also fail in this session:
- Process recognition: sees
node.exe ...\index.js, not a process namedcursor-agent. - OSC/title recognition: terminal title remains
Windows PowerShell, notCursor Agent. - Hook recognition: Orca's Cursor hooks are installed, but this session produced no Orca status record.
All three detection paths therefore miss a live Cursor session.
Proposed solution
1. Recognize the Cursor Node wrapper
Identify Cursor when the foreground command line matches the installed package path and entrypoint, for example:
.../cursor-agent/versions/<version>/node.exe .../cursor-agent/versions/<version>/index.js
Do not rely only on the executable basename.
2. Recognize both supported launcher names
Treat both cursor-agent and its installed agent alias as Cursor launch commands. Alias handling should use command/path context and must not classify unrelated Windows processes such as Battle.net's Agent.exe as Cursor.
3. Make hooks a reliable fallback
Verify that manually launched Cursor CLI sessions receive the Orca pane environment and emit lifecycle/status hooks. Existing user hooks should be composed safely rather than overwritten.
4. Add Windows regression coverage
Cover at least:
cursor-agentwrapper launchagentalias launch- versioned
node.exe ...\index.js - nested
index.js worker-server - unrelated
Agent.exeprocesses - manual launch from a vanilla PowerShell terminal
Acceptance criteria
- Running
cursor-agentmanually in an Orca PowerShell terminal creates a Cursor agent record and sidebar icon. - Running the installed
agentalias produces the same result. - Cursor status transitions are reflected in the sidebar.
- Detection survives Orca restart or terminal reconnection.
- Unrelated Node and
Agent.exeprocesses are not misclassified. - Launching through Orca's agent picker continues to work.
- Existing user Cursor hooks are preserved.
Supporting documentation
Cursor documents cursor-agent as the CLI command:
Related broader feature request: #7766
Activity
OrcaWin commentedon Jul 17, 2026
Agent reproduction package (Windows orchestration 2026-07-16)
Host context: Windows 11 / Orca 1.4.143.0 / repo path used:
docs/bug-reproductions/Labels applied: see issue labels (
has_reproorcannot_repro).Security: Do not run user-uploaded binaries from issue attachments. Recreate fixtures from the steps/scripts below.
Issue 8258 — Cursor Agent CLI not detected in sidebar on Windows
Status:
needs_setupHost: Windows 11 10.0.26200, Orca 1.4.143.0
Label: (none — not live-repro conclusive; missing
cursor-agent)Issue: #8258
Summary
Reporter: running
cursor-agent/agentin an Orca PowerShell terminal does not create a Cursor agent row. Root-cause writeup in the issue matches current mainline config.Environment
cursor-agenton PATH%LOCALAPPDATA%\cursor-agentagenton PATHC:\Users\neil\.grok\bin\agent.exe(Grok), not CursorConfig / code (matches issue)
orca agent hooks status→cursor: installed(~\.cursor\hooks.json) even without the CLI.agentornode.exe ...\cursor-agent\...\index.jsto Cursor (see issue body +agent-detection.test.tstitle rules).Evidence
docs/bug-reproductions/evidence/8258-agent-alias-is-grok.txt—agent→ Grokdocs/bug-reproductions/evidence/hooks-status.json— cursor hooks installed, CLI absentdocs/bug-reproductions/issues/8258.jsoncursor-agentbinaryExpected vs actual
cursor-agent/ Cursor Node wrapper shows sidebar Cursor statusRepro when Cursor CLI is installed
Conclusion
needs_setup— no Cursor Agent CLI on this machine. Source still implements the weak recognition paths described in the issue (namecursor-agentonly; no Node package map for Cursor).How another agent should use this
%LOCALAPPDATA%\Programs\orca).--json, screenshots, logs) under a local folder; optionally comment results back here.cannot_repro/ needs_setup, satisfy the listed prerequisites first, then re-attempt and flip labels: removecannot_repro, addhas_reprowhen conclusive.AmethystLiang commentedon Aug 1, 2026
Linked duplicate closed
Closing #8259 as a Discord-bot mirror of this issue. The Discord post restates the same Cursor Agent sidebar-detection failure on Windows and links here; no independent reproduction beyond what's already in this report.
Snuux commentedon Aug 2, 2026
I have same issue
NiklasDor commentedon Aug 2, 2026
Same issue when orchestrating cursor agents there is no indicator of it running
AmethystLiang commentedon Aug 14, 2026
Related newer report: #14434 (Windows, Orca 1.4.180). Sidebar shows
opencodestatus but notcursor cliwhen both tabs are in the same workspace. Unclear whether Cursor is undetected entirely (this issue) or a dual-agent status-display gap. Leaving #14434 open until that's distinguished.nwparker commentedon Aug 31, 2026
Resolved by merged PR #8266 (commit 4c7bbed), which detects the Cursor Agent Node wrapper on Windows. Closing as completed.