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.

What you need

Windows 10 or 11, macOS 12+, or a current Linux — and Python 3.11 or newer, which the installer offers to fetch if it is missing.

Windows 7 and 8 cannot run Siphrix: Python dropped them several releases ago, and their PowerShell has no irm, so the command below answers “The term 'irm' is not recognized” — an error about PowerShell that says nothing about Siphrix. Stated here because that message would otherwise be somebody's first impression of an audit tool.

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

One question first: company or personal?

The installer asks outright rather than guessing. A wrong guess would either send somebody's records to a console they never chose, or leave a company laptop invisible to the people answerable for it — and the person answering could undo neither.

1Company. You paste a connection code from your console. The machine enrols, and everything on it — agents, editors, browser — reports through that one connection. One code per machine, not per tool.

2Personal. Press Enter. Everything is recorded to your machine only: no account, no network, nothing sent anywhere. You can connect later with siphrix cloud-connect.

Either way, every command afterwards says which one you are in, on its first line. For an audit tool, “who can see this?” should never require opening a config file.

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.

2Shows the plan, then asks once. Three lists: what it will connect on its own, what needs one click from you, and what it found but cannot wire. Nothing changes until you agree.

3Connects what it can. Agent hooks and editor extensions install themselves. Browser extensions cannot — Chrome removed local installs in 2018 because it was the most abused malware vector the browser ever had. That refusal protects you from us exactly as it protects you from malware, so the installer opens the store page and stops.

4Waits, then looks again. After you install the browser extension, press Enter and it links up. This step matters: the bridge learns which extension to admit by reading your browser profile, so without the second look the extension would install, look active, and record nothing.

5Names the gaps. Anything left unwatched is listed by name. A console showing four entries is indistinguishable from a quiet week unless somebody can say what should have produced entries.

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

“siphrix is not recognized”? pip installs the command into a per-user scripts directory that is often not on your PATH — Scripts\ on Windows, ~/.local/bin on Linux. Nothing is wrong with the install; put py -m (or python3 -m) in front instead:

py -m siphrix coverage py -m siphrix doctor py -m siphrix console

The browser and editor pieces

VS Code: install the Siphrix extension from the Marketplace — it bundles the engine and sets itself up.
Chrome / Edge: the Siphrix extension from the Chrome Web Store, then siphrix bridge links it to the engine.
Firefox: the Siphrix add-on, same bridge.
JetBrains IDEs: the Siphrix plugin from the JetBrains Marketplace.

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.