Background sync stays numeric
Normal Kimi Code activity tracking never includes prompts, replies, source code, repository names, or paths.
Kimi Code session guide
Share one Kimi Code session after you have seen the final payload.
Agentprint finds local Kimi Code sessions, prepares a readable redacted preview on your machine, and publishes only the session and audience you choose.
Session sharing is separate from automatic activity tracking. Your other Kimi Code conversations are not included.
Selected local sessionFix retry behavior on 429
Local previewNothing uploaded
CredentialsreplacedLocal pathsrewrittenImagesremovedLong outputtrimmed
UnlistedDefault
FriendsAccepted people
PublicProfile + search
One sessionSelected from local history
Local previewRequired before confirmation
RevocableDelete the session and disable its link
The useful outcome
Preserve a useful build story without publishing your history.
A shared Kimi Code session can document the decisions behind a fix or feature while remaining separate from background activity collection and every other project.
- 1
List recent Kimi Code sessions
Browse locally discovered sessions by title and time. Listing them does not upload transcript content.
agentprint sessions --harness kimi-code - 2
Open the exact local preview
Use a dry run to inspect the serialized payload, rewritten paths, removed images, and redaction markers before publishing.
agentprint share 2 --harness kimi-code --dry-run - 3
Choose the audience
Keep the link unlisted, limit it to accepted friends, or make it public on your profile. You can revoke it later.
agentprint share 2 --visibility unlisted
Built into the workflow
Useful by design, clear about the boundary.
The preview is the payload
The local review represents the escaped data prepared for publishing, rather than a simplified transcript-only mockup.
More context means more review
Strict mode removes the most detail. Balanced and full modes preserve more of the session and require closer inspection.
Frequently asked questions
Does Agentprint support Kimi Code session sharing?
Yes. Kimi Code has a supported local session reader, and a selected session can use the same preview, redaction, visibility, and revocation workflow as other supported readers.
Will Kimi Code conversations be uploaded during normal sync?
No. Automatic activity sync and transcript sharing are separate pipelines. Normal sync only accepts numeric activity metadata.
Can automated redaction guarantee that nothing sensitive remains?
No automated detector can make that promise. The local preview is required so you can read the final payload before deciding to publish it.
How do I remove a shared Kimi Code session?
Run agentprint shares to find the published item, then agentprint unshare with its ID. Deletion disables the link.
Keep exploring.
Follow the product from the question you have now to the exact workflow that answers it.