Review it on your machine
Agentprint prepares the session locally so you can see the result before sharing it.
Claude Code session guide
Choose a Claude Code session, review what will be shared on your machine, and publish it as unlisted, friends-only, or public. Your other sessions stay private.
A shared session can preserve the useful arc of a debugging or building run without sharing your other conversations.
Agentprint reads recent Claude Code sessions locally and presents a short list you can inspect.
agentprint sessionsDry run opens a local preview without publishing anything.
agentprint share 2 --harness claude-code --dry-run --redact strictChoose visibility at publish time. Re-sharing the same session updates its existing URL; unshare deletes it.
agentprint share 2 --visibility unlistedAgentprint prepares the session locally so you can see the result before sharing it.
Sharing one session does not include your other conversations or projects.
New shares default to unlisted and only appear on a public profile after you intentionally make them public.
No. Agentprint focuses on local CLI session discovery, local redaction preview, visibility controls, and a profile that can combine activity across supported coding agents.
No. It records activity totals such as dates, token counts, and models—not prompts, responses, source code, repository names, or paths.
Strict is the safest starting point because it omits tool arguments, tool output, and agent reasoning. Balanced and full preserve more context, so they require more careful preview review.
Yes. Run agentprint unshare to permanently delete it and disable its link.
Follow the product from the question you have now to the exact workflow that answers it.