Answer: Team-owned repos offer Internal (visible to anyone on your team with access to the codebase) and Private (visible only to members granted access directly or through codebase permissions) visibility, while personal repos are always Private and visible only to you by default, with sharing done via Settings then Collaborators. Status: Confirmed Entry: tool/cursor/permissions-and-security/origin-repository-visibility Revision: 1 Digest: sha256:c39a7d91158ebddb (changes whenever the content changes) Timeline: Created: 2026-11-13T03:11:54Z Last changed: 2026-11-13T03:11:54Z Last verified: 2026-11-20T12:40:20Z Next check: 2026-11-21T12:40:20Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Team visibility option 1 | Internal | [1] | 2026-11-20 Team visibility option 2 | Private | [1] | 2026-11-20 Personal repo visibility | Private | [1] | 2026-11-20 Personal repo visibility chooser | does not show a visibility chooser | [1] | 2026-11-20 Sharing personal repos | Settings | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/origin/create-repository.md". https://cursor.com/docs/origin/create-repository.md Role: primary. Accessed: 2026-11-20T12:40:20Z Quote: "**Internal**, visible to anyone on your team with access to the codebase" (Supports: Team visibility option 1) Quote: "**Private**, visible only to members granted access directly or through codebase permissions" (Supports: Team visibility option 2) Quote: "Repos created under a personal account are always **Private** and visible only to you by default." (Supports: Personal repo visibility) Quote: "The **New Repo** dialog does not show a visibility chooser for personal repos." (Supports: Personal repo visibility chooser) Quote: "To share a personal repo, open the repo, go to **Settings**, then **Collaborators**, and invite the people you want to give access." (Supports: Sharing personal repos) Snapshot SHA-256: 3f5dfc7bd9a1359c8f6083ddd70be27e5f8b7b292e8dc21d48abcdc2ecd0de77 (captured 2026-11-17T12:51:10Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-17T12:51:10Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:40:20Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:40:20Z Last attempt: 2026-11-20T12:40:20Z Notes and limitations: Extracted automatically from a single official source (section "Name, visibility, and sharing"). Related: https://latestn.com/tool/cursor/permissions-and-security/permissions-vs-sandbox-json What is the difference between permissions.json and sandbox.json in Cursor? https://latestn.com/tool/cursor/permissions-and-security/prevent-eval-side-effects How do I keep side effects out of Cursor eval sessions? https://latestn.com/tool/cursor/permissions-and-security/protect-public-webhooks How do I protect public webhook endpoints in Cursor's Agent SDK? https://latestn.com/tool/cursor/permissions-and-security/origin-grants-api-scopes What scopes are available for the Cursor Origin Grants API? https://latestn.com/tool/cursor/permissions-and-security/origin-mcp-readonly How do I make the Cursor Origin MCP server read-only? https://latestn.com/tool/cursor/permissions-and-security/origin-migration-api-authentication How do I authenticate requests to the Cursor Origin Migration API? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:11:54Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/permissions-and-security/origin-repository-visibility/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cursor/permissions-and-security/origin-repository-visibility POST: https://latestn.com/dispute/tool/cursor/permissions-and-security/origin-repository-visibility with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/permissions-and-security/origin-repository-visibility?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What visibility options exist for Cursor Origin repositories and how are personal repos handled? Revision 1, last verified 2026-11-20T12:40:20Z. https://latestn.com/tool/cursor/permissions-and-security/origin-repository-visibility (accessed 2026-11-21T10:03:56Z). @misc{LatestN_tool_cursor_permissions_and_security_origin_repository_visibility_r1, title = {What visibility options exist for Cursor Origin repositories and how are personal repos handled?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/permissions-and-security/origin-repository-visibility}}, note = {Revision 1; digest sha256:c39a7d91158ebddb; last verified 2026-11-20T12:40:20Z; accessed 2026-11-21T10:03:56Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cursor/permissions-and-security/origin-repository-visibility