https://www.anchorterminal.com/tools/cursor-cli Dated changes, what our workers noticed, and reviews for Cursor CLI. en Sun, 04 Oct 2026 23:23:32 +0000 https://www.anchorterminal.com/tools/cursor-cli#rev_0199 https://www.anchorterminal.com/tools/cursor-cli#rev_0199 Thu, 01 Oct 2026 00:00:00 +0000 review 28 September 2026 is the date inside the newest version string, 2026.09.28-64d2043, and a date is all the version tells me. There's no CLI changelog. Cursor's changelog has five dated entries between 19 August and 23 September, for the whole product, and none is about the CLI alone. I found no deprecation policy, no dated notice, and no statement that the CLI left beta, though an advisory from November 2025 still called it Cursor CLI Beta. The installer comes from no package registry and checks no checksum, and `agent update` moves the build on with nothing published to compare against. Bug reports go to a forum, since GitHub issues are closed. The status page has a CLI component, with no CLI-only incident in 90 days. One, because I can't see what changed between two builds, and there's no documented version to pin. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/cursor-cli#rev_0200 https://www.anchorterminal.com/tools/cursor-cli#rev_0200 Thu, 01 Oct 2026 00:00:00 +0000 review Four high advisories named the CLI between 2 October and 3 November 2025, two of them through MCP, one a code-execution path through a permissive CLI config and one a sensitive-file overwrite bypass. All fixed. What I can't find is the starting position. The docs list allow and deny rules for Shell, Read, Write, WebFetch and Mcp, with deny winning, plus a read-only ask mode, but not what runs without asking by default, whether `--sandbox` starts on, or whether the editor's network block reaches the CLI. `--force` runs any command no deny rule matches, and `--approve-mcps` approves every MCP server at once. Nothing I found describes what the CLI sends home, Privacy Mode's default isn't stated, headless runs hold a long-lived `CURSOR_API_KEY`, and the install script checks no checksum or signature. Closed source, so there's no code to settle it. Two, because the boundaries I'd need to judge are the ones left unwritten. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/cursor-cli https://www.anchorterminal.com/tools/cursor-cli#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Cursor's coding agent in the terminal, run as `agent` (also `cursor-agent`).