These docs are in English. If you prefer German, write us at beta@clickprobe.ai.

Updating the ClickProbe Proxy

clickprobe-proxy is a binary you install and run on your own machine — it does not auto-update. This page covers how to check your version, how to update on each platform, what the staleness notice means when you see one, and how to turn the check off.

Check your version

clickprobe-proxy status

Prints version, commit, and build date, plus (if you’re behind) a one-line notice naming the newer version and where to get it. clickprobe-proxy status --json carries the same three fields as version/commit/build_date, plus update_available/latest_version.

The local dashboard (clickprobe-proxy webui, http://127.0.0.1:9100) shows the same notice as a banner at the top of the page when a newer version is published.

How the check works

Once at startup and on every status call, the proxy makes a single, plain, unauthenticated GET request to clickprobe.ai/downloads/latest/VERSION and compares the version there to yours. That request carries no account id, no token, no machine label, and no session id — it can’t be linked to you or your account. It’s bounded by a 5-second timeout, never blocks startup, and is silent if the network is unreachable or the check otherwise fails (no error, no retry storm — it just tries again next time). See the outbound hosts table if you’re pre-approving destinations in a change request.

Turn it off:

export CLICKPROBE_DISABLE_UPDATE_CHECK=1

Set this in your shell profile or the environment your service manager uses (systemctl --user edit clickprobe-proxy, or the equivalent for launchd/Windows Service) to disable it permanently.

Update

macOS / Linux — re-run the installer; it always fetches the current latest/ build:

curl -fsSL https://clickprobe.ai/install.sh | bash

Windows (PowerShell):

irm https://clickprobe.ai/install.ps1 | iex

Linux .deb/.rpm — if you installed via package manager rather than the shell installer, download the current package from clickprobe.ai/downloads/latest/ and install it the same way you did the first time (apt install ./clickprobe-proxy-linux-amd64.deb or dnf install ./clickprobe-proxy-linux-amd64.rpm) — it upgrades in place.

If you’re running as a service (clickprobe-proxy install --service), restart it after updating so the new binary actually takes over:

systemctl --user restart clickprobe-proxy   # Linux

(macOS/Windows service restart: see the Onboarding Guide for the equivalent for your platform’s service manager.)

A stale proxy still works

A version behind latest/ is not blocked from connecting or running sessions — the staleness check only ever informs, it never gates. You won’t lose functionality by waiting to update; you may miss fixes and new capabilities that shipped since your version, which is exactly what the notice is telling you.