Surfil
Surfil/Products/Radar
// surfil radar · consumerpartly built

Observability and rewind - metadata only.

When an agent does something unexpected three steps ago, you need to see what happened. But watching agents shouldn't mean shipping your source code to a dashboard.

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
Radar is partly built. Some of what follows ships on a linked device today and the rest does not. Your dashboard marks each capability, and nothing shows a number it has not measured.
What it does

See it. Rewind it.

Radar gives you a timeline of what your agents did and a rewind to any point in it - built entirely from metadata. Your source stays on the device; the dashboard only ever sees what happened, not the code itself.

Action timeline - See every tool call and decision your agents made, in order.
Rewind - Step back to any prior point in a session to understand what changed and why.
Metadata only - Dashboards render events and hashes - never file contents or source.
Zero-trace by design - Nothing Radar shows you required your code to leave the device.

Proof, not promises

Radar produces one metric type on the shared spine: agent actions on a rewindable timeline. 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 dashboard

Radar, as you'd actually see it

hub.surfil.com/radar
14:02:11edit · src/auth/refresh.rs · hash 9c41…
14:02:09tool-call · cargo test (sandboxed)
14:01:47read · 3 files · 18.2k tokens
14:01:32session start · claude-code · repo acme/api
Illustrative Radar timeline - events and hashes only, never file contents.
How it works

How Radar does it

1Radar records every agent event at the interception point - as metadata.
2Events carry names, hashes, timestamps and token counts; never source.
3The timeline renders in the Hub dashboard, per session and per repo.
4Rewind steps you back to any prior point to see what the agent knew and did.
5The same events feed Proof when you need attestations, not just visibility.
Use cases

Where Radar earns its place

Debugging agent behavior

Find the exact step where a session went sideways, and rewind straight to it.

Reviewing before merging

Check what an agent actually did, every tool call in order, before trusting its diff.

Observability without exposure

Give leads visibility into agent activity without any code leaving devices.

Claude CodeCursorCodexCopilotMCP agents
FAQ

Questions developers ask first

Does the dashboard see my code?

No. It renders events, hashes and timestamps. Zero-trace is architectural.

How far back can I rewind?

To any recorded point in a session - the timeline is append-only on-device.

Is this a keylogger for developers?

No - it records agent actions, not your typing, and it's your dashboard, on your account.

Works well with

One spine - products compound

Add Radar to your agents.

Core installs with Starter; Radar plugs into the same interception point - no second layer, no new setup.