Get started
AgentPing protects each computer where people use AI. Getting a team going takes three steps.
- Create your organisation. Ask us for a workspace (the first 5 seats are free). Its first admin gets an email invitation and signs in to the console.
- Invite people. In the console, open Settings › People and invite each person as a Device user (their computer only), Analyst (read-only console) or Admin.
- Install on each computer and sign in with the organisation's name. Protection starts at once; findings appear in the console within minutes.
Until a computer signs in, AgentPing still protects it locally. Nothing is shared with anyone.
Install
The installer adds the AgentPing engine and menu bar app, then connects every supported AI tool it finds on the computer.
$ curl -fsSL https://github.com/madsquarebs/homebrew-agentping/releases/latest/download/install.sh | sh
$ brew install --cask madsquarebs/agentping/agentping
# PowerShell
PS> irm https://github.com/madsquarebs/homebrew-agentping/releases/latest/download/install.ps1 | iex
The installer runs agentping setup, which turns on everything below: hooks for each coding agent found, the LLM proxy, the browser extension's connection and MCP protection. Run it again any time; agentping setup --remove undoes it.
Rolling out to many computers? Use your device management (Jamf, Intune, Kandji, Group Policy) to run the installer. agentping browser policy writes the browser policy that installs the extension on managed computers.
Sign in a computer
In the AgentPing menu bar app, enter your organisation's name and press Continue. The browser opens your organisation's sign-in (password, Google, Microsoft or your company's single sign-on). Check the code matches the one in the app and press Connect this computer.
From a terminal:
$ agentping login --server https://app.agentping.dev --org "Your company" Opening your browser to sign in to AgentPing. Sign in to Your company. Check the page shows code BCDF-GHJK, then press Connect. Connected to Your company.
The computer joins as yours and takes your seat. Your organisation's policy applies from the next sync. agentping logout or Sign out in the app disconnects it; protection carries on locally.
Coding agents
AgentPing connects to each coding agent through its official hooks, so it sees prompts, files the agent opens, shell commands and tool results before they're sent.
| Agent | Where | What's checked |
|---|---|---|
| Claude Code | Terminal, VS Code, JetBrains | Prompts, file reads, searches, shell commands, edits, MCP calls, tool output |
| OpenAI Codex | CLI | Prompts, shell commands, tool output |
| Cursor | Editor | Prompts and attachments, file reads, shell commands, MCP calls |
| GitHub Copilot | VS Code agent mode, Copilot CLI | Prompts with attached context, tool calls, tool output |
$ agentping hooks install --agent auto # every agent found (setup does this) $ agentping hooks status # what's connected
When an agent tries to read a sensitive file such as .env, cloud credentials or an SSH key, the read is stopped and the agent is told why. If it runs a command that prints a file (cat, head, grep, jq…), the file is checked first, the same way.
LLM proxy
Hooks can stop a send but can't always rewrite it. The local proxy can: agents' requests to the model go through it, and sensitive values are replaced with placeholders like «REDACTED:aws_access_key_id:3f2a» so the agent keeps working. It also measures token usage and cost for the console.
$ agentping proxy service install # starts at login, for every app (setup does this) $ agentping proxy env # the variables, for a single shell export ANTHROPIC_BASE_URL=http://127.0.0.1:8787/anthropic export OPENAI_BASE_URL=http://127.0.0.1:8787/openai/v1
Restart editors and terminals after installing so they pick up the proxy. Your company already has an LLM gateway? Point the proxy at it with --upstream anthropic=https://gateway.example.com.
Browser
The AgentPing extension checks what people type, paste and upload in AI chats before the page sends it. Sensitive values are replaced in the message box, uploads are cleaned (values blacked out) or stopped, and the person sees a short banner saying what happened.
- Browsers: Chrome, Edge, Brave, Arc, Opera, Vivaldi and Firefox.
- Sites: ChatGPT, Claude, Gemini, Microsoft Copilot, Perplexity, DeepSeek and Grok.
- Uploads: text, CSV, PDF, Office documents, archives and images (screenshots are read with on-device text recognition).
$ agentping browser install # connect the extension to the engine (setup does this)
$ agentping browser status
The extension never sends text anywhere but to the AgentPing engine on the same computer.
MCP servers
AgentPing wraps the MCP servers your agents use, local and remote, so tool calls carrying secrets or personal data are cleaned before they reach the server.
$ agentping mcp install --include-remote $ agentping mcp status
Files and screenshots
Files are inspected wherever they're sent: uploads in the browser, files a coding agent opens, attachments. AgentPing extracts the text of PDFs, Word, Excel and PowerPoint documents and archives, and reads images and scanned PDFs with the operating system's own text recognition (macOS Vision, Windows OCR), on the device.
When a file holds something sensitive, AgentPing sends a cleaned copy with the values blacked out, or stops the upload if your policy says so. Files it can't read (encrypted, too large) can be blocked or let through with a warning.
What's detected
| Kind | Examples | Default |
|---|---|---|
| Secrets | Cloud keys (AWS, Azure, Google Cloud), GitHub, GitLab, Slack, Stripe, OpenAI and Anthropic keys; private keys; passwords in text; database connection strings; 140+ formats | Replaced |
| Payment cards | Card numbers (checksum-validated) | Replaced |
| Identity numbers | US SSN, Aadhaar, PAN, passports, driving licences, national IDs and tax numbers from 40+ countries (checksum-validated) | Replaced |
| Personal data | Email addresses, phone numbers, IBANs | Warned |
| Sensitive files | .env, cloud credentials, SSH keys, production configs, keystores | Read stopped |
| Agent mistakes | Packages that don't exist, versions that were never published, unbacked claims | Blocked |
agentping rules lists every detector on a computer.
Policies
A policy says what happens to each kind of finding: allow, audit, warn, redact (replace) or block. The defaults replace secrets, card numbers and ID numbers, warn about other personal data, and block agent mistakes.
Organisation policy
Admins edit the policy in the console under Policies: a form for the common choices and YAML for the rest. Simulate replays recent findings under the draft before anyone is affected. Published policies reach computers at their next sync and keep working offline.
mode: enforce # monitor: record only · warn: tell, don't stop · enforce standard: sensitive_data: redact # or block: stop the send instead of replacing policy: rules: - match: { category: pii, surface: prompt.browser } action: block # no personal data in browser chats
Per repository
A repository can be stricter with .agentping.yml at its root, in the same format. The organisation's policy is a floor: each finding gets the stricter of the two actions.
New organisations often start in monitor mode for a week to see what would be stopped, then switch to enforce.
Console
| Page | What it's for |
|---|---|
| Overview | Findings by severity, what was prevented, coverage, agents in use, spend |
| Findings | Every finding with its risk and outcome; filter by severity, status, project or device; triage |
| Projects and devices | Findings, AI requests and cost per project (browser chats are “Browser”) and per device, with whose computer it is |
| Coverage | Which computers are protected, which agents are connected, which run an old policy |
| Agent quality | Agent mistakes and how often agents correct themselves |
| Policies | Edit, simulate and publish the organisation policy |
| Usage and cost | Requests, tokens and cost by model and day |
| Audit log | Every change by admins and AgentPing staff |
| Settings | People, single sign-on, alerts to Slack and API keys |
People and sign-in
People sign in with their work account: password, Google, Microsoft, passwordless codes or your company's single sign-on, with multi-factor sign-in and password reset built in.
| Role | Console | Computer |
|---|---|---|
| Admin | Everything, including policies, devices and people | If they sign one in |
| Analyst | Read only: findings, devices and reports | If they sign one in |
| Device user | No console | Yes (takes a seat) |
Single sign-on and directory sync: in Settings › Single sign-on and directory, your IT team connects Okta, Microsoft Entra ID, Google Workspace or any SAML/OIDC provider, and your user directory (SCIM) so joiners and leavers are added and removed automatically. Each opens a guided setup.
API keys (Settings) are for scripts and integrations, such as pulling findings into a SIEM. They can't sign in to the console.
Scanning in CI
The same detectors can check a repository before code is merged:
$ agentping scan --fail-on restricted .
config/settings.py:12 AWS access key ID (restricted)
1 finding · exit code 1
--json gives machine-readable output; --fail-on confidential is stricter, none only reports.
Command line
| Command | What it does |
|---|---|
agentping setup | Turn on every integration found (the installer runs it) |
agentping login --server URL --org NAME | Sign this computer in to your organisation |
agentping logout | Sign out; local protection carries on |
agentping status | Protection, connection and policy on this computer |
agentping dashboard | This computer's own dashboard (a local page, no sign-in) |
agentping activity -f | Follow what's being checked, live |
agentping findings | Recent findings on this computer |
agentping hooks install|status | Coding agent hooks |
agentping proxy service install | The LLM proxy, at login |
agentping browser install|status | The browser extension's connection |
agentping mcp install|status | MCP server protection |
agentping scan PATH | Check files and folders |
agentping usage --days 30 | Tokens and cost on this computer |
agentping doctor | Find and explain problems |
agentping update | Install the latest signed release |
Self-hosting
Enterprise self-hosted runs the console and API in your own cloud. It's one container plus Postgres 16 or later; database migrations run when it starts. Contact sales for a licence.
$ AGENTPING_TOKEN_KEY=$(openssl rand -hex 32) docker compose up -d
| Setting | Purpose |
|---|---|
DATABASE_URL | Postgres connection. Each workspace's rows are isolated with row-level security. |
AGENTPING_TOKEN_KEY | Random secret that signs device tokens |
AGENTPING_PUBLIC_URL | The service's https address, as computers and browsers reach it |
AGENTPING_RETENTION_DAYS | How long events and findings are kept (default 365) |
WORKOS_CLIENT_ID, WORKOS_API_KEY | Sign-in, single sign-on and directory sync |
Run the image's maintain command daily: it prepares storage, applies retention and clears expired sessions. Computers then sign in with --server set to your address.
Troubleshooting
- Something isn't protected: run
agentping doctor; it lists what's missing and how to fix it. - Claude Code blocks instead of replacing: it isn't using the proxy yet. Restart the editor or terminal after setup.
- A finding is wrong: mark it False positive in the console; detectors are tuned from these.
- “No organisation called …”: check the name with your admin; it's shown in the console under Settings.
- Still stuck? Email support@agentping.dev.