senkani compare

Run one command across four feature permutations and compare the token savings. The CLI counterpart to senkani exec when you want to know what each filter rule actually buys you.

Syntax

Behavior

Runs <cmd> once, captures the raw output, then re-applies four FilterPipeline permutations — passthrough, filter only, secrets only, all features — and prints a per-permutation byte / saved-% / bar-graph table. Use it before adding a filter rule to confirm the rule actually moves the needle on the workloads you care about.

Example

$ senkani compare -- git status

Flags