Install Siphrix

One command, on a machine enrolled with your organisation's console. It senses what is on the 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. On Windows fleets the installer brings its own Python; on other machines you need Python 3.11 or newer.

Windows fleets

Siphrix arrives through your organisation's IT: one installer, deployed with Intune or the management tool your fleet already uses. It brings its own Python, installs offline from a bundled wheelhouse, and asks for exactly one thing — the connection code below. No administrator rights, no system service, nothing written outside the user's own profile.

The installer is not yet Authenticode-signed. SmartScreen will warn on first run, and on a locked-down fleet it may be refused outright until an administrator allows it. The certificate is bought rather than built, and this paragraph goes away the day it arrives. We would rather you read that here than discover it on the machine you were about to deploy to.

A machine that already has the engine

Provisioned machines connect with one command:

siphrix set-up --code <connection code> --server <console url>

The old install.ps1 / install.sh one-liners were retired at 2.0.0 — the URLs still answer, and say so themselves. Self-serve installation ended when the licence changed; versions 1.8.9 and earlier remain MIT on PyPI, permanently.

One thing first: a connection code

Siphrix installs on machines enrolled with your organisation's console. Set-up asks for the code outright rather than guessing, because a company laptop recording to nowhere — or to a console nobody chose — is exactly the kind of quiet gap this product exists to prevent, and the person answering for that laptop could undo neither.

1Get a code. Whoever runs your console creates one on its Surfaces screen. One code per machine, not per tool.

2Paste it when set-up asks. The machine enrols, and everything on it — agents, editors, browser — reports through that one connection. A machine installed before its code existed connects later with siphrix cloud-connect.

Every command afterwards names the console this machine reports to, 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

Set-up normally does this for you. If a machine was installed before its code existed — or your organisation self-hosts its console, which is part of the commercial licence — connect it 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. Its popup asks for nothing: on a computer already running Siphrix it works out which machine it is on and joins that record.
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.