Document the privacycommand CLI and how to install it

[adamXbot]

Why

The CLI was renamed from auditctl to privacycommand and now ships inside the app (privacykey/privacycommand#28). These docs still said it isn't in the DMG and had to be built and run with swift run -c release auditctl.

What changes

• auditctl.mdx → cli.mdx ("Command line"). A redirects entry in docs.json sends /auditctl to /cli. The page now covers:

  • Homebrew: the cask links the tool, so there's nothing to do.
  • Disk image: privacycommand ▸ Install Command Line Tool… links it into /usr/local/bin. That covers the sudo command it offers when the folder isn't writable, the Uninstall item, and what it refuses to touch.
  • Build from source, for contributors and for 0.1.5 and earlier. v0.1.5 predates the embedded tool, so the page says it arrives with the first release after 0.1.5.
  • Usage, flags and preview, all with the new name, plus a new table of audit exit codes (0/1/2/4, checked against AuditCommand.swift).

• Cross-references. Introduction, Reports, Security, Compare runs, Batch scan, FAQ and About these docs link /cli and use privacycommand ….

• Tab completion (second commit): cli.mdx gains a section on privacycommand completion <zsh|bash|fish>, covering what completes, that Homebrew sets it up, and the one line per shell otherwise. Troubleshooting gains a zsh entry (compinit order, Homebrew's fpath, a stale ~/.zcompdump). This documents privacykey/privacycommand#29, so merge that before the next app release, or hold this section back.

• Installation gets a short "Command-line tool" section.

• Updating notes that --version matches the app and that the tool updates with it.

• Troubleshooting renames its section to "Command line" and adds two entries: "command not found" and "asks you to move the app".

• Develop pages use the new target names (privacycommandCLI / privacycommandCLIKit), .build/debug/privacycommand, and mention the Embed command-line tool build phase.

• llms.txt / llms-full.txt are regenerated.

• upgrade, --max-risk, --greedy and .pkg (third commit, after merging main). The CLI on privacycommand main gained these, so cli.mdx's ".pkg is skipped" and "will not upgrade anything" were out of date. The page now covers:

  • preview's new flags and the casks and formulae it lists but can't analyse.
  • the brew calls it makes, and exit code 3.
  • how .pkg artifacts are expanded with pkgutil.
  • a new Upgrading within a risk limit section: cleared versus held, --dry-run, --no-input, exit codes 0/1/2/3, and the daily alias. All checked against privacycommand upgrade --help and the code.

  Security lists brew upgrade as the sixth outbound call, and the Introduction and FAQ follow.

Checks

• npm run check: docs check (29 linked files) and llms check pass.
• npm run linkcheck (lychee): 0 errors.
• npx mint broken-links: no broken links.

Not changed, but stale

Three pages say macOS 13: installation, introduction and FAQ. The app's deployment target is 14.0, and build-from-source says "deployment target is macOS 13.0". Installation also points at Help → Show Onboarding…, which the new shared Help menu replaced with Welcome to privacycommand. I left these for a separate pass.

🤖 Generated with Claude Code

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	docs-privacycommand	44a16fc	Commit Preview URL Branch Preview URL	Oct 09 2026, 02:10 AM