Codex Privacy HUD plugin
A Codex plugin that shows in each session which personal data the agent sees and where it goes.
- 110 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The installer downloads and substitutes an unsigned patched build for the `codex` launch.
- Hooks can deny actions and rewrite input.
Install
- Works in
Manual install
curl -fsSL https://raw.githubusercontent.com/inin-zou/codex-privacy-hud/main/install.sh | shThe one-step installer command from the README. Read the script before running: it installs dependencies and a patched Codex build.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The installer downloads and substitutes an unsigned patched build for the `codex` launch.
- Hooks can deny actions and rewrite input.
This is third-party code. Review the repository files before installing.
What it does
Codex Privacy HUD records Codex hook observations into a session ledger and can deny an action or rewrite input before a tool runs. The interface shows confirmed disclosures, recipients and the number of denials. A percentage appears only when the records support it. Detection runs locally: prompts, files and secrets do not go to a remote scanner, and communication uses Unix sockets and a local page on `127.0.0.1`. For names and addresses the installer offers to download the `openai/privacy-filter` weights (about 2.8 GB). The `privacy-hud-doctor` command checks installation consistency.
Who it is for. Codex users on macOS who want to see leaks of personal data and secrets in a live session and block them when needed.
Good fit when
- The agent reads working files with tokens and you need to know where they go.
- The team is unsure which MCP servers receive data from the conversation.
- Before code leaves, you want a hook that strips paths and credentials.
- Per-session disclosure stats are wanted next to token usage.
Not a fit when
- The system is not macOS: the package and installer target Mac.
- You need a guarantee data never left the machine: hooks do not confirm delivery or enforcement of denials.
- You are not ready to replace `codex` launch with a wrapper and a patched build.
Example request
Show the Privacy HUD panel for this session and list confirmed disclosures and recipients.Limitations
The installer creates a virtual environment, installs `torch` and `transformers`, downloads a patched Codex build for your version, puts a `codex` wrapper in `~/.local/bin` and edits `~/.codex/config.toml`. The build is unsigned and not notarized, and SHA-256 protects only against file corruption. Hooks do not confirm that data entered model context, was sent or that a denial was applied, so readings are indicative. Names and addresses need about 3 GB of disk. Linux and Windows are not officially packaged.
How to disable. Run uninstall via the installer manifest and restore the original `codex` command: remove the wrapper from `~/.local/bin` and the `privacy` item from the status line in the config.
FAQ
Does the plugin send data out?
No, processing is local: the scanner uses no remote services, and communication goes through Unix sockets and `127.0.0.1`.
What does the percentage show?
The share of confirmed disclosures. For new sessions it appears only when records support the calculation; otherwise counts are shown.
Must I download the model?
No, but without `openai/privacy-filter` (about 2.8 GB) names and addresses go undetected, leaving only secrets and paths.
How do I verify the install?
With `privacy-hud-doctor`: each line should read `OK` or `WARN`, never `FAIL`.
How do I update after a release?
Rerun the install command. If the bundle does not match, run `codex plugin marketplace upgrade codex-privacy-hud`.
Discussion
No questions or reviews yet.
Related
PluginsAn offline personal-data firewall for agents: a Claude Code hook and a LiteLLM guardrail that mask emails, phones and cards.
Codex Security scans code, validates findings and fixes, saves evidence and exports results for review and CI workflows.
MyPrivacy swaps configured names and company names for aliases in model input and restores the originals before tools run
A marketplace of 22 hook plugins for Claude Code: safety, cost control, observability and automation
A local dashboard for Claude Code, Codex CLI and OpenCode: what the agent loads, its token cost and an MCP server security scan
A Sysdig plugin for Claude Code: cloud onboarding, vulnerabilities, risk analysis and runtime threat investigation.
README in short
Explains the approach to disclosure accounting, the difference between legacy and new accounting, install steps and the hook design.