One file. Nothing to install first.
This page is the helper, an optional companion program. It is not webQsee itself: the extension comes from the Chrome and Edge stores, and an existing report opens in a browser tab with nothing installed at all. You need the helper for Deep Inspection and for reaching your recordings from your own agent. Everything else, the quick AI analysis included, works without it.
Looking up the current release…
Three ways to run webQsee. This page is the third.
Most people never need the helper. It is worth thirty seconds to check which of these you are actually after.
The extension
This is webQsee itself: recording a tab with its network traffic and console, replay, the analyzer, screenshots. Free, and no account needed for most of it. It installs from your browser's own store, not from here.
webQsee in a browser tab
Somebody sent you a report or a snapshot and you only want to read it? Open it at view.webqsee.com, replay it, search it and export it, with no extension and no download. Capturing a new recording is the one thing it cannot do.
The helper
A small program on your own machine, for two things only: Deep Inspection, which runs an agent locally against a recording, and pointing your own agent at your recordings. It carries its own runtime and needs no administrator rights.
Available now in the browser, and in the extension this autumn.
The AI analysis, the three webQsee AI strengths, Deep Inspection and the new plans are live today in webQsee web at view.webqsee.com: open a recording there, analyse it, and buy a plan or a booster if you want one. The Chrome and Edge extensions are in review and follow this autumn. Your recordings, your gallery and your account are the same in both, so nothing you do now has to be done again.
Pick the file for your machine.
Each archive contains the binary, the installer scripts, the documentation and a SHA256SUMS file. File names carry their version, so an older download keeps working and its link never breaks.
Windows Intel / AMD
64-bit x64. The usual choice on a Windows PC.
wqs-helper-<version>-win32-x64.zip
Windows ARM
Snapdragon and other ARM64 Windows machines.
wqs-helper-<version>-win32-arm64.zip
macOS Apple silicon
M1 and later. "Apple M..." under About This Mac.
wqs-helper-<version>-darwin-arm64.tar.gz
macOS Intel
Pre-2020 Macs. "Intel" under About This Mac.
wqs-helper-<version>-darwin-x64.tar.gz
Linux Intel / AMD
64-bit x64. uname -m says x86_64.
wqs-helper-<version>-linux-x64.tar.gz
Already have it?
Run wqs-helper update and it fetches release-manifest.json from this directory, compares versions and replaces itself. You never need to come back here for an upgrade.
Three steps, then it is done.
1 · Unpack and run the installer
install.cmd on Windows, ./install.sh everywhere else. It needs no administrator rights and writes only inside your user account.
2 · Restart the browser
This is the step everyone skips. The browser reads the helper's registration when it starts, so until you restart it, webQsee will keep saying the helper is not reachable.
3 · Check it
wqs-helper doctor reports what is registered and what is missing. In webQsee, Deep Inspection stops being greyed out.
Every step with what you should see after it, and the part only webQsee in a browser tab needs: starting the helper yourself, pasting its token and allowing the browser's one-time question.
Your system will ask before it runs this
These builds are not code-signed yet. Chrome or Edge may hold the download back as suspicious or "not commonly downloaded" (keep it from the browser's download list), and each operating system shows its own confirmation: SmartScreen on Windows ("More info", then "Run anyway"), Gatekeeper on macOS (open it once from the Finder context menu, or clear the quarantine attribute), and nothing at all on Linux beyond making the file executable. The SHA-256 on each card confirms the file is the one published here.
How the pieces connect.
Everything stays on your computer. Only the link from webQsee depends on whether you use the extension or webQsee in a browser tab; every agent reaches the helper the same way, which is why the line that registers one never differs between the two.
webQsee differs by variant
127.0.0.1:48621 with the token you paste once, after your browser allows it; you start the helper with wqs-helper start:48620/mcpMCP, for agents:48621/wsWebSocket, for a browser tab- one per machine, shared by every window and agent
Your agents the same in both variants
wqs-helper continue <session>, the line Continue in a terminal copies. Cursor and Antigravity use their own global registration Not through this helper: an agent registered with wqs-helper mcp --dir <folder> talks stdio to a private helper of its own. That one reads the archives in those folders and sees no webQsee window.
- Recordings travel back the same way. When an agent asks for one (
list_recordings,fetch_recording,await_new_recording), the helper asks the open webQsee windows over their own link, and the recording comes back along it. A cloud recording the helper downloads itself, from a signed link, with no window needed. - It has to be running. The extension starts the helper whenever it needs it, and a helper started that way ends itself 15 minutes after the last window closes with nothing running. A browser tab cannot start it at all. If your agent should reach it with no webQsee window open, run
wqs-helper startonce: that one stays untilwqs-helper stopor a reboot. - The quick analysis needs none of this. The browser sends it to webQsee AI in the EU, or with your own key straight to your provider. No helper, no agent CLI.
Stop guessing. Start webQseeing.
Add webQsee to Chrome or Edge in one click. Recording and replay are free, no signup needed. Upgrade when you need AI analyses, cloud sharing, S3 storage and Pro-grade tooling.
Works in Chrome 103+, Edge 103+ and most Chromium-based browsers. Install instructions.