Apollo Research Watcher
by Apollo Research PBC
Runtime monitoring and blocking for Claude Code and Codex: catch dangerous coding-agent actions before they run
Watcher is a runtime monitoring and control system from AI-safety lab Apollo Research that records coding-agent sessions, grades each proposed action with LLM monitors, and blocks or escalates risky ones before they execute. It is for security and platform teams that want developers to run Claude Code or Codex with fewer permission prompts but central guardrails.
Watcher is Apollo Research's commercial product for overseeing AI coding agents, launched February 17, 2026 alongside an integration with Tailscale's Aperture AI gateway. Apollo Research, a public-benefit corporation known for evaluating frontier models for scheming and deception, built Watcher to turn its monitoring research into production security. A lightweight client installs hooks into Claude Code and OpenAI's Codex (remote Claude Code sessions are covered through Claude Tag), records every session and trajectory, and routes each proposed tool call through a staged blocking-review pipeline: deterministic always-allow and always-deny thresholds and command rules first, then a cheap triage grader that can only approve, then a deep-review LLM grader that scores risk from 1 to 10, and finally human escalation. Calls are allowed, denied or held for approval, and a separate asynchronous trailing review grades whole trajectories for cross-turn problems such as a wrong diagnosis. Apollo says it detects more than twenty failure modes, including instruction violations, deception, dangerous code execution, data deletion and actions exceeding instructions, and claims 100% recall on critical-severity failures with under 1% false positives on benign tool calls, at an estimated 3-5% added cost and 6-8% added latency. It runs as a cloud service hosted in Western Europe or self-hosted on the customer's own infrastructure with bundled AWS Terraform, customer-supplied LLM keys and no phone-home telemetry. Apollo reports monitoring billions of agent tokens a month at agent-building scale-ups, trading firms and multinational enterprises; pricing is not published.
CISO or application-security lead at a company rolling out Claude Code or Codex who needs guardrails without drowning developers in permission prompts
Risky agent actions are blocked or escalated before they run, with a full, auditable record of every coding-agent session
At a Glance
- Category
- Governance & Security
- Pricing
- Contact for pricing
- Target Market
- CISOs, CTOs, Platform Engineering Teams, Application Security Teams
- Deployment
- Cloud-first, Self-hosted
Key Features
- ✓Blocking review
Gates each proposed tool call before execution through rules, a triage grader, deep LLM review and optional human approval.
- ✓Trailing review
Asynchronously grades whole session trajectories for cross-turn problems and surfaces findings in the Analyzer without slowing the agent down.
- ✓Custom graders
Versioned LLM grading rubrics with score dimensions; teams can build their own graders and roll them out for live blocking or on-demand grading.
- ✓Analyzer dashboard and Slack alerts
Investigate sessions, review security decisions, manage monitors and organisation settings, and push grading findings to Slack for fast response.
- ✓Self-hosted deployment
Run the backend on your own infrastructure with bundled AWS Terraform, your own Postgres and LLM keys, and no telemetry sent to Apollo.
- ✓Fleet rollout via MDM and containers
Deploy the client to managed Macs, shared VM images and dev containers with MDM scripts, headless sign-in and organisation API keys.
- ✓Python SDK and HTTP API
Programmatic ingest, grading and session queries let teams feed Watcher from custom agents or pipe results into existing security tooling.
Capabilities
Use Cases
- •Safer auto-approval for coding agents
Engineering organisations let Claude Code run with fewer permission prompts while Watcher blocks destructive commands and escalates risky calls to a human.
- •Preventing data leakage
Security teams catch agents attempting to send private code or data to outside destinations and stop the tool call before it executes.
- •Incident investigation
When an agent deletes files or breaks a build, teams replay the recorded trajectory in the Analyzer to see exactly what happened and why.
- •Org-wide agent visibility
Paired with Tailscale Aperture's identity-linked gateway logs, security leaders get high-level summaries of agent behaviour while developers see real-time detail.
- •Self-hosted monitoring for regulated firms
Trading firms and enterprises keep full agent transcripts, including source code, inside their own network by running the self-hosted deployment.
Ideal For
Best For
- ✓Security teams governing Claude Code and Codex use across engineering
- ✓Enabling agent auto-approval without giving up guardrails
- ✓Forensic review of what coding agents actually did in a session
- ✓Organisations that must keep agent transcripts on their own infrastructure
Not Ideal For
- ✗Teams standardised on Cursor, GitHub Copilot, Windsurf or Gemini CLI: the docs list only Claude Code and Codex as supported agents
- ✗Buyers who need published pricing or third-party compliance attestations up front: neither the product site nor the security docs list SOC 2 or ISO certifications or prices
- ✗Latency-sensitive agent workflows where Apollo's own estimate of 6-8% added latency is unacceptable
Integrations
Deployment
Market Analysis
Pros
- ✓Built by a respected AI-safety evaluation lab with published monitoring research
- ✓Layered pipeline puts cheap deterministic checks in front of expensive LLM review, limiting cost and latency
- ✓Self-hosted option with no telemetry and bring-your-own model keys
- ✓Human escalation and anti-loop protections instead of silent repeated denials
Cons
- ✗Narrow agent coverage: only Claude Code and Codex, plus remote Claude Code via Claude Tag
- ✗Codex sessions running under an approval policy that asks about nothing send Watcher no requests, so review can be bypassed by configuration
- ✗Using LLMs to monitor LLMs invites an arms race; TechCrunch notes a malicious model might trick the monitor
- ✗Stores full transcripts including source code and any secrets, retained indefinitely by default unless a retention policy is set, and no compliance certifications are documented
Pricing
Watcher (cloud or self-hosted)
Contact for pricing
- ✓Claude Code and Codex monitoring
- ✓Blocking and trailing review
- ✓Cloud hosted in Western Europe or self-hosted
Apollo Research does not publish list pricing; access is arranged by contacting the company, and the February 2026 launch was offered as early access on request. Apollo estimates monitoring adds 3-5% to agent running cost, and self-hosted deployments also carry their own LLM provider bills because the graders run on customer-supplied API keys for OpenAI, Anthropic and Google models.
Security & Compliance
Connect
Sources
This page was written from 8 sources, 7 on domains other than watcher.apolloresearch.ai.
- 1.watcher.apolloresearch.ai — watcher.apolloresearch.aivendor
- 2.watcher-docs.apolloresearch.ai — blocking and trailing review.md
- 3.watcher-docs.apolloresearch.ai — security.md
- 4.watcher-docs.apolloresearch.ai — supported agents.md
- 5.apolloresearch.ai — introducing watcher for ai oversight
- 6.techcrunch.com — the fix for rogue ai agents could be more ai
- 7.tailscale.com — aperture partners update
- 8.siliconangle.com — secure networking startup tailscale launches identity linked
Stay Ahead of the Curve
Weekly enterprise AI insights for technology leaders. No spam, no vendor pitches—unsubscribe anytime.
SubscribeRelated Products
Comp AI
Open-source, agentic compliance automation for SOC 2, ISO 27001, HIPAA and GDPR: an AGPL alternative to Vanta and Drata
Mate Security
Open agentic SOC platform powered by a security context graph built for each organisation
Cymphony
Workforce security graph that maps what employees and AI agents can reach, then remediates the exposure
MintMCP
Enterprise MCP gateway that gives every AI agent its own identity, scoped tools and audit trail