Cursor CLI
Cursor CLI is a supported coding agent in Band that uses the
@nothumanwork/cursor-agents-sdk to interact with Cursor's AI backend.
It provides real-time streaming, tool use visibility, and session resume, but does
not support cost tracking or session listing.
Prerequisites
- Install the Cursor IDE from cursor.com.
- Ensure the Cursor CLI agent SDK is available. Band uses the
@nothumanwork/cursor-agents-sdkpackage internally. - Have an active Cursor subscription with API access enabled.
Configuring Band to Use Cursor
To switch Band to use Cursor CLI as the coding agent:
- Open the Band dashboard and go to Settings.
- Under Coding Agent, select
cursor-clifrom the agent type dropdown. - Save your settings. All new tasks will now use the Cursor CLI adapter.
How It Works
The Cursor CLI adapter creates a CursorAgent instance and calls its
stream() method with the task prompt. Band processes the streaming
events and maps Cursor's tool call format to Band's unified event system. Cursor
uses a different tool naming convention internally — Band translates these
automatically:
| Cursor Internal Name | Band Display Name |
|---|---|
| readToolCall | Read |
| writeToolCall | Write |
| shellToolCall | Bash |
| editToolCall | Edit |
| globToolCall | Glob |
| grepToolCall | Grep |
Differences from Claude Code
There are several differences to be aware of when using Cursor CLI instead of Claude Code:
- No cost tracking. Cursor does not report per-session cost data. The cost field in task results will always be zero.
- No session listing. You cannot browse previous Cursor sessions from the Band dashboard. The session history view is unavailable.
- No hook-based status detection. Cursor does not have a hook system like Claude Code. Band only detects Cursor activity through tasks it submits directly.
- No user input prompts. The Cursor adapter does not support intercepting tool approval requests. All tool calls are auto-approved.
- Model selection. Cursor uses its own model routing. The
modeloption defaults to"auto", which lets Cursor choose the best model for each request.
Configuration Options
The Cursor CLI adapter accepts these configuration options:
- model — The model to use for Cursor requests. Defaults to
"auto". Cursor supports its own set of model identifiers. - maxTurns — Maximum number of agentic turns per session (default: 50 when run through Band).
Session Resume
Cursor CLI does support session resume via chat IDs. When a task completes and a follow-up task is queued, Band passes the previous session's chat ID so the agent can continue in the same conversation context. However, you cannot manually browse or select previous sessions from the dashboard as you can with Claude Code.