Origin overlay in Agents cannot be dismissed; Get Started claims the org codebase name

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The standalone Agents window (Glass) now shows an Origin / Codebase promotional surface that covers a large part of the app. It cannot be closed, dismissed, or moved. There is no X, no Esc dismiss, and it is not an OS window so it cannot be dragged.

The only obvious way out of that UI is Get Started. Per Cursor docs, Get Started claims a codebase name for the entire Cursor organization/team — the namespace for https://cursor.com/codebase/{owner}/

That is a coercive design: a non-dismissible overlay whose only exit performs an org-level side effect. Users who only wanted their Agents chat back are forced to opt the whole team into Origin hosting they did not choose.

I use Agents only, on native Windows. Origin CLI is documented as macOS/Linux/WSL only, so this Windows client is advertising a flow this machine cannot complete, then insisting the way off the overlay is to claim the org codebase anyway. I already clicked Get Started because it was the only way to recover the UI. That should never have been required.

Steps to Reproduce

  1. Use Cursor standalone Agents window (Glass) as the daily UI. Do not use the editor layout.
  2. After Origin early beta rollout (changelog 2026-08-17), launch the Agents app on Windows 11.
  3. Observe an Origin / Codebase Get Started surface covering a large portion of the Agents UI.
  4. Try to close it: no close control. Try to move it: it is not a window; it will not drag.
  5. Esc / clicking elsewhere does not restore the chat surface.
  6. The only action that proceeds is Get Started, which (per Origin docs) claims the codebase name for the whole organization.
  7. Click Get Started because it is the only way to get the app back. Org namespace is now claimed.

Expected Behavior

  • The Origin / Codebase promo must be dismissible without enabling Origin.
  • Dismiss, close, or hide must not claim a codebase name for the organization.
  • Claiming a team/org codebase name must be an explicit admin action, never the only way off a blocking Agents overlay.
  • Native Windows Agents users should not be pushed into Origin setup when Origin CLI is not supported on native Windows.

Operating System

Windows 10/11

Version Information

Cursor IDE, standalone Agents window (Glass), Windows 11. Origin early beta rollout of 2026-08-17. Origin CLI is not supported on native Windows (macOS/Linux/WSL only).

Additional Information

Docs: Origin | Cursor Docs — “Any team member can claim the codebase name… select Get Started”. Changelog 2026-08-17 launched Origin in the product. Team admins can disable Origin from the dashboard, but that is not a substitute for a user-level dismiss on a blocking Agents overlay.

Requested product fix: dismissible Origin/Codebase UI that does not claim or create org state. Claim-name must be a separate, explicit admin confirmation. Do not force this on Windows Agents-only users.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Thanks for posting, had this same thing just happen on my Mac. No way to dismiss other than click the Try Origin button. Given the multi-platform uniformity of this UI, this seems less likely a bug and more intended and shady design. “That is a coercive design” is exactly right.

Hi Steve, thanks for the detailed write-up, and I’m sorry. First, the part I most want to clear up: nothing was claimed for your organization. I checked on our side, and there is no codebase name registered to your team or to your account.

The Get Started button doesn’t claim a name by itself. All it does is open the setup page at cursor.com/codebase/get-started in your browser. A name is only claimed if you go through that page, pick a name, and submit it. Since you didn’t complete that, your team’s namespace is untouched and there’s nothing you need to undo.

Second, how to get the panel out of your way right now: that banner is tied to the “Start from scratch” (New Repository) option in the target picker, and that option is currently what gets pre-selected when the window opens without a project. If you select any of your existing projects or repositories in that picker instead, the banner goes away, and your normal chat surface comes back, with no Origin setup involved.

Thanks for the response. I got the idea that our code was claimed from the Cursor agent I asked to help me deal with the panel. I had it do the bug report as well.

An X button would have saved all of us a lot of time.