zyphr

A paper trail for
your coding agent.

See which tools ran, where proxied requests went, and which proxy rules applied. Zyphr keeps the session on your machine.

Source statusSee an example

Local by design. Source release in preparation.

ASCII illustration of a small recorder printing a paper trail.

For Claude Code, Cursor & Pi.

Hooks observe. Proxy rules cover routed HTTP(S) only. Same-user code can bypass or alter the record.

Follow a request through the session.

Your agent read a file, then made a request.
Zyphr records both, with their sources.

01 / Session recordSample session · Synthetic data
SESSION / sample-07c2

Review a config change

Adapter
Claude Code
Hook mode
Observe
Prompt capture
Off
Storage
Local SQLite
Local timeObserved eventSource
  1. Session openedNative session recorded
    Hook
  2. Readsrc/config.ts
    Hook
  3. Request allowedregistry.npmjs.org
    Proxy
  4. Request deniedingest.example.invalid
    Proxy
  5. Local findingPolicy denial with request evidence
    Analysis
End of sampleFindings do not block tool execution.

The tool call.
The request.
The evidence.

A tool call, a network request, and a security finding tell you different things. Zyphr keeps their sources attached.

Start with what ran.

Native hooks record session and tool events from Claude Code, Cursor, and Pi. They stay permissive: collector failures do not stop the agent's tools.

Adapter behavior

Put requests under a rule.

The optional HTTP(S) proxy applies explicit allow and deny policies to routed traffic. A request outside that path is a coverage gap, not an inspected request.

How proxy policy works

Open the record locally.

Review events, findings, and their evidence in the local console. Local SQLite stores the session history, not a hosted Zyphr service.

Run the local console

Know what
can go missing.

Code running as your user can modify hooks, binaries, keys, and local data. It can bypass an optional proxy. Zyphr gives you visibility within that boundary.

Prompt capture is off by default. Optional capture is redacted and encrypted, but redaction can miss a secret.

Read the security model

Start with the source.

Zyphr is under active development. Public source publication is still in preparation. The setup notes explain what you will need once it is available.

Installation and first run
git clone https://github.com/zyphr-labs/zyphr.git
cd zyphr
go build -o bin/zyphr ./cmd/zyphr

Planned setup after source publication. Requires Git and Go. Check source status.