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-13-cursor-read-access-needs-a-team-boundary-and-control-over-user-extensions

Read Access needs a team boundary and control over user extensions. The documented IDE setting requires 3.23 and adds a Workspace choice that asks before outside reads. System remains the default, including access to ~/.ssh for sandboxed commands. Repository settings replace a user’s readBoundary and additionalReadPaths. Team Workspace policy outranks those choices, but member and repository allowlist extensions remain possible unless the admin disables them. The CLI server gate’s false fallback does not establish its rollout to any particular account.

Channel: tagged-release (IDE setting requires 3.23; CLI plumbing in e373342); docs-only (admin policy semantics). Half: both. Date: 2026-10-01 (documented IDE 3.23 requirement); 2026-10-13 posture read, corroborated October 14.

Operator consequence: Use team Workspace policy and turn off Read Control User Extensions for an administrator-owned read boundary. Otherwise inspect repository sandbox.json and the effective allowlist. Confirm CLI behavior with a harmless outside-workspace read before depending on the gate. Expect more prompts and manage the allowed paths deliberately; Run Everything bypasses this control.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-cursor-read-access-needs-a-team-boundary-and-control-over-user-extensions

Profile citations

  • cursor / claim / read-access-and-user-extensions

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact