Pick your setup
Find the tool you use in the table. Each row links to a step-by-step page.
| I use… | Use | Page |
|---|---|---|
| Claude Code (terminal, desktop or IDE) | Hooks, plus the gateway if you want tool output covered | Claude Code |
| GitHub Copilot CLI or agent mode | Hook | GitHub Copilot |
| Copilot Chat in VS Code with my own API key | Gateway | GitHub Copilot |
| Cursor, Continue, Aider, Codex CLI | Gateway | Other AI apps and SDKs |
| My own script using the OpenAI, Anthropic or Gemini SDK | Gateway | Other AI apps and SDKs |
| A file or some text I want to clean by hand | Command line | Clean a file or some text |
| ChatGPT.com, claude.ai or other websites and phone apps | Not supported | See below |
Why websites and phone apps are not covered
pii-airlock works by changing where a program sends its requests. Websites and mobile apps give you no setting for that. For those, use Clean a file or some text before you paste.
Gateway or hooks: which one?
Gateway means your tool talks to a local address, and pii-airlock swaps placeholders in and out automatically. Nothing to approve, nothing interrupts you. It works with any tool that lets you set a "base URL".
Hooks are checkpoints inside Claude Code and Copilot. When something personal is about to be sent, they stop and tell you, and you decide. They do not rewrite anything.
If you use Claude Code a lot, many people use hooks as the everyday safety net. The gateway is the better pick when you want everything handled silently, or when the tool has no hook system.
One thing to know before you start
None of these setups makes detection perfect. Read Safety and limits once.