Surfil
// integration

Surfil sits under Codex, one adapter deep

The same single Surfil adapter sits under Codex - same signed outputs, same byte-exact passthrough, and no second proxy added to the path you already run.

Install for CodexAll integrations →
surfil · one interception point
Claude CodeCursorCodex · Copilot
↓
◈ interceptor
↓
1. security2. cost3. quality4. observability5. memory
↓
≋ one signed Weave spine
Where it sits

One layer in your stack

One adapter under Codex, on your device - the same interception point every other agent uses, never a stacked second layer.

youCodex
↓
surfilSurfil · one on-device interception point
↓
providerModel provider · byte-exact passthrough
ⓘ One interception point, on your device. Surfil never chains a second proxy in front of Codex, and passthrough to the provider is byte-exact.
What you get

What you get

One adapter, all products

Cap, Guard and Mind attach to Codex through the same single point - adding capability never adds a hop.

Signed outputs

Every paid output from Codex through Surfil is Ed25519-signed and verifiable offline, with no account.

No second proxy

Surfil is the one interception layer; it never chains another proxy in front of Codex to sell you more.

Setup

Add Surfil to Codex

Three steps, no config rewrite, reversible byte-for-byte.

1Install Surfil; the same adapter that serves your other agents picks up Codex too, automatically.
2Run normally for a week - Cap measures the recoverable spend and signs your first receipt from it.
3Move Guard from monitor to enforce once the report shows the block-list is safe for your work.
Install for CodexRead the docs →
What holds

Why it fits Codex

One layer, not many

Every product is a stage on the same stream, so Codex never gets a second interception point stacked on.

Prefix cache preserved

Passthrough keeps the provider prefix hash byte-exact, so Codex's cache keeps hitting - asserted in CI.

Reversible byte-for-byte

A clean uninstall restores every Codex config exactly, so backing out costs you nothing.

Works with

Every agent, the same layer

One adapter per agent, all on the same on-device interception point.

Claude Code

Between Claude Code and your model provider, on your device - one interception point, never a second proxy stacked into the path.

See adapter →

Cursor

At Cursor's MCP layer on your device: one endpoint for its MCP servers today, with full-traffic interception on the roadmap via the network layer.

See adapter →

Copilot

Beside Copilot on your device: detected, with its MCP connected where a host exposes it. Its GitHub-proxied completions are not redirectable today.

See adapter →

MCP agents

In front of your MCP servers on your device, collapsing many endpoints into one interception point you can meter and govern.

See adapter →

Add Surfil to Codex

Core installs beside the agents you already run, byte-exact, and the first signed receipt arrives after one normal week of traffic.

Install for CodexAll integrations