Cursor launches profiles with public handles and team opt-in controls

• Cursor shipped ericzakariasson's launch post for public profiles, letting users claim first-come handles and publish shareable pages at cursor.com/@handle, as Cursor's own Profiles docs confirm.
• A claimed handle flips the page public by default, and the docs say profiles can show your account name, profile photo, join date, up to four outbound links, and usage activity over time, which lines up with DannyLimanseta's claimed profile.
• Teams get an extra gate: ericzakariasson's follow-up says org admins can enable public profiles from team settings, adding an opt-in layer above the personal public/private toggle in the official docs.

You can claim a handle, read the official profile docs, and inspect a live example at Danny Limanseta's public page. The docs also bury one important constraint: handles are permanent once claimed, while ericzakariasson's settings screenshot shows teams can still decide whether the feature is available at all.

Cursor framed the release as a lightweight identity layer. ericzakariasson's launch post points users straight to the claim page, and the official docs say handles use lowercase letters, numbers, and single hyphens, must be at least three characters long, and are first come, first served.

The same docs add two details that matter more than the teaser tweet: you cannot change a handle after claiming it, and Cursor reserves the right to reclaim names tied to products, impersonation, policy violations, or other abuse.

A live profile already looks closer to a coding stats page than a static bio. According to the Profiles docs, each page can show a name, avatar, join date, four custom links, and usage data over time.

Danny Limanseta's example page exposes the shape of that usage layer: streaks, longest agent run, total agents, model breakdowns, token totals, and a split between local and cloud agents. The docs also say the owner keeps the handle even if they turn the page private later.

Cursor did not ship profiles as a blanket org-wide default. In ericzakariasson's follow-up, Zakariasson points team users to a dedicated public-profiles switch inside team settings, which means admins can gate access before individual members publish anything.

That sits on top of the personal toggle described in the Profiles docs, where each claimed page can be switched on or off without releasing the handle. Cursor's broader team dashboard docs already describe the admin panel as the place for team-wide preferences and security settings, so profiles are landing inside an existing control surface rather than as a separate social feature.