Handles and recovery

Nothing tokunseba removes is destroyed. Every substitution names a handle, and the handle holds the original.

tokunseba expand h_4b91c07e

That prints the original text exactly as it arrived: the same bytes, the same line endings, the same trailing whitespace. If what comes back differs in any way from what your tool produced, that is a bug worth reporting.

Where handles come fromCopy Anchor Link

A handle looks like h_ followed by twelve hexadecimal characters, derived from the content. The same text always gets the same handle. They appear:

• inside the replacement text, so the model can ask for the original
• in tokunseba top, so you can
• in tokunseba explain, next to what they replaced

Three ways to redeem oneCopy Anchor Link

tokunseba expand h_4b91c07e

When a handle is goneCopy Anchor Link

expand returns nothing and says so. There are exactly two reasons:

1. The retention window passed and the blob was pruned. Default is 90 days for the ledger and 14 days for stored request bodies. See Retention.

2. The text contained something that looked like a credential, so it was never written to disk in the first place. In that case the marker says so rather than naming a handle:

   Copy Text

   [tokunseba: the full text is not stored, because it contains what looks like a
    credential. Nothing was written to disk.]

Seeing one request in fullCopy Anchor Link

tokunseba explain 1f4c9a20e8bb

Prints the request block by block, original beside replacement, with the transform kind and the token counts for each. This is the command to reach for when you want to know exactly what the model saw.

Request ids come from tokunseba top, tokunseba stats --json, and tokunseba replay --verbose.