Cursor CLI
On macOS, Linux, or WSL:
curl https://cursor.com/install -fsS | bashOn Windows with PowerShell:
irm 'https://cursor.com/install?win32=true' | iexAs with any install script, read it before piping it to a shell if your environment calls for that.
Run agent for an interactive session, or open one with an initial prompt:
agent
agent "refactor the auth module to use JWT tokens"In a session you describe goals, review proposed changes, and approve commands, the same loop as the editor.
Press Shift+Tab for plan mode when the task needs a decision first, or /ask for read-only exploration when you want no changes at all.
Modes#
The CLI supports the same modes as the editor.
| Mode | Purpose | How to switch |
|---|---|---|
| Agent | Full tool access for complex tasks | Default |
| Plan | Design the approach first, with clarifying questions | Shift+Tab, /plan, --plan, --mode=plan |
| Ask | Read-only exploration, no changes | /ask, --mode=ask |
Ask mode is worth knowing about. When you want to understand code without any risk of it being modified, read-only is a stronger guarantee than asking nicely.
Execution controls#
Sandbox controls
Configure command execution with /sandbox or --sandbox <mode>, where mode is enabled or disabled. An interactive menu controls sandboxing and network access, and settings persist across sessions.
Sudo password prompts
When a command needs elevated privileges, Cursor shows a masked password prompt. The password goes to sudo through a secure IPC channel and is never exposed to the model.
Cloud handoff
Prefix a message with & to push the conversation to a cloud agent that keeps running after you close the terminal:
& refactor the auth module and add comprehensive testsPick the task up later on web or mobile at cursor.com/agents.
Related#
- Sessions — resume earlier conversations
- Automation — non-interactive runs for scripts and CI
One install command, and the same agent you use in the editor runs where you already work.