Skip to main content
JD Codec sits between your AI agent and the browser it’s automating. It compresses each DOM/ARIA snapshot the agent sees, sending the smallest possible representation while keeping every reference your agent needs to act. Token cost drops, accuracy holds.

​
How it works in 30 seconds

  1. Install the local connector (npm install -g jdcodec or pip install jdcodec).
  2. Wire it to your AI agent as an MCP server (claude mcp add --scope user jdcodec -- jdcodec).
  3. Run your agent normally. The connector intercepts browser snapshots, redacts PII on-device, sends the rest to the JD Codec cloud, splices the compressed output into the agent’s tool response.
Your agent sees only what changed since the last step. Your customers’ PII never leaves the local machine.

​
Where to next

Quickstart

Install, configure, and see your first compression event in under 5 minutes.

API Reference

Endpoints, schemas, error codes — everything the connector talks to.

What is JD Codec?

The codec, the connector, the cloud — what each piece does.

Privacy posture

What stays local, what reaches the cloud, what’s never persisted.