Reference

Limits

A measurement tool that overstates its reach is worse than none. These are the boundaries.

It only sees what the agent already logged

If a session was never written to disk, or the transcript was deleted or rotated away, there is nothing to read. Actualis reconstructs history from records that already exist; it does not create new ones.

Secret detection is pattern-based

A bespoke internal token with no distinguishing shape can pass unnoticed. A clean report means nothing matched, not nothing is there.

Subagent shell activity is partly invisible

Commands run inside subagents are not recorded in the parent transcript. The report states what share of shell activity that accounts for rather than quietly under-counting — that is finding AF011.

Cost depends on published rates

Spend is computed from recorded token counts against published per-model rates. A model with no published rate is priced at the top of the known range for its provider, so that portion is an upper bound rather than a measurement. It is included in the total but reported as its own number (cost_usd_from_unpriced_models), so you can subtract it and see the floor instead of having to trust the estimate. Rates sourced from a third party rather than the vendor are flagged separately.

Deduplication depends on message ids

One billable message can appear many times in a transcript while a response streams. Repeats are collapsed by message.id, so a record carrying no id cannot be keyed and is always counted. If a transcript format stopped emitting ids, over-counting would return silently — a repeat count of zero on a large scan is the signal that this has happened.

Two agents are supported

Claude Code and Codex are the transcript formats implemented. Other tools are not partially supported without saying so — they are simply not read. Cursor and Windsurf keep their content server-side, so there is nothing local to read; verified on a machine with both installed.

It will not rotate, revoke or block anything

Actualis tells you a credential was exposed. Rotating it is your job, and deliberately so — a read-only tool cannot break your workflow, and that guarantee is worth more than the convenience of acting for you.