Cursor Shared Transcripts: Team Links, Redaction, Limits

Cursor describes the feature as sharing "read-only copies of your AI conversations with teammates or the public via a link," with the full history included: code snippets, tool calls and their results. Recipients are not limited to reading. Any of them can press Fork to Cursor and continue the conversation in their own editor, which turns a shared debugging session into something the next person picks up and keeps working.

1. 1Open the chat you want to share and click the Share icon in the header.
2. 2Pick visibility: Team (signed-in members of your team; listed in the dashboard under Shared Transcripts) or Public (anyone with the link, no sign-in, at a cursor.com/s/abc123 URL).
3. 3Copy the share link and send it wherever the discussion lives.

That order matters more than it looks. The review belongs before the click and not after, because a public link is live the moment it exists, and deleting it from the dashboard revokes access without un-reading the page for whoever already opened it.

Visibility is also a decision you can only widen comfortably. Team to Public later is a change you make in the dashboard, while the other direction leaves a link you have already sent people. Teams plans get both link types; on Enterprise, team links are the only ones available by default.

Read-only covers what a recipient can do to your copy of the conversation, and Fork to Cursor is what they can do with it. The thread reopens in their editor with the shared history as its starting context. For a bug handoff that is exactly the point, and on a public link it means anyone who opens the page can carry the whole conversation into their own editor, which is worth a beat of thought before you widen the audience.

Best-effort only, and Cursor says so plainly: it "applies best-effort redaction for known secret patterns, such as common API key formats, tokens, and passwords"; in the same breath, "Redaction is not guaranteed and can miss secrets, especially custom values or values without recognizable prefixes." The operational rule follows directly: "Review transcripts before you share them. Do not share content that includes secrets you cannot expose."

The qualifier at the end of that quote is the part to plan around. Redaction is pattern matching, so it catches the shapes it knows and skips anything that reads like ordinary text, such as a bare token from your own auth service or a customer email sitting in a row of query output. Cursor does scope this in one genuinely useful way: local files, authentication credentials and your identity are not included in a share. What travels is the conversation and whatever the agent pulled into it while it worked.

How much comfort to take from that depends on what your agents touch. Transcripts that are mostly reasoning about application code are fine to pass around. Where an agent read production rows or ran a migration, though, the safer default is to treat the thread as unshareable and copy out the two paragraphs that matter. That is a policy call, and the product does not make it for you.

From the dashboard. Open the Shared Transcripts tab at cursor.com/dashboard, where you can change a transcript's visibility or delete it, and where team admins can delete any member's transcripts, not only their own. That admin power is the cleanup path for the two cases that really come up: a thread shared publicly that shouldn't have been, and someone leaving the company with links still live.

It is also the first place to look when a Team link stops opening for a colleague.

Small teams can run this on trust, and I think most do. Past the size where you know which repos everyone touches, somebody has to own what is public, and the Shared Transcripts tab is where the full set is visible. A monthly skim of that list is the cheapest version of that job.

Teams and Enterprise only. Individual and Pro plans do not have the feature. Teams plans get both team and public links; Enterprise gets team links only by default, so the larger plan is the more restricted one here.

"By default" is doing work in that Enterprise line. It reads like something an admin can change, and the help page does not say either way. Whoever owns your Cursor org will know, so ask them, and treat public links as unavailable on Enterprise until they say otherwise.

The gating makes this a team-workflow feature in practice. Prompt-technique show-and-tell and bug reports handed over with the agent's full context are the two uses that survive contact with a real week; onboarding examples of how your team drives a refactor are a third, if somebody maintains them. Anyone on an individual plan who wants the same effect is back to screenshots and copy-paste.

I used to describe all of this as "sharing is a paid-plan feature" and leave it there. That is too coarse to act on, because the gates sit on features rather than tiers. Shared canvases, the nearest neighbour, are available on Pro if you are on a team, and transcripts are not, though both need a privacy mode that allows data storage. Check the surface you actually plan to use before you promise a workflow to anyone.

The 50-a-day cap is probably the number to worry about least. Nobody clicking Share by hand gets near it, and if something you built is getting near it, the cap is the second problem. Treat it as a ceiling on automation and forget about it otherwise.

When you cannot share a chat at all, the two documented reasons are the plan and No Storage 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.. Check both before filing a bug. If it is the Public option specifically that is missing on Enterprise, that is the documented default for the plan.

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. is the one of those two you may not control yourself. Team admins can enforce and lock it org-wide, so the toggle is not always yours to flip, and with no stored conversation there is nothing for a share link to point at. A team in that position should plan its review flow around pasted excerpts and stop hunting for the Share icon.