Cortex
◆ Cortex / Atlas / On-device Capture
Atlas · How Cortex captures

Observe supported AI work at the device boundary.

An on-device sensor and local proxy can record supported browser, IDE, provider, harness, and tool signals according to deployment configuration.

  • Deployment-scoped capture coverage
  • A 127.0.0.1 proxy for configured routes
  • Telemetry coverage documented by source
Pairs with Work & Attribution Context & Memory
Cortex · Sensor
Cortex · Sensor
The sensor console

Employees keep their tools. Telemetry follows capture policy.

The endpoint sensor observes supported AI activity locally. Capture policy controls minimization and synchronization to the configured Cortex data plane. The provider request path remains separate.

Cortex Sensor · Console

Cortex Sensor

Running

Local capture for Claude Code, Codex, ChatGPT web, and Claude web. Coverage and minimization depend on the deployed capture configuration.

Checked 16:13:04
Capture healththis Sensor process
Captured
174
4 CLI · 6 browser shown
Uploaded
174
up to date
Upload failures
0
no failed batches
Last capture
16:13:03
just now · Browser

Capture modes

Sensor · CLI · Browser · Upload
CLI CaptureConfigured

Claude Code and Codex are configured to use the local relay.

Browser CaptureEnabled · PAC active

Supported browser AI requests are routed through the local proxy.

UploadUp to date

Reconstructed exchanges are syncing to the capture API.

Local endpoints

loopback only
CLI Relay127.0.0.1:9000Claude Code & Codex base-URL traffic
Browser Proxy127.0.0.1:9001PAC-routed browser CONNECT tunnels
PAC Server127.0.0.1:19090Serves the proxy auto-config to macOS
Status API127.0.0.1:9000/statusLocal status & recent captures
Raw prompt capture · deployment-configured Credential patterns · configurable minimization

See On-device Capture on your own data.

We'll scope it as part of Cortex Atlas on your stack and document the supported capture and telemetry paths.

Talk to the team Explore Atlas