Agent Secret Leak Sentinel

Scans AI coding agent logs for leaked secrets and tells you exactly what to rotate

Problem

In the Warp security incident, users were told their agent traces might contain secret keys and to consider rotating them — but individuals had no way to know which keys leaked or what to rotate. Developers routinely feed entire codebases and terminal context to agents like Claude Code or Codex, and API keys and DB passwords easily end up in traces and logs.

Solution

Run regex and entropy scanning locally or in CI over agent session logs, trace files, and terminal transcripts to detect common API keys, tokens, and connection strings. On a hit, show exactly where it leaked, which service the key belongs to, and generate an actionable rotation checklist. Ship as a CLI plus a lightweight web panel with scheduled scans.

Users

Indie developers and small teams who heavily use AI coding agents; engineering teams with compliance requirements.

MVP

Scan common agent log directories (Claude Code, Codex); ship 100+ built-in secret regex rules; output rotation checklists grouped by service; run fully local with zero upload.

Revenue

Free tier capped on rule count; Pro subscription unlocks custom rules, team policies, and CI integration; per-seat team pricing.

Why now

AI agents now routinely read terminal and code context, so secrets-in-traces is the new normal, yet platforms only issue vague warnings and no personal remediation tools exist.