Skip to content

Collection boundary

Agentprint keeps the activity signal and leaves the work itself behind.

Automatic sync accepts a small numeric record: when activity happened, how many tokens were recorded, and which supported coding tool, version, provider, and model produced it.

Transcript publishing is a separate, explicit action. Turning on activity sync does not turn on conversation sharing.

Start with Agentprint See how it works
NumericDates and token totals
Source-awareTool, version, provider, and model
Content-freeNo prompts, replies, code, repos, or paths
The useful outcome

A narrow contract that is easier to inspect and enforce.

The collector does not try to upload a full local record and hide fields later. It constructs a recognized activity object and the API rejects unknown or content-bearing fields.

  1. 1

    Discover a supported local source

    Agentprint checks known local records for Claude Code, Codex, OpenCode, and Kimi Code without asking for provider account passwords.

    agentprint sources
  2. 2

    Construct a strict activity record

    The adapter emits dates, token counts, coding-tool identity and version, provider, and model. Prompt text, responses, source code, repository names, local paths, shell history, keys, and credentials are excluded.

  3. 3

    Reject anything outside the contract

    The shared schema and ingestion API refuse unknown fields rather than storing arbitrary source records for future use.

  4. 4

    Apply profile visibility at the data boundary

    Public-profile queries include only the metric groups you enabled, instead of downloading private fields and hiding them with browser styling.

Built into the workflow

Useful by design, clear about the boundary.

Collection is intentionally boring

The normal sync record is useful for activity history precisely because it excludes the interesting—and sensitive—substance of the session.

Visibility is enforced before rendering

Token totals, coding tools, models, and streaks each have a server-enforced public visibility control.

Leaving stays possible

You can pause collection, revoke a device, export your account data, remove shared sessions, or delete the account.

Frequently asked questions

Does Agentprint upload my prompts during automatic sync?

No. Prompts and assistant replies are not part of the automatic activity contract.

Does Agentprint collect repository names or file paths?

No. Repository names, project paths, home directories, and source code are outside automatic activity collection.

What fields can appear in my public profile?

Your display identity and the activity groups you enable: token totals, coding-agent mix, model mix, and streaks. Each activity group has its own visibility control.

How is session sharing different?

It uses a separate command, contract, endpoint, database path, local preview, confirmation step, visibility choice, and revocation workflow for one selected session.

Keep exploring.

Follow the product from the question you have now to the exact workflow that answers it.

Activity methodologySee how accepted numeric records become a daily history.
Session redactionUnderstand the separate content-sharing workflow.
Supported coding agentsInspect source-specific capabilities and limitations.