Cursor Origin
Cursor Origin Codebase Settings, Apps and Automations Explained
Codebase settings apply across your team's Origin repos at cursor.com/codebase, separate from any one repository's Settings tab. They hold team Permissions, Slack Notifications and Apps, where you install apps such as Vercel, Depot and Buildkite or build private apps for the Origin API. Automations and cloud agents reach Origin repos the way they reach GitHub repos.

On this page
What are Origin codebase settings, and how do they differ from repo settings?
Origin has two settings surfaces. Codebase settings apply across your team's Origin repos and open from the codebase home, while each repo has its own Settings tab for its sync status, access and rules. Codebase settings decide who can use Origin, which Slack notifications you get and which apps the team has installed.
The split follows the namespace. A codebase is the namespace your repositories live under, the {owner} in each repo URL, so membership and app installs apply to all of it. Controls over one repo's branches, protections and collaborators stay with that repo. Apps show up at both levels: you install and manage them in codebase settings, and a repo's Apps tab shows which ones it has.
- Codebase settings (codebase home)
- Permissions: who can access repos under the claimed name and who can create repos. Notifications: Slack DMs, reminders and channel subscriptions. Apps: install marketplace apps or build private ones.
- Repository Settings tab
- Tabs depend on the owner. A team repo has General, Access, Rules and Protections and Apps; a personal repo has General, Collaborators, Apps, Rules and Protections and Advanced. On a mirror, General shows sync status and Detach from GitHub.
From cursor.com/docs/origin/settings, which covers both levels. The Access, Collaborators and Rules and Protections screens are being redesigned.
Notifications cover pull request activity across the codebase's repos. You choose which events send you a Slack DM from @Cursor, schedule reminder digests of open review requests, and subscribe Slack channels to a repo's pull requests. Cursor won't post a private or internal repo's activity to a channel shared with another organization through Slack Connect.
If you can't find a setting, ask whether it could sensibly differ between two repos on the same team. Branch rules can, so they live on the repo. Whether Origin is enabled can't, so it lives on the codebase.
This is covered hands-on in Cursor Compile 2026 — 1 short Unit, free to read.
Rather do it than read about it? Run 11 interactive Cursor walkthroughs in a simulated editor. Free, no account needed.
Who can use Origin for your codebase?
The plan comes first. Free and Plus don't include Origin, which needs Premium or a higher tier, Teams, Enterprise, or one of the legacy paid plans (Start, Pro, Pro+ and Ultra). Within a team, the Permissions settings decide who can access repos under your claimed codebase name and how Origin relates to your Cursor team membership.
- 1Claim the codebase name at cursor.com/codebase. During the beta, it can't be changed once claimed.
- 2Once Origin is enabled, admins can create repositories and use Permissions to grant access, including repository creation, to other members.
- 3Admins can disable Origin for the team at any time from the dashboard.
The docs disagree on who claims the name. The settings page says a team admin claims it and enables Origin, and that non-admins can request access from the same page. The Origin overview says any team member can claim it by selecting Get Started. The name becomes the {owner} in every repo URL, so agree on it with an admin before anyone claims it.
The privacy-mode rule catches established teams. Teams on legacy privacy mode can't enable Origin, and the docs say to switch to Privacy ModeCursor's setting that guarantees code data is not used for training by Cursor or its model providers, and that an admin can enforce org-wide; data-retention terms are a separate, contractual layer. Press Enter for the full definition. first. Once enabled, Origin follows the Privacy Mode of the namespace owner: the team, or the individual who owns the repo. Switching is a team-wide change with its own effects, so it belongs to whoever owns the team's data policy, not to whoever wants to try Origin this afternoon.
That is the docs' own wording. Treat the three steps above as the stable shape, and expect the toggles and labels under Permissions to move while Origin is in beta. Re-check the page before you write an internal runbook that names them.
Because admins can grant repository creation, an admin can keep the namespace tidy without being the only person who can start a project. We suggest granting it to leads first and widening it once the team has a naming habit.
How do Apps and the Origin API work?
Apps live on the Apps page of codebase settings, at cursor.com/codebase/settings/apps, where you install and manage them for the whole codebase. A repo's own Apps tab shows which installed apps it has, and its Manage Apps button leads back to that page. There are two kinds: third-party apps from the Origin App Marketplace, and private apps your team builds against the Origin API.
- Kind
- Third-party app (Origin App Marketplace)
- Where you install it
- Codebase settings, Apps
- What it is for
- Connect an outside service, such as Vercel, Depot or Buildkite, to your Origin repos; each repo's Apps tab shows which it has
- Kind
- Private app
- Where you install it
- Codebase settings, Apps, after you create the app there
- What it is for
- API access for your own tooling, with app credentials and an installation flow; a workspace admin installs it
| Kind | Where you install it | What it is for |
|---|---|---|
| Third-party app (Origin App Marketplace) | Codebase settings, Apps | Connect an outside service, such as Vercel, Depot or Buildkite, to your Origin repos; each repo's Apps tab shows which it has |
| Private app | Codebase settings, Apps, after you create the app there | API access for your own tooling, with app credentials and an installation flow; a workspace admin installs it |
From cursor.com/docs/origin/apps and the Build an Origin App page.
Cursor's Origin Apps page lists 22 marketplace apps in six categories, including Vercel, Depot and Buildkite. The marketplace is open to submissions: make your app public and submit it for review.
Every app works only on Origin-hosted repos, so a repo mirrored from GitHub keeps its CI and integrations on GitHub.
Apps authenticate with app JWTs and installation access tokens, the same pattern GitHub Apps use. The Origin API reference covers the base URL, scopes, webhooks and endpoints. To try the API before you build an app, use the origin api command in the Origin CLI, which makes authenticated requests with your own login.
Can Automations and cloud agents run on Origin repos?
Yes, and the docs treat Origin like GitHub or GitLab here. An automation runs cloud agents on a schedule or when source-control events fire, and you point one at an Origin repository the same way you would at a connected GitHub or GitLab repo. Its agents can then review, change and push code on that repo. The Agents and automations page lists these common triggers for Origin repos:
- Push to branch (for example, a push to main or master)
- Pull request opened, Pull request pushed and related PR events
- Label change, for a label added to or removed from a pull request
Billing, sharing and the full trigger list are in the Automations docs. Create an automation from cursor.com/automations, the Agents WindowCursor's surface listing your agent runs; open a run to read its diff and search transcripts from the command palette. Press Enter for the full definition. or the /automate skill. Then pick the Origin repo or a multi-repo environment that includes it, set the trigger and prompt, and save and activate it.
Outside an automation, a cloud agent can still clone an Origin repository, branch, commit and push. A mirrored repo sends its pull requests to GitHub, while a repo created on Origin keeps them on Origin. Attaching an agent works like any other connected source control: you pick the Origin repo from your team's codebase. A local agent in Cursor can go a step further and create the repo through the Origin CLI, as the create-repository page explains.
For governance, the docs say agents use your Cursor account's Origin access, so the Permissions decisions above also limit what each person's agents can reach.
Automations on a team account add a Run as choice: Me runs with the creator's auth, and Service account runs the automation as its own dedicated account. Only team admins can pick Service account. No Origin or Automations page we checked says what Origin access that account gets, so try it against one repo before relying on it.
How do you browse and search code on Origin?
Open a repository at cursor.com/codebase and use the Code tab to browse files, search code and inspect commit history. The repository header carries Pull requests and Settings tabs next to Code, and the green Code button opens clone setup for HTTPS, SSH and the Origin CLI.
- Folders and files
- Browse directories and open files in the tree. Switch branches from the branch control in the header.
- Search
- Go to file (shortcut T) or the search field in the repository header, for files and code matches.
- Branch history and commits
- Open commit history for the current branch, then select a commit to see its message, metadata and changed files. Change branches with the branch control first. All authors, or an email, filters by person, except on one file's or folder's history.
From cursor.com/docs/origin/browse.
Two GitHub habits carry over: T for go-to-file, and switching the branch before you open history, so you read the branch you meant to.
The docs describe search only from inside a repository and don't mention searching across every repo in a codebase, so assume search covers the repo you have open.
Frequently asked questions
What is the difference between codebase settings and repository settings on Origin?
Codebase settings apply across all of your team's Origin repos and open from the codebase home: Permissions, Notifications and Apps. Repository settings are a tab on one repo: General, Access, Rules and Protections and Apps on a team-owned repo, or General, Collaborators, Apps, Rules and Protections and Advanced on a personal one.
Who can enable Origin for a team?
It depends which docs page you read. Per the settings page, a team admin claims the codebase name and turns Origin on, while non-admins request access there. Per the Origin overview, any team member can claim the name via Get Started at cursor.com/codebase. After that, admins grant access, including repository creation, and can switch Origin off from the dashboard.
Why can't my team enable Origin?
Check the plan and the privacy setting. Free and Plus don't include Origin, and a team still on legacy privacy mode has to move to Privacy Mode before it can turn Origin on. That move is a team-wide data-policy setting, not a per-user toggle.
Which apps can I install on an Origin codebase?
Any of the 22 apps in the Origin App Marketplace, such as Vercel, Depot and Buildkite, or a private app your team builds. Installed apps run only on repos hosted on Origin, so a mirror of a GitHub repo keeps its integrations on GitHub. Apps authenticate with app JWTs and installation access tokens.
Do Cursor Automations work with Origin repositories?
Yes. Point an automation at an Origin repository the same way you would at a GitHub or GitLab repo. Common triggers are push to branch, pull request opened or pushed, and label changes. Create one from cursor.com/automations, the Agents Window, or the /automate skill.
How do I search code in an Origin repo?
Open the repo's Code tab. Press T for Go to file, or type in the search field in the repository header to match file names and code. The same tab holds commit history for the current branch, which you can filter by author.
Sources & last verified
- Cursor Docs: Browse & Search
- Cursor Docs: Origin repository settings
- Cursor Docs: Automations
- Cursor Docs: Origin
- Cursor Docs: Origin agents and automations
- Cursor Docs: Origin Apps
- Cursor Docs: Build an Origin App
- Cursor Docs: Clone, Push & Pull
Cursor ships frequently. Facts verified against primary sources on October 28, 2026.