Sharing is always deliberate
Automatic activity tracking never turns your conversations into published sessions.
Agentprint session sharing
Agentprint turns one coding-agent session into a readable link. You choose the session, inspect the prepared version on your machine, choose who can open it, and keep every other session private.
Redaction looks for common sensitive details, but no automated check can promise that every secret is gone. The local preview is there for you to read before publishing.
A finished feature or fix rarely shows the reasoning behind it. Session sharing preserves that useful story without turning your full coding-agent history into public content.
Browse the supported sessions found on your machine and select the one that tells the story you want to share.
Agentprint creates a local preview, replaces likely credentials, rewrites private paths, removes images, and trims long output before anything is published.
Keep the link unlisted, limit it to accepted friends, or make it public on your profile.
Share the same session again to update its link, or revoke it to permanently remove the published copy.
Automatic activity tracking never turns your conversations into published sessions.
You see the prepared session before Agentprint asks whether you want to publish it.
New shares begin unlisted. Public and friends-only visibility require a choice from you.
It is a way to publish one selected coding-agent session as a readable link after reviewing a redacted preview on your machine.
No. Normal activity collection does not include conversations. A session is only prepared for publishing after you select it and start the sharing flow.
Agentprint supports sharing selected Claude Code, Codex, and Kimi Code sessions. OpenCode activity can appear on your profile, but OpenCode session sharing is not currently supported.
Yes. Revoking a share permanently removes the published session and disables its link.
Follow the product from the question you have now to the exact workflow that answers it.