HIDEEPrivacy checkpoint for AI agents

How to use Hidee

Quick start

Install Hidee from the download page, then run hidee app. Hidee opens in its own window. Start a session with your AI agent (Claude Code, Gemini CLI, or Codex CLI) in the folder you want it to work in, and use it as you normally would. The practice lesson shows the whole thing with a scripted agent and needs no sign-in.

Hidee starts the agent with one extra setting: a hook that sends each tool call to Hidee before it runs. It also routes the session's connections through Hidee. Your own agent settings do not change, and nothing is checked outside Hidee's sessions. Safe mode, on by default, also puts the agent in a sandbox (for Gemini CLI and Codex CLI, on macOS).

What Hidee checks

StepWhat Hidee does
Reading and editing files in the session folderShows it on the map. No question asked.
Files outside the session folderRuns, and marks it as overreach.
Credential files such as .env or ~/.ssh, and privileged commands such as sudoWaits for you.
Web searches, page fetches, MCP tools, network commands, messagesOrdinary text goes through. Personal, secret, or internal details wait for you.
A command that runs a scriptReads the script, and treats what it sends like any other step.
Any connection the session opensShows where it went. Hosts you forbid are refused.
Traffic to the model providerAlways passes, and shows as its own flow, because the agent sends what it reads there.

Four kinds of risk

Privacy means details about real people: emails, phone numbers, government IDs, health and pay. Security means keys, card numbers, credential files, and privileged commands. Internal means confidentiality markers, private network addresses, and local file paths leaving the computer. Overreach means steps beyond the folder you gave the agent. The counts at the top of the live map add up what each session has done.

Deciding

A waiting step appears in the checkpoint with what it would send and why it stopped. You can send a shorter version with the sensitive parts replaced by placeholders, approve it as written, or reject it. Every choice asks you to confirm, so a slip of the mouse changes nothing. The agent sees the shorter input or the reason for the refusal. A step nobody decides within ten minutes is refused.

Rules

Rules live in ~/.hidee/app/rules.yaml, and Hidee reloads them when the file changes. Each rule names a session ("*" for any), a kind of step, a destination ("*" for any), the kinds of information allowed without asking, and the kinds never allowed. To refuse a host outright:

recipients:
  tracker.example: a tracker
rules:
  - {agent: "*", kind: network, recipient: tracker.example, forbid: [plain]}

What it cannot see

For HTTPS, the network gate sees where a connection goes, not what it carries. Programs that ignore proxy settings or open raw sockets are not covered.

Your data

Hidee keeps its records in ~/.hidee on your computer. The record of each checked step stays there for you to review; the live map is kept in memory only. Hidee has no account and sends nothing to us. It checks for updates only if you said yes, and then only for the version number.