Before your first session.

The public product repository is still empty. Source publication is pending, and this site does not offer a release binary. The installation page explains the publication status and intended source setup.

Zyphr records coding-agent activity on your machine. Native hooks supply tool events. An optional process-scoped proxy records routed HTTP(S) requests and applies explicit egress rules. The local console joins these records into sessions and findings.

The current implementation has adapters for Claude Code, Cursor, and Pi. Each adapter records the events its agent exposes. Coverage differs by agent. Adding an agent label to a command does not install an adapter.

Other clients may work through the proxy if they honor its proxy and certificate settings. That does not provide native tool events. Read the adapter overview.

The current project is a local engine and console. There is no hosted Zyphr account system or team service to sign up for. Managed deployment and organization policy distribution are later work.

The current source targets Linux and macOS. It uses a Go CLI, a local collector, SQLite, and a browser console. It does not require a separate database server or a cloud account. Check the published source requirements when source becomes available.

No. The local application has no Zyphr telemetry service or automatic remote upload. This website does not connect to your collector. Your coding agent still sends requests to model providers and other destinations.

Website visits pass through Cloudflare. See Privacy for the separate website and application scopes.

No. Prompt and response capture is off by default. Optional content capture uses redaction and encryption. Redaction can miss secrets, and event metadata can still contain sensitive paths or command fragments.

Optional capture encryption does not mean the whole SQLite database is encrypted. Read capture and local data before enabling it.

The proxy uses a runtime-scoped certificate authority for HTTPS inspection. Zyphr does not install that CA in the operating system trust store. A client can reject interception, including through certificate pinning.

Keep existing Lantern data and hooks intact until you follow an explicit migration procedure. The project name changing does not make a directory rename safe. See the Lantern lineage note.

Native hooks observe activity and remain permissive. Findings do not independently veto tool calls. Explicit proxy deny rules can block HTTP(S) requests routed through the proxy.

This is not a sandbox or an operating system security boundary. See the observation and policy model.

Yes. A program can ignore proxy settings or use a network path the proxy does not handle. Code running as your user can also change user-owned hooks, binaries, keys, and records. Policy applies only on the proxy path.

Hook or collector failure must not deny tool execution. The proxy has different failure behavior. An explicit deny blocks a request, setup failure can stop the wrapped command, and transport failure can interrupt a request. Zyphr must not silently retry an uncertain write.

No. A finding points to supporting events and an interpretation. A suspicious sequence is a reason to investigate. A socket connection alone does not prove which plaintext crossed TLS. Missing events do not establish that an action was safe.

No. The homepage session uses synthetic data to explain how records fit together. It is not a product screenshot, live connection, test result, or record of a compromise. The recorder illustration is artwork.