Skip to content

Session redaction

Redaction is a review layer, not a promise that secrets cannot exist.

Before Agentprint publishes a selected coding session, it rewrites likely credentials and private paths locally, removes unsupported media, and shows you the exact prepared payload.

Automated detection is defense in depth. You remain responsible for reading the local preview before publishing a session.

Start with Agentprint See how it works
Local firstRedaction happens before upload
2 checksCLI preparation and server rejection
3 levelsStrict, balanced, and full
The useful outcome

Make the final payload inspectable before it leaves your machine.

The safest sharing decision comes from combining conservative automated rewriting with an exact local preview and a separate confirmation step.

  1. 1

    Select one supported session

    Agentprint reads only the session you choose from a supported local reader. Browsing the list does not publish anything.

    agentprint sessions
  2. 2

    Apply the chosen redaction level

    Credential-shaped values become visible markers, home and project paths are rewritten, images are removed, and long output is truncated. Strict mode also omits tool details and reasoning.

  3. 3

    Open the exact local preview

    Dry run writes and opens the escaped serialized payload so you can review the real data prepared for the API.

    agentprint share 3 --dry-run --redact strict
  4. 4

    Confirm, validate, and publish

    After confirmation, the server checks uploadable strings again and rejects payloads that still resemble credentials.

Built into the workflow

Useful by design, clear about the boundary.

Preview failure stops confirmation

If Agentprint cannot open the local preview, it does not silently continue into an interactive publish confirmation.

All uploadable strings matter

Checks cover titles, summaries, harness and model metadata, turn content, tool identifiers, inputs, and outputs—not only the visible transcript body.

Deletion remains part of safety

Published sessions have stable share IDs and can be permanently removed with agentprint unshare.

Frequently asked questions

Can Agentprint guarantee that every secret is redacted?

No. Automated matching can miss unexpected formats or sensitive context that does not resemble a credential. Always read the exact local preview before publishing.

What is different about strict mode?

Strict mode preserves user and assistant text while omitting tool arguments, tool output, and agent reasoning. It is the safest starting point for a public example.

Why check the payload again on the server?

The server is a backstop for uploadable data. It prevents a client regression or older client from publishing strings that match known credential shapes.

Can I inspect without uploading?

Yes. The dry-run command prepares and opens the local preview, then exits without publishing.

Keep exploring.

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

Share a Claude Code sessionFollow a complete tool-specific walkthrough.
What Agentprint collectsSeparate background activity from explicit sharing.
Privacy policyRead the complete product privacy explanation.