aka-setup

AKA setup wizard

You are onboarding the AKA Security plugin for this machine. AKA works fully locally with zero backend and zero Docker: detection runs in-process and findings persist to a local SQLite store at ~/.aka/data/aka.db.

This wizard tells a calibration story: introduce AKA → show what it does → offer one retroactive scan → report the real numbers it found and the posture it recommends → apply on confirmation → show the installed summary → hand off to the dashboard. Everything the user sees is derived from their actual history — never a fabricated or demo number. When there isn't enough history to judge, the wizard falls back to a conservative severity-derived floor instead of guessing.

The false-positive/severity judgment needs the raw (unmasked) findings to rate them accurately, so it sends them to the model API through separate agy subprocesses (a large history is judged in several batches). Two things cross for each finding: its raw value, and about 120 characters of the surrounding transcript text on either side of it — re-masked first, so any other detectable secret in that window never leaves raw. The transcript file's path, the value's fingerprint, and the fingerprint key version are dropped before egress. A copy of the raw value leaves the machine, sent to the model provider like any other Antigravity prompt. You act only on the raw-free plan the subprocesses print back.

Two limits of this host are worth knowing before you consent, because they are weaker than the Claude Code and Codex plugins' equivalents:

• The agy CLI documents no ephemeral mode. Every run is written to your conversation store under ~/.gemini/antigravity/brain/, raw values and all — the same store this backfill scans. AKA therefore deletes the judge's own conversation itself as soon as the run ends. That deletion is best effort: if the process is killed between the write and the cleanup, the conversation stays on disk until you remove it.
• Deleting the conversation is not network isolation. It is a local-write cleanup only; it cannot recall what was already sent.

Reading history is granted in step 1; sending findings to the model is a distinct consent, collected in step 3 before the judgment pipe runs — the judge refuses to run without it.

Follow the steps below in order. Nothing is written to the policy store until step 5 (or a floor fallback in step 3 if the calibration can't complete).