Turn any Code transcript into a public link at continuumcode.ai/share/<id>. The page is immutable, server-redacted, and safe to drop in Slack, iMessage, or X - without shipping your username or raw tool payloads.
The cloud doesn’t scrape your host history. Clients POST the transcript items they render; Continuum stores an immutable, redacted copy and returns a hard-to-guess link.
From Mac, iPhone, web, desktop, or the terminal client - any Code session transcript you can open.
See the redacted page before it goes public. Set expiry: 7 days, 30 days, or never.
Copy continuumcode.ai/share/<id>. SSR page with Open Graph tags; after load, no further network.
GUI clients mint with your account bearer. The host proxy path exists for the terminal client when there’s no cloud login.
Redaction runs only on the server. Clients never “pre-clean” for trust - so no surface can widen what a link exposes. Messages are rebuilt from a known key set; unrecognized fields are dropped.
No username leak in the serialized payload. Tool detail / raw input is deliberately not stored - the UI never needed it, and it was the largest leak surface.
Choose 7 days, 30 days, or never when you publish. Revoke kills the link immediately. You can also update a share when you need a corrected snapshot without guessing a new URL.
Unlisted is the model: no directory, no search listing - reach depends on the link, and entropy on the id is the real gate (not robots.txt tricks that break social unfurls).
Settings → Shared Links lists every share you own: title, expiry, and view counts. Open, copy, update, or revoke without hunting through old sessions.
The public page is server-rendered so Slack, iMessage, and X get real Open Graph tags. The transcript is inlined; the page makes zero requests after load.
Short answers here, long answers in the docs.
No. Redaction is server-side only. Clients upload the items they render; Continuum rebuilds an allowlisted copy. There is no client “trust me, I cleaned it” path.
Not after load. The transcript is inlined in the SSR HTML (including OG tags for unfurls). The public page is designed for zero follow-up network under a tight CSP.
Live mirror pages only cover recent, mirror-enabled host activity and are retention-pruned. Sharing an older session that way would silently 404. Publishing the items you’re already viewing is the reliable path.
No - deliberately. The watch never decodes full session transcripts, so there’s nothing to share from the wrist. Mac, iPhone, web, desktop, and terminal client can publish.
Open any Code transcript, preview the redacted page, pick an expiry, share.
server redaction · immutable · revocable