A session should leave
something you can inspect.

Start with what happened.

A final answer does not show every tool call or network request that led to it. Zyphr records native hook events and requests routed through its optional proxy. It joins those records into sessions you can inspect on your machine.

The source of each record matters. A tool event describes tool activity. A proxy decision describes a request on that path. A finding points to evidence that needs review.

Leave the gaps visible.

Zyphr should make its limits easy to see. Hooks observe activity and remain permissive. Explicit egress rules apply only to HTTP(S) requests routed through the proxy.

Code running as your user can change user-owned records and configuration. It can also bypass the proxy. A useful session record must keep those gaps visible.

From Lantern to Zyphr.

Zyphr succeeds Lantern. It carries forward the work on recording coding-agent activity and adds a session view of hook events, proxy decisions, and local findings.

Hari maintains this independent project at Zyphr Labs. The current work focuses on the local engine and console. Managed fleets and OS-level sensors are later work.

If you used Lantern, keep its data and hooks intact until you follow an explicit migration procedure. A new project name is not a migration.