Cursor CLI

Cursor CLI brings Cursor's coding agent to a terminal for interactive development and non-interactive automation. It can inspect a repository, explain code, propose and apply changes, and execute project commands. It is a command-line package, distinct from the Cursor desktop IDE and from a remotely running Cloud Agent.

Terminal workflows

Use the CLI in the intended project directory, choose a task and review its work. Interactive sessions let you discuss a problem and approve commands. Ask mode supports read-only exploration, Plan mode develops an approach, and Agent mode provides the tools for implementation. Saved sessions can be resumed. Print mode supports scripts and CI, with output formats suited to automation.

Rules, skills, hooks and MCP servers can customize the workflow and connect tools. Project runtimes, compilers, Git credentials and test dependencies remain part of your environment. Installing the agent does not install every dependency needed to build a repository.

Installation and platform support

The catalog recorded 2026.10.01-e373342 Apple Silicon archive is 176,796,992 bytes before extraction and installed storage. Separate Mac ARM64 and x64 archives are published. This cask exposes cursor-agent on the executable path; current official documentation also uses the agent command for its direct-install route. Follow the command supplied by your installation route rather than assuming all aliases are present.

The current cask declares no additional package dependency, conflict or explicit macOS minimum. That does not establish support for every older system. Official installation documentation covers macOS, Linux, WSL and Windows with separate platform installers. The CLI can be used alongside a preferred editor and does not require opening the Cursor IDE for every session.

Permissions and local execution

The agent can read, change and delete files and execute shell commands with the available local user permissions. Review commands and diffs, keep version control or backups, and use trusted projects and integrations. Non-interactive runs deserve particular care because the chosen automation flags determine how work proceeds without a person at the terminal.

Official sandbox controls let you enable or disable command isolation and configure network access; the settings persist across sessions. Sandboxing and permission approvals are distinct controls, and neither should be described as permission to bypass an operating system or service restriction. An elevated command requires the appropriate local authorization. Plugins, hooks and MCP servers can have their own access and runtime requirements.

Account, cloud services and data

Authenticate with a Cursor account or the supported API-key route for automation. Model and usage availability depend on the account, plan and organization policy. Running tools locally does not make AI inference offline: prompts, code context and tool results can be sent to the service. Review Cursor's applicable privacy settings and provider terms for sensitive repositories.

A Cloud Agent handoff transfers work to a separate remote environment and depends on its service entitlement, repository access and configuration. It is not equivalent to leaving a local CLI process running, and it may have different credentials and execution resources. Installing the CLI alone does not provide unlimited Cloud Agent usage.

License and cost

Cursor is proprietary Anysphere software under the applicable terms. The current public pricing page lists the free Hobby plan with limited Agent requests, Pro from US$20 per month and Teams Standard from US$40 per user per month. Higher individual and team tiers, extra usage and enterprise terms differ. Check the account's current model availability, included usage and spending controls before starting long or parallel jobs. The CLI uses Cursor account entitlements rather than including a separate free model or unlimited subscription with the download.

Official sources: Cursor CLI, CLI overview, Installation, CLI changelog, Pricing, CLI introduction.