Your work stays private
Automatic activity tracking records your totals, not your conversations or project content.
Kimi Code integration
Turn local Kimi Code activity into a durable work history.
Agentprint turns your Kimi Code activity into a year-long history, model mix, streaks, and a profile you control.
Agentprint tracks historical coding activity. It does not report remaining Kimi quota, reset windows, or provider billing.
Kimi Code
Claude Code
Codex
Local activity collectorNormalizes numbers, not conversations
DateskeptTokenscountedContentexcluded
Your AgentprintA living activity historyPrivate until you choose otherwise
Local firstKimi activity read on-device
Two pathsTracking and sharing stay separate
PrivateYour profile starts hidden
The useful outcome
Keep the pattern, without syncing the work itself.
Kimi Code sessions contribute to the same cross-agent activity field as your other tools, while prompts, responses, code, repository names, and local paths remain outside normal sync.
- 1
Connect your machine
Sign in without sharing your Kimi account credentials.
agentprint login - 2
Add your Kimi Code activity
Agentprint finds Kimi Code and adds its activity totals to your profile.
agentprint sources && agentprint sync - 3
Choose what becomes public
Keep the profile private or independently show tokens, coding tools, models, and streaks.
Built into the workflow
Useful by design, clear about the boundary.
Cross-agent history
Kimi Code activity can live beside Claude Code, Codex, and OpenCode on one profile.
Deliberate session sharing
A specific Kimi Code session can be previewed and redacted locally through the separate share command.
Frequently asked questions
What Kimi Code activity does Agentprint record?
Dates, token counts, the coding tool and version, provider, and model. It does not include the contents of your work.
Does Agentprint share Kimi Code prompts automatically?
No. Automatic activity tracking never includes prompts, replies, code, repository names, or paths.
Can I share one Kimi Code session?
Yes. Kimi Code has a supported session reader. Sharing remains a separate explicit workflow with a local redacted preview before upload.
Can Kimi Code activity remain private?
Yes. The profile begins private, and each public metric group has its own visibility control.
Keep exploring.
Follow the product from the question you have now to the exact workflow that answers it.