Agents & Workflows
Cursor Shared Transcripts: Team Links, Redaction, Limits
Shared transcripts publish a read-only copy of a Cursor conversation — code, tool calls and results included — via the Share icon in the chat header, scoped to your team or public at a cursor.com/s/ link. Teams and Enterprise plans only, capped at 50 shares per day, with best-effort (not guaranteed) secret redaction.
On this page
What are shared transcripts in Cursor?
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. The receiving side is not a screenshot: recipients can hit Fork to Cursor on a shared transcript and continue the conversation in their own editor, which turns a debugging session into a handoff artifact.
- 1Open the chat you want to share and click the Share icon in the header.
- 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/…URL). - 3Copy the share link and send it wherever the discussion lives.
This is covered hands-on in Agent Mode Foundations — 6 short modules, free to read.
Does Cursor redact secrets in shared transcripts?
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" — and in the same breath, "Redaction is not guaranteed and can miss secrets." The operational rule follows directly: "Review transcripts before you share them. Do not share content that includes secrets you cannot expose."
The dangerous content in an agent transcript is rarely the conversation — it's the tool results: environment listings, config file reads, database rows a query returned. Skim the tool-call blocks specifically before sharing, and prefer Team visibility whenever the audience allows it.
Which plans get shared transcripts, and what are the limits?
- Plans
- Teams and Enterprise only.
- Daily cap
- 50 shares per day.
- Privacy interaction
- Unavailable with No Storage Privacy ModeCursor's setting that routes requests under zero-data-retention terms so providers don't store or train on your code. Press Enter for the full definition. — no stored conversation, nothing to share.
- Recipient powers
- Read-only viewing, plus Fork to Cursor to continue the conversation in their own editor.
Per cursor.com/help/ai-features/shared-transcripts, checked 2026-07-16.
The plan gating makes this a team-workflow feature in practice: prompt-technique show-and-tell, bug-report handoffs with full agent context, and onboarding examples ("here's how we drive a refactor") are the patterns that stick. Individual-plan users wanting the same effect are limited to screenshots or copy-paste.
Frequently asked questions
Who can see a shared Cursor transcript?
Your choice at share time: Team links are visible to signed-in members of your team (and listed in the dashboard under Shared Transcripts); Public links are open to anyone holding the cursor.com/s/ URL, no sign-in required.
Can someone continue a conversation from my shared transcript?
Yes — any recipient can click Fork to Cursor on a shared transcript and pick the conversation up in their own editor, with the shared history as the starting context.
Are shared transcripts available on the Pro plan?
No — Teams and Enterprise plans only, with a limit of 50 shares per day. The feature is also unavailable when No Storage Privacy Mode is on.
Is the secret redaction safe to rely on?
No. Cursor applies best-effort redaction for known secret patterns but states outright that it can miss secrets. Review the transcript — especially tool-call output — before sharing, and don't share anything containing secrets you cannot expose.
Sources & last verified
Cursor ships frequently. Facts verified against primary sources on July 16, 2026.