Install Siphrix

One command. It senses what is on your machine — coding agents, editors, browsers, local models — and offers to record each one. Nothing connects without asking you first.

Windows

Open PowerShell and run:

irm https://siphrix.com/install.ps1 | iex

Piping a script from the internet deserves suspicion — so open it first. It is short, plain text, and does three things: checks Python 3.11+, installs the siphrix package from PyPI, runs siphrix set-up.

macOS / Linux

curl -fsSL https://siphrix.com/install.sh | sh

Same three steps, same advice: read it first.

Already have Python? Skip the script

pip install siphrix siphrix set-up

What set-up actually does

1Senses. Looks for Claude Code, Codex, VS Code, JetBrains IDEs, Chrome/Edge/Firefox, and local model servers (Ollama, LM Studio, vLLM…). Passive — it reads the PATH and asks loopback ports, nothing more.
2Asks. For each surface it found: connect it, or skip it. Skipping is remembered and respected.
3Records. From then on, every agent action on a connected surface is written down — action, app, verdict, time. Never file contents, never message text.

Connect this machine to a console

One machine works alone. A team connects each machine to a console — this site, or one you host — with a single token:

siphrix cloud-connect https://siphrix.com <your-device-token>

The token comes from your console's Surfaces screen. One token per machine; each machine signs what it sends with a key that never leaves it, so the console can prove — not just claim — which machine every entry came from.

Check yourself

siphrix coverage # what is recorded on this machine, and what is not siphrix doctor # is the install healthy, can this machine sign siphrix console # open the local console

The browser and editor pieces

Uninstall

pip uninstall siphrix

Your record stays in ~/.siphrix — it is yours, so removing the software does not delete the evidence. Delete that folder yourself if you want it gone.