Share Any Conversation — Private Invite Or Public Link

April 21, 2026

Send a teammate, investor, or friend the whole conversation — privately by email, or as a public link — without leaking credentials, secret tool payloads, or files they shouldn't see. The recipient gets their own forked copy to keep working. Your session stays untouched.

What you can do

• Share privately by email. The recipient gets a branded invite, signs in (or signs up), and lands directly on their own forked copy of the conversation.
• Share publicly with a link. Anyone with the link can read it and download the artifacts. If they sign in, they can fork it and continue the thread in their own workspace.
• Manage shares from one panel. Active, revoked, expired — all visible. One-click revoke kills any live share immediately.
• Re-copy a public link without burning a new one. Hitting "Generate" when one is already live just hands you back the existing link, so you can paste it from anywhere without breaking bookmarks.
• Anything that ran credentials, vault entries, or integration secrets is automatically redacted. The recipient can see something happened on that turn so the conversation still reads, but never the actual API key, password, or OAuth payload.
• Artifacts are downloadable. Slides, videos, images, and docs the conversation produced are listed on the shared page, ready to download. Temp files and dotfiles are filtered out — the recipient sees only the deliverables.

When you'd reach for it

• An investor wants to read through a research session end-to-end without you narrating it. Share → Public link, paste it in an email, they see the whole thread — artifacts and all — in the same layout you saw.
• You're handing a campaign off to a freelancer. Share → Private to their email. They sign up and land in their own fork of your conversation, ready to keep going without losing context.
• You shared something you shouldn't have. Open Share History, click Revoke, and any live reader hits a clean 403 immediately.

Try it

• "Share this conversation publicly and give me the link."
• "Share this conversation privately with alex@example.com."
• "Show me every share I've sent and which ones are still active."
• "Revoke the share I sent to jordan@example.com last week."

Heads up

• Private invites expire after 7 days if the recipient hasn't claimed them. A safety net so stale invites can't be claimed months later.
• There's a daily share cap per user. High enough that normal use never hits it, low enough to stop runaway fan-out.
• Forks are real, independent sessions. Once the recipient claims the share, their copy is theirs — edits on either side don't cross over.
• Public links are readable by anyone who has them. Treat them like a Google Doc "anyone with the link" share. Use a private email invite if that's not what you want.