Shows mode, source (local, profile, default), the number of your own secret files and exclusions, and the protection per agent.
sudo poison0 leak0 enforce, observe, off
Sets the mode locally.
sudo poison0 leak0 clear
Removes the local setting; then the profile or off applies.
sudo poison0 leak0 file add <glob> --keys k1,k2
Adds your own secret file, --keys optional. Also file remove and file list.
sudo poison0 leak0 exclude add <glob>
Adds an exclusion. Also exclude remove and exclude list.
poison0 leak0 allow <file>
Approves a secret file for commits (10 minutes) and one push.
On Windows, without sudo in an administrator terminal. On cloud devices the changing commands other than clear refuse to run; the console applies there.
Profile fields
Field
Values
leak0.mode
enforce, observe or off. New profiles: On, existing ones: Off.
leak0.secretFiles
Up to 200 entries { path, keys }; path is a glob, ~ and %USERPROFILE% are allowed.
leak0.exclusions
Up to 200 globs that do not count as a secret source.
leak0.userMayApprove
true (default) or false: whether users may approve secret files in Git.
Edge cases
Situation
Behavior
Token sent to its own sign-in endpoint (Authorization header, user:token@host)
Question or note, no block.
Copy to your own servers, S3-compatible storage, your own GitLab or Vault
No block; a question for a credential file.
.env, ~/.zshrc or PEM files in the repository
Question, placeholder or note, no block.
Secret file with real values in a test folder
Question instead of block.
Checksummed token in a docs folder
Question instead of block. leak0 checks secret files there like anywhere else.
Git check does not finish in the time available
Question, otherwise a block with a request to retry. Never unchecked.
Test folders:test, tests, testdata, fixtures, fixture, __tests__, __fixtures__, __mocks__, plus *_test.*, *.spec.*, *.test.* and templates ending in .example, .sample, .template. Docs folders:docs, doc, examples, example, samples, sample, spec. The path from the repository root counts.
Approval limits
Situation
Behavior
New attempt after a refusal or no answer
No new dialog for the same file for 60 seconds, block.
More than three dialogs in one minute
Block without a dialog.
No desktop, nobody signed in or PoisonZero service not reachable
Block; the message names poison0 leak0 allow.
Failed attempts with allow
3 seconds between two attempts, locked for 15 minutes after 5 failures.
File changed after the approval
The approval no longer applies.
The sign-in of the account the agent runs under counts; no admin rights are needed. The PoisonZero service must be running.
Hooks
Situation
Behavior
Installation or turning it on in a cloud profile
Adds the hooks to every supported agent found.
leak0 or exec0 off
The hooks stay; only uninstalling removes them.
Hook does not run, Claude Code
The tool call is blocked when leak0 or exec0 runs in mode enforce.
Hook does not run, other agents
The agent continues the call.
Audit
Action
Meaning
leak0_blocked
Call blocked with proof. Incident.
leak0_asked
Question asked, for Codex and Gemini CLI with the result of the PoisonZero dialog.
leak0_redacted
Value in an output replaced with a placeholder. Incident.
leak0_warned
Note instead of intervention because the agent does not allow it.
leak0_observed
Hit in mode Observe. In the console only with Also in the console (cloud audit).
leak0_granted
File approved with poison0 leak0 allow. Incident.
leak0_grant_failed
Approval failed, sign-in wrong or cancelled.
leak0_grant_locked
Approval locked after too many failures. Incident.
Fields: agent, tool, rule class, mode and short hash. Never: secret value, path, command or prompt. Short hashes of detected values stay on the device per session and are deleted at the end of the session or after 24 hours.