Untitled conversation
- User
[Bug]: Cursor CLI agent stays in loading state after task completes
Operating system
macOS
Orca version
Unknown (please add from Orca > About Orca if available)
Details
Summary
When running a Cursor CLI agent session in Orca, the UI continues to show a loading/running state after the agent has finished its task — as if work is still in progress.
Steps to reproduce
- Start a Cursor CLI agent session in Orca.
- Give the agent a task and wait for it to complete (agent finishes and produces final output).
- Observe the session UI state.
Expected behavior
Once the Cursor CLI agent finishes, the session should transition to an idle/completed state — loading indicators should stop and the UI should reflect that no work is in progress.
Actual behavior
The session remains in a loading/running state after the task is done, giving the impression the agent is still working.
Environment
- macOS: darwin 25.4.0
- Agent: Cursor CLI
Additional notes
- Reproduces when the agent has clearly finished (final response delivered) but Orca does not update the activity/loading indicator accordingly.
- May cause confusion about whether it is safe to send a follow-up prompt or close the session.
Evaluation contract
When a synthetic-title agent reports a non-working state, reconcile the terminal title with that agent's synthetic title profile. For Cursor,
donereplaces spinner/working titles, the bareCursor Agenttitle, and stale permission titles withCursor ready;waitingorblockedusesCursor - action required. Preserve descriptive completed titles that are not classified as working or permission, and do not rewrite agents without a synthetic-title profile. Apply this resolver before storing agent-status snapshot titles.Interface
Type: Function Name: resolveAgentStatusTerminalTitle Path: src/renderer/src/lib/agent-status-terminal-title.ts Input: payload: Pick<ParsedAgentStatusPayload, 'agentType' | 'state'>, currentTitle: string | undefined Output: string | undefined Description: Reconciles hook-reported state with synthetic terminal-title profiles. For Cursor, done maps stale spinner, working, bare native, or permission titles to "Cursor ready"; waiting/blocked maps to "Cursor - action required". Descriptive completed titles and agents without a synthetic profile are preserved. The IPC status integration must call this resolver before storing the title.
- Assistant
Investigating how agent status and terminal titles are handled so we can fix the stuck loading state after Cursor CLI completes.
- Assistant
Implementing
resolveAgentStatusTerminalTitleand integrating it into the IPC status path so completed Cursor sessions don't keep a stale working title. - Assistant
Fixed the stuck loading state for Cursor CLI agent sessions.
Root cause
When a Cursor hook reported
done, the renderer stored agent status with the pane’s current terminal title — often still⠋ Cursor Agentfrom the synthetic spinner. That stale working title could outlive the hook completion and keep loading indicators active even though the agent had finished.Fix
Added
resolveAgentStatusTerminalTitleinsrc/renderer/src/lib/agent-status-terminal-title.tsto reconcile hook state with synthetic-title profiles before persisting status:done: replaces spinner/working titles, bareCursor Agent, and stale permission titles withCursor ready; keeps descriptive completed titleswaiting/blocked: maps toCursor - action requiredworking: leaves the title unchanged- Agents without a synthetic profile (e.g. Codex): unchanged
The IPC integration in
useIpcEvents.tsnow calls this resolver beforesetAgentStatus, so snapshots and UI rows get the reconciled title immediately instead of waiting for the synthesized OSC frame to land inruntimePaneTitlesByTabId.The same contract applies to other synthetic-title agents (OpenCode, Droid, Hermes).
Tests
- Unit tests in
agent-status-terminal-title.test.ts(6 passing) - Integration test in
useIpcEvents.test.tsfor cursordone+ spinner title →Cursor ready
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- fable-5Compare side by side →
- fable-5Compare side by side →