Surfil
Surfil/Products/Core
// surfil core · consumerlive

The install that bootstraps everything else.

Every AI coding agent - Claude Code, Cursor, Codex, Copilot, MCP agents - wants its own config, its own memory file, its own hooks. Run a few of them and you're maintaining a pile of overlapping, drifting setups.

surfil · your control plane
▤ Saved / mo
$412
⛨ Blocked
27
≋ Memory
94%
Savings trendsigned
Trend, last 12 points
rcpt_8f2aepoch 7 · offlineVALID
!AWS key in payloadacme/apiblocked
What it does

The install everything plugs into

Core is the one-time install that sits beside your agents at a single interception point. It consolidates their configuration, bootstraps Weave (Surfil's signed knowledge network), and gives every other Surfil product a shared foundation to plug into.

One install - A single on-device runtime intercepts at one point instead of patching each agent separately.
Consolidation - Merges scattered agent configs into one consistent baseline, without changing how you already work.
Weave bootstrap - Stands up the signed, offline-verifiable knowledge network the rest of Surfil reads and writes.
Included in every plan - Core comes with Starter and every plan above it - it's the foundation, not a funnel. Upgrade only for the products you need.

Proof, not promises

Core produces one metric type on the shared spine: consolidated endpoints per machine. Every paid output is signed (Ed25519) and verifiable offline with no account. Zero-trace: your source never leaves the device.

$ surfil verify rcpt_8f2a
✓ VALID (offline · epoch 7)
In your terminal

Core, as you'd actually see it

~/acme/api - curl -fsSL https://surfil.com/install.sh | sh
$ curl -fsSL https://surfil.com/install.sh | sh
# detecting agents… claude-code, cursor, codex, copilot
interception point established (one layer, byte-exact passthrough)
$ surfil consolidate
# scanning 6 MCP servers across Claude Code + Cursor…
consolidated 6 → 1 endpoint
weave bootstrapped · signed · offline-verifiable
How it works

How Core does it

1Install once; Core detects every supported agent on the machine.
2It establishes the single interception point - passthrough is byte-exact, so provider prefix caches keep hitting.
3Scattered MCP servers and configs are consolidated into one baseline.
4Weave is bootstrapped: a signed knowledge network every other product writes to.
5Uninstall restores every agent config byte-for-byte - zero residue.
Use cases

Where Core earns its place

Agent config sprawl

Four agents, six MCP servers, one machine - Core collapses them into one maintained baseline.

Trying Surfil safely

Install is fully reversible; the clean uninstall is verified byte-exact, so backing out costs nothing.

Foundation for the rest

Cap, Guard and Mind all plug into the interception point Core establishes - one install, not three.

Claude CodeCursorCodexCopilotMCP agents
FAQ

Questions developers ask first

Is Core a separate purchase?

No - Core comes with Starter and every plan above it. It's the foundation the rest of Surfil plugs into, not a trial.

Will it change how my agents behave?

No. Passthrough is byte-exact; the provider prefix hash is preserved and asserted in CI.

What if I uninstall?

Every agent config is restored byte-for-byte and your Weave exports as a portable .surfilpkg.

Works well with

One spine - products compound

Get Core

One install beside every agent. Reversible byte-for-byte.