Bitter Frontier What coding agents just made possible, where the bottleneck moved, and what deserves attention.

Evidence record / cursor

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-24-cursor-current-state-cursor-s-hosted-agent-sessions-are-built-to-be-refused-review-approvals-whil

Current state: Cursor’s hosted agent sessions are built to be refused review approvals, while Grok Bot can approve through the Origin MCP server without a confirmation prompt. The public docs describe a cloud agent as acting with the user’s access. The shipped client shows a narrower design: the cloud-agent VM receives a session scoped to specific repositories and scopes, the CLI blocks merges sent with anything broader (merging through the scoped session itself remains possible, subject to rulesets), and the server is expected to refuse that session’s approvals. Grok Bot, a separate computer-use product, can approve through MCP as the member it serves, with no confirmation flag on the approve tool. Who may approve therefore depends on which Cursor product holds the session, not on the word “agent”.

Channel: docs-only (MCP and agents docs), with client evidence from Origin CLI stable artifacts 2026.10.13-14-06-43-ea1dfe5 and 2026.10.23-18-47-36-f52be1e. Half: both. Date: posture read 2026-10-24 (MCP text already present in the 2026-10-07 capture; CLI guards present in both the 13 and 23 October stable bundles).

Operator consequence: Do not assume agents cannot approve on Origin. Whether an approval made via Grok Bot counts toward required approvals or code-owner review is undocumented; test it on a scratch repository before letting members who are required reviewers use Grok Bot on Origin, or require group approvals from people who do not. Point read-only agents at https://api.origin.cursor.com/mcp/readonly. Reviewers can no longer rely on a [bot] suffix to spot app-written commits; check the actor type instead. Server enforcement of the scoped session was not tested here.

Receipt

Finding metadata

Confidence
medium

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-cursor-current-state-cursor-s-hosted-agent-sessions-are-built-to-be-refused-review-approvals-whil

Profile citations

  • cursor / claim / origin-session-review-differences

Source links

Primary links, including exact changelog lines when available.

  1. Cursor
    official docs2026-10-24-cursor-current-state-cursor-s-hosted-agent-sessions-are-built-to-be-refused-review-approvals-whilweb.archive.org/web/20261024093422/https://cursor.com/docs/origin/agentsofficial docs2026-10-24-cursor-current-state-cursor-s-hosted-agent-sessions-are-built-to-be-refused-review-approvals-whilweb.archive.org/web/20261007190558/https://cursor.com/docs/api/origin/mcpofficial docs2026-10-24-cursor-current-state-cursor-s-hosted-agent-sessions-are-built-to-be-refused-review-approvals-whilweb.archive.org/web/20261024094355/https://cursor.com/docs/api/origin/mcpofficial docs2026-10-24-cursor-current-state-cursor-s-hosted-agent-sessions-are-built-to-be-refused-review-approvals-whilweb.archive.org/web/20261024094434id_/https://cursor.com/docs/api/origin/mcp/tools.mdofficial docs2026-10-24-cursor-current-state-cursor-s-hosted-agent-sessions-are-built-to-be-refused-review-approvals-whilweb.archive.org/web/20261024093206/https://cursor.com/docs/release-notes/cloud-agents#oct-12-2026official docs2026-10-24-cursor-current-state-cursor-s-hosted-agent-sessions-are-built-to-be-refused-review-approvals-whildownloads.cursor.com/co/2026.10.23-18-47-36-f52be1e/darwin-arm64/co.tar.gz

Versioned source: run artifact