What PocketQA puts on your computer
Results are from the release that's live, deployed 17 Nov 2026 (667a7eb): 453 of the 459 checks behind the security, privacy and terms pages passed.
For whoever approves the lab installer: what it installs, what it can do, what leaves the computer, and how to take it off. Each part lists the tests that check it against the code that's installed, and what they did on the release that's live; the parts marked “From SECURITY.md” are that file's own words.
Check the installer before it runs
The installer and each release are signed with PocketQA's release key, and each one's SHA-256 is published beside it. To check the installer before it runs, in Terminal:
- Download it, its signature and the public key:
curl -fsSL -O https://pocketqa.dev/install.sh -O https://pocketqa.dev/install.sh.sig -O https://pocketqa.dev/release.pub - Check the key is PocketQA's:
openssl pkey -pubin -in release.pub -outform DER | openssl dgst -sha256must end with the fingerprint under "Updates are signed", below. - Check the signature:
openssl dgst -sha256 -verify release.pub -signature install.sh.sig install.shmust sayVerified OK. If it doesn't, don't run it. - Read it if you like, then run it with the code from your install command:
bash install.sh --code ABCD-2345
The checksum alone (curl -fsSL -O https://pocketqa.dev/install.sh.sha256, then shasum -a 256 -c install.sh.sha256, or sha256sum -c on Linux) shows the download arrived whole, not who made it: it comes from the same service.
Checked by 24 tests before every release: all passed on the live release
- checking the installer installer Passed
- signed with the release key, as releases are installer Passed
- a signature that fails for any other installer installer Passed
- and its SHA-256, under the name it downloads as installer Passed
- each release has its SHA-256 beside it, and it checks out installer Passed
- a whole download checks out installer Passed
- a changed one fails the check, before anything runs installer Passed
- it installs with a code: a good, signed release goes in installer Passed
- the installer refuses a download that doesn't match installer Passed
- saying nothing was installed, and what to do installer Passed
- the served checksum matches the served installer service Passed
- its signature is served beside it, byte for byte service Passed
- another address's signed installer is never served here service Passed
- and no signature is claimed service Passed
- the served installer's checksum matches the served installer end to end Passed
- and the release's matches the release end to end Passed
- the served installer and release are each signed with the release key end to end Passed
- a release that doesn't match its signature is refused installer Passed
- and so is one with no signature installer Passed
- the installer refuses a download that installer Passed
- a signed release whose files would land outside the lab folder installer Passed
- a copy with no release key takes no update installer Passed
- the agent updates itself to the newer, signed version installer Passed
- and never back to an older one, signed or not installer Passed
What it installs, and where
- PocketQA itself:
~/pocketqa(its code) and~/pocketqa-work(its runs, screenshots, log and keys). Nothing outside your home folder, except the optional lid watcher below.Checked by 2 tests before every release: all passed on the live release
- where: outside the home folder installer Passed
- its code in ~/pocketqa and its work in ~/pocketqa-work installer Passed
- Tools, on a Mac through Homebrew: Node, libimobiledevice (for iPhones), Google Chrome and Android's platform tools (adb); Homebrew brings Apple's command line tools if they aren't there. On Linux, through your package manager: Python, Node and npm, adb (with its phone rules), curl and, on a desktop, xprintidle (how long since someone used the computer); Google Chrome from Google (
dl.google.com), or Chromium on an Arm computer. ChromeDriver, matched to Chrome, is downloaded over https from Google's Chrome for Testing storage (storage.googleapis.com/chrome-for-testing-public/), using Chrome for Testing's own list (googlechromelabs.github.io); download redirects and remote list overrides are refused. It is saved into~/pocketqa-work, with no Node, and used only once it says it's the driver for that Chrome.Checked by 14 tests before every release: all passed on the live release
- installs: every Homebrew and Linux package the setup installs is on the page installer Passed
- xprintidle only on a desktop installer Passed
- inventory: finds each kind lab Passed
- and only sizes and PocketQA's own names leave the computer lab Passed
- never a profile in use, the newest ChromeDriver, results, keys lab Passed
- asked for from the dashboard or an agent by name, with no password lab Passed
- uninstall --dry-run: lists what would go, by name and path, and touches nothing lab Passed
- tools it didn't install are only asked about lab Passed
- uninstall: its folders, temporary files, launch agents and npx entry are gone lab Passed
- a link named like its profiles goes, never what it points to lab Passed
- the uninstall never runs as root lab Passed
- and removes nothing the inventory doesn't name lab Passed
- the lid watcher removed and the sleep setting put back, with fixed commands under sudo lab Passed
- the uninstall takes its computer off the account, and its key stops working end to end Passed
- Only for a lab with an iPhone: its Web Inspector bridge, the npm package
appium-remote-debuggerat a pinned version, into~/pocketqa-work/inspector(install scripts off).Checked by 1 test before every release: passed on the live release
- the iPhone inspector installer Passed
- Only for native app tests: installed with
--native, Appium and its Android and iOS drivers, through npm.Checked by 1 test before every release: passed on the live release
- Appium and its drivers only with --native installer Passed
- Background services, as your user, never as root: - Mac:
dev.pocketqa.agent(takes the dashboard's tests) anddev.pocketqa.hub(the Grid, a WebDriver hub on this computer only), in~/Library/LaunchAgents. - Linux:pocketqa-agent.serviceandpocketqa-hub.service, systemd user services.Checked by 9 tests before every release: all passed on the live release
- services: every launchd label and systemd unit the code writes is on the page installer Passed
- the agent and the Grid as the user installer Passed
- hub: a token is made, readable by this user only lab Passed
- nothing without it lab Passed
- a request from a web page (Origin) is refused lab Passed
- as is one by another name (DNS rebinding) lab Passed
- and no capability can start a program lab Passed
- nested Appium options cannot bypass the capability checks in either match set lab Passed
- safe grouped Appium options are normalized before choosing and forwarding a device lab Passed
- Only if your team lets a Mac test with its lid shut: a lid watcher,
com.pocketqa.lidwatch, run by macOS for the whole computer (/Library/LaunchDaemons, script in/Library/PocketQA). It keeps the Mac running closed only while it's on its charger and PocketQA says it's testing.Checked by 16 tests before every release: all passed on the live release
- where: outside the home folder installer Passed
- pairing again leaves the key readable by this user alone lab Passed
- setup never keeps a computer awake always lab Passed
- the lid watcher runs a closed Mac only on its charger lab Passed
- installed once, as root lab Passed
- and undoes an older setup that did lab Passed
- the real list is read over https only, from Chrome for Testing lab Passed
- a download that says it's another version is refused, not used lab Passed
- a Linux lab runs as its user's own systemd service, never as root lab Passed
- and setup uses sudo only to install packages lab Passed
- ChromeDriver downloads only use Google's Chrome for Testing storage (#1091) lab Passed
- ChromeDriver downloads refuse redirects to another host (#1091) lab Passed
- ChromeDriver versions from arguments and the list cannot form paths (#1091) lab Passed
- Safari repair refuses to quit when idle time is unknown (#1217) lab Passed
- Safari repair waits for the person when Safari will not quit (#1217) lab Passed
- Safari quit never force-ends the browser when a prompt keeps it open (#1217) lab Passed
When it asks for the password
The installer asks once, at the start, and keeps it only while it runs. What it's for:
- Mac: installing Homebrew (if it isn't there), letting Safari be driven by tests (
safaridriver --enable), undoing an older always-awake sleep setting if one is set, and the lid watcher if your team chose it. - Linux: installing packages, adding your user to
plugdev(to use an Android phone), undoing masked sleep, andloginctl enable-linger(so it runs with nobody logged in).
Each is optional: skip one and PocketQA says what it can't do without it.
After that, only when someone asks, and each time with a password typed on this computer: a fix your team or its agent asks for (Labs › Fix it, or lab_fix), shown in macOS's own password prompt, and taking PocketQA off with its uninstaller, for the parts outside your home folder.
Checked by 3 tests before every release: all passed on the live release
- the password: every sudo the installer and the setup run is for a reason the page gives installer Passed
- each of those reasons is on the page installer Passed
- later, only when asked installer Passed
What it can and can't do
It opens your team's sites in browsers on this computer and on the phones plugged into it, and nothing else. It reads no files outside its own folders, runs as a standard user if you install it as one, and takes only tests your team's account sends it, signed with this computer's own key.
In Safari's test sessions only: a small web extension of PocketQA's own (its listeners for a page's script errors, the same ones it reads every page with), loaded into the test's Safari session on that test's site and PocketQA's control page, and taken off when the test ends. It changes nothing on the page, has no permission but scripting, and is loaded for the test session only, never installed in Safari for your own browsing. From SECURITY.md: "Safari's load hook."
Checked by 6 tests before every release: all passed on the live release
- Safari's load hook (#474): the lab's own listeners, the same as page_js.HOOK's lab Passed
- scoped to this test's own addresses: its site and the lab's control page, nothing else lab Passed
- loaded into this test session only, a copy with those addresses written in lab Passed
- and taken off before the session ends, its copy deleted lab Passed
- a Safari that can't load it says so, nothing else changes lab Passed
- by a Manifest V3 extension with no more than scripting lab Passed
The password-free lab_fix safari_sessions repair may ask your own Safari to quit if it still holds an old test session, but only after the Mac has been idle for at least five minutes. If idle time is unknown, Safari is left alone. It quits normally: PocketQA never force-ends Safari if a prompt keeps it open, and asks you to finish instead. From SECURITY.md: "The lab computer itself."
Checked by 18 tests before every release: all passed on the live release
- pairing again leaves the key readable by this user alone lab Passed
- setup never keeps a computer awake always lab Passed
- the lid watcher runs a closed Mac only on its charger lab Passed
- installed once, as root lab Passed
- and undoes an older setup that did lab Passed
- the real list is read over https only, from Chrome for Testing lab Passed
- a download that says it's another version is refused, not used lab Passed
- a Linux lab runs as its user's own systemd service, never as root lab Passed
- and setup uses sudo only to install packages lab Passed
- ChromeDriver downloads only use Google's Chrome for Testing storage (#1091) lab Passed
- ChromeDriver downloads refuse redirects to another host (#1091) lab Passed
- ChromeDriver versions from arguments and the list cannot form paths (#1091) lab Passed
- Safari repair refuses to quit when idle time is unknown (#1217) lab Passed
- Safari repair waits for the person when Safari will not quit (#1217) lab Passed
- Safari quit never force-ends the browser when a prompt keeps it open (#1217) lab Passed
- Test now with devices chosen: only real device names are kept end to end Passed
- a report address that isn end to end Passed
- a site address with a password in it is refused end to end Passed
Phones
Each phone plugged in has a role your team sets in its dialog: someone's personal phone (until your team says otherwise) or a test device. On a personal phone PocketQA changes no settings and never uses the owner's browser: an iPhone tests in Safari's own clean test window, and an Android phone is never tested in its owner's Chrome, since Chrome there can't give a test a separate browser: it's tested in Chrome Beta when that's installed beside it (its own app with its own data, cleared for the test), and otherwise not at all, its result saying how to install Chrome Beta. It's tested only while it's awake and unlocked: never woken. Only on a test device does it keep the phone awake on its charger, set a longer screen timeout, stop it charging at 80% if your team chooses, and clear its browser between tests. From SECURITY.md: "Phones: a test device or someone's own."
Checked by 22 tests before every release: all passed on the live release
- a phone nobody has said about is personal, and not set service Passed
- a phone nobody has said about is end to end Passed
- marked a Test device from its dialog end to end Passed
- its lab hears each phone end to end Passed
- phone fixes skip a personal phone: not kept awake, no screen timeout, no 80% charging lab Passed
- is never woken, kept awake or driven in its owner's Chrome lab Passed
- is tested in Chrome Beta (issue 1089) lab Passed
- never touches com.android.chrome's data lab Passed
- its lock never dismissed, never kept awake, nothing opened on it after lab Passed
- without Chrome Beta, its result says to install Chrome Beta first lab Passed
- that's asleep or locked isn't woken lab Passed
- and the end of a run never sets a personal phone lab Passed
- the Grid never drives a personal Android phone lab Passed
- a skipped personal phone says so in its evidence lab Passed
- a test device gets them: awake while charging lab Passed
- held on someone's own phone: WebDriver and a fresh safaridriver tried, the phone never restarted lab Passed
- nor a test device with no screen code, where #890 restarted it (#933) lab Passed
- the lab never restarts an iPhone (#933) lab Passed
- a personal Android phone without Chrome Beta isn service Passed
- one tested in Chrome Beta says which app and version service Passed
- step screenshots go once its results have service Passed
- results: a personal iPhone says a clean browser service Passed
The network
Outbound only: it opens no port to your network (the Grid listens on this computer alone, with its own token). For an allowlist, it reaches:
- the PocketQA service it's paired with (
pocketqa.dev), over HTTPS; - the sites your team tests;
- at install and update:
raw.githubusercontent.com,formulae.brew.shandghcr.io(Homebrew, Mac),dl.google.com(Chrome, Linux),registry.npmjs.org(the iPhone inspector, and Appium with--native) andstorage.googleapis.com(ChromeDriver); unpkg.com(the browser-support data it uses to predict what a site needs);googlechromelabs.github.io(Chrome for Testing's list, to pick the ChromeDriver for this Chrome);example.com, from a test device's browser, only when that device can't open PocketQA's own page: to tell a device with no internet from PocketQA being unreachable.
The command-line runner in the package (lab/cli.py), when your CI runs it on a pull request with a GitHub token, comments its result there through GitHub's API (api.github.com): from your CI, never from the lab.
Checked by 13 tests before every release: all passed on the live release
- the network: every host the lab's code reaches is in the page's list installer Passed
- every host the page lists is one it reaches installer Passed
- point the lab at its own network end to end Passed
- a site on the lab computer end to end Passed
- lab: an address on its own network, the service saying nothing, is refused lab Passed
- enough on its own lab Passed
- only http and https lab Passed
- pages are paths on the site lab Passed
- a journey that leaves its site fails there lab Passed
- desktop Chrome opens the site at the address the lab checked lab Passed
- expect says true or false lab Passed
- private redirects need both team and local approval lab Passed
- a private initial address is refused before fetching lab Passed
Removing it
Mac, in Terminal:
`` launchctl bootout gui/$(id -u)/dev.pocketqa.agent; launchctl bootout gui/$(id -u)/dev.pocketqa.hub rm -f ~/Library/LaunchAgents/dev.pocketqa.*.plist; rm -rf ~/pocketqa ~/pocketqa-work sudo launchctl bootout system/com.pocketqa.lidwatch 2>/dev/null; sudo rm -rf /Library/LaunchDaemons/com.pocketqa.lidwatch.plist /Library/PocketQA ``
Linux:
`` systemctl --user disable --now pocketqa-agent.service pocketqa-hub.service rm -f ~/.config/systemd/user/pocketqa-*.service; rm -rf ~/pocketqa ~/pocketqa-work ``
Installed before PocketQA's own names (November 2026)? An update moved it to the names above and left a link at each old one; remove those too (a link goes, not what it points at): rm -rf ~/pocket-lab ~/pocket-lab-work. A Mac's lid watcher keeps its older name: sudo launchctl bootout system/com.pocketlab.lidwatch 2>/dev/null; sudo rm -rf /Library/LaunchDaemons/com.pocketlab.lidwatch.plist /Library/PocketLab. Or let PocketQA do all of it: python3 ~/pocketqa/lab/uninstall.py --dry-run lists what goes, under either name, and without --dry-run removes it.
Then remove the computer from your team's dashboard (Labs › the lab › Remove): its key stops working at once. Homebrew and the tools it installed stay; remove them with Homebrew if you want them gone.
Checked by 14 tests before every release: all passed on the live release
- removing it: the commands name every launchd label installer Passed
- the systemd units it disables are the ones it installs installer Passed
- inventory: finds each kind lab Passed
- and only sizes and PocketQA's own names leave the computer lab Passed
- never a profile in use, the newest ChromeDriver, results, keys lab Passed
- asked for from the dashboard or an agent by name, with no password lab Passed
- uninstall --dry-run: lists what would go, by name and path, and touches nothing lab Passed
- tools it didn't install are only asked about lab Passed
- uninstall: its folders, temporary files, launch agents and npx entry are gone lab Passed
- a link named like its profiles goes, never what it points to lab Passed
- the uninstall never runs as root lab Passed
- and removes nothing the inventory doesn't name lab Passed
- the lid watcher removed and the sleep setting put back, with fixed commands under sudo lab Passed
- the uninstall takes its computer off the account, and its key stops working end to end Passed
From SECURITY.md
What leaves the computer. With each run: which device, passed or failed, page timings, each page's errors and the requests that failed, the last 15 lines of each device's console, and each flow step: its words, whether it passed, and, unless the team switches it off (Settings › Privacy › Send each flow step's screen text), a line of what a tap hit and of what was on the screen after.
Checked by 21 tests before every release: all passed on the live release
- nothing of anyone else's: no customers, projects or results installer Passed
- what leaves: addresses without their query strings lab Passed
- no tokens or emails lab Passed
- never what a journey typed lab Passed
- the last 15 console lines at most lab Passed
- screen text only while the team sends it lab Passed
- keyed by the lab lab Passed
- the computer sends no network name lab Passed
- the computer sends its model identifier (which model and year), never its serial number or its name lab Passed
- the computer's battery leaves as its level lab Passed
- the Wi-Fi network's name never leaves the computer lab Passed
- no internet: the phone's Wi-Fi network name never leaves the computer lab Passed
- the site's stack leaves as plain names only lab Passed
- readings that move every look aren't a change worth sending lab Passed
- a page that looks different from its last clean run says how much lab Passed
- a flow step live is what the result sends for it, screen text on lab Passed
- a flow step live is what the result sends for it, screen text off lab Passed
- and with screen text off, no tapped words and no screen text lab Passed
- lab/agent.py tells each run the team's screen-text choice lab Passed
- masked by the result's own rule: no query string, no typed text, no email end to end Passed
- and with the team's screen text switched off, no tapped words and no screen text end to end Passed
Before any of it leaves, addresses lose their query strings, tokens and emails are masked, and what a flow typed is never sent (the step keeps its field).
With the computer's status: its model, its model identifier (which model and year: a Mac's "MacBookPro16,2", a PC's firmware model name; never a serial number), chip, memory and system (macOS), its free disk space, whether it's on its charger and its battery's level (a number), the phones' models and versions, their health (battery, charging, temperature, free memory and storage, hours since restart), what changes how a site looks or runs on them (screen size and refresh rate, text size, display zoom, dark mode, animations, language and region, Low Power Mode, how hot they are, battery health), whether they're on Wi-Fi with its signal and speed, and whether a VPN is on (never the Wi-Fi network's name), its setup checks and the end of its own log; with a run, also the names of what the site is built with (Flutter, React…), never more of the page; no network name, and a phone is told apart by a short id keyed by the lab's own key, never its serial number.
The service also notes which country the computer's network is in, as Cloudflare sees the request (never its address).
No screenshots or page contents: a page that looks different from its last good run is sent as how much of the screen changed and where (top, middle or bottom), worked out on the computer from screenshots that stay there.
Tests started on the computer itself (the local MCP) report the same way, to the team's own dashboard. Tables are capped at 1.8 MB a send; runs older than 90 days are dropped on the computer.
The lab computer itself. Its key is readable by its user alone, and stays so when it's paired again.
Checked by 15 tests before every release: all passed on the live release
- pairing again leaves the key readable by this user alone lab Passed
- setup never keeps a computer awake always lab Passed
- the lid watcher runs a closed Mac only on its charger lab Passed
- installed once, as root lab Passed
- and undoes an older setup that did lab Passed
- the real list is read over https only, from Chrome for Testing lab Passed
- a download that says it's another version is refused, not used lab Passed
- a Linux lab runs as its user's own systemd service, never as root lab Passed
- and setup uses sudo only to install packages lab Passed
- ChromeDriver downloads only use Google's Chrome for Testing storage (#1091) lab Passed
- ChromeDriver downloads refuse redirects to another host (#1091) lab Passed
- ChromeDriver versions from arguments and the list cannot form paths (#1091) lab Passed
- Safari repair refuses to quit when idle time is unknown (#1217) lab Passed
- Safari repair waits for the person when Safari will not quit (#1217) lab Passed
- Safari quit never force-ends the browser when a prompt keeps it open (#1217) lab Passed
Setup never keeps a computer awake always (no sleep 0, disablesleep or masked sleep, which keep a shut or unplugged laptop running, where it can't cool), and undoes an older setup's that did: PocketQA itself holds a computer awake only while it's on its charger and only for testing, or while a test runs, and lets go otherwise.
A Mac the team lets test with its lid shut gets a lid watcher, installed once with the Mac's password as root's own copy: it runs the Mac closed only on its charger, and only while the lab keeps saying so; unplugged, or the lab stopped, it sleeps.
ChromeDriver is downloaded over https only from Google's Chrome for Testing storage, using Chrome for Testing's own list. Download redirects and remote list overrides are refused; versions are checked before they form a path. The driver is used only once it says it's the driver for that Chrome.
The password-free lab_fix safari_sessions repair can ask the person's own Safari to quit when it still holds an old automation session and the Mac has been idle for at least five minutes. If idle time cannot be read, it leaves Safari alone. It asks Safari to quit normally and never force-ends it if a prompt or unsaved work keeps it open; the result asks the person to finish.
A Linux lab (Android phones and Chrome) runs as its user's own systemd service, never as root, through the same signed updater; setup uses sudo only to install packages, undo an older always-awake, join plugdev and keep it running.
Phones between sites. Desktop Chrome gets a fresh profile every session. Only a test device's Chrome on Android is driven (below): ChromeDriver's own documentation says it starts Chrome there with a clear data directory, and the lab also clears cookies, cache and the site's storage before and after every run (web.py --clear). Either way that's the phone's own Chrome, so a personal phone's never is: a personal phone is tested in Chrome Beta (com.chrome.beta) instead, a separate app with its own data, started and cleared the same way. Storage other sites left (a sign-in provider's, say) isn't cleared yet: see Still open.
Not tested automatically: clearing a phone needs a real phone; checked by hand on the labs.
Phones: a test device or someone's own. Each phone has a role the team sets in its dialog (Labs › the lab › the phone › Status), asked until someone answers; until then it's someone's own (personal).
Checked by 22 tests before every release: all passed on the live release
- a phone nobody has said about is personal, and not set service Passed
- a phone nobody has said about is end to end Passed
- marked a Test device from its dialog end to end Passed
- its lab hears each phone end to end Passed
- phone fixes skip a personal phone: not kept awake, no screen timeout, no 80% charging lab Passed
- is never woken, kept awake or driven in its owner's Chrome lab Passed
- is tested in Chrome Beta (issue 1089) lab Passed
- never touches com.android.chrome's data lab Passed
- its lock never dismissed, never kept awake, nothing opened on it after lab Passed
- without Chrome Beta, its result says to install Chrome Beta first lab Passed
- that's asleep or locked isn't woken lab Passed
- and the end of a run never sets a personal phone lab Passed
- the Grid never drives a personal Android phone lab Passed
- a skipped personal phone says so in its evidence lab Passed
- a test device gets them: awake while charging lab Passed
- held on someone's own phone: WebDriver and a fresh safaridriver tried, the phone never restarted lab Passed
- nor a test device with no screen code, where #890 restarted it (#933) lab Passed
- the lab never restarts an iPhone (#933) lab Passed
- a personal Android phone without Chrome Beta isn service Passed
- one tested in Chrome Beta says which app and version service Passed
- step screenshots go once its results have service Passed
- results: a personal iPhone says a clean browser service Passed
On a personal phone PocketQA changes no settings: it doesn't keep it awake, lengthen its screen timeout or change its charging, and the end of a run doesn't set any of them back. Its browser is never the owner's.
An iPhone tests in Safari's own automation window, which starts from a clean slate, hides the owner's tabs until it ends and destroys what the test left (Apple's WebDriver).
Chrome on Android can't give a test a separate browser, so a personal Android phone isn't tested in Chrome, by a test or through the Grid. A test runs in Chrome Beta instead, when it's installed beside Chrome: its own app with its own data, cleared for the test, so the owner's Chrome is never started, cleared or sent anything. Only Chrome Beta's version is read (as Chrome's is), the phone is tested only while its owner has it awake and unlocked, and nothing opens on it afterwards.
Someone who uses Chrome Beta as their own browser would lose its data, so the dashboard and the result name the app. Without Chrome Beta it isn't tested, and its result says how to install it. Its screenshots stay in the run's folder on the computer and go with it, and on the service a run's step screenshots go once its results do.
On a test device PocketQA may keep it awake on its charger, set a 30-minute screen timeout, stop it charging at 80% when the team chooses, and clear its browser between tests.
PocketQA never restarts a phone, whichever it is: when Safari on an iPhone stays held by a test session that ending the session and restarting the lab's driver didn't free, the result and lab_doctor say what a person does. Each result says which a phone was. Making a test device personal stops these changes; it doesn't undo settings already made.
Run diagnostics include fixed pipeline statuses, exit codes and exception categories for CSV generation, evidence collection and detail collection. They never include exception text, commands or home-folder paths. They stay with the account's test result, under the same account and support-access controls.
The lab computer's own network. A lab sits on someone's office or home network, and nobody can point it there: not an agent, a script, a teammate or the service itself.
Checked by 11 tests before every release: all passed on the live release
- point the lab at its own network end to end Passed
- a site on the lab computer end to end Passed
- lab: an address on its own network, the service saying nothing, is refused lab Passed
- enough on its own lab Passed
- only http and https lab Passed
- pages are paths on the site lab Passed
- a journey that leaves its site fails there lab Passed
- desktop Chrome opens the site at the address the lab checked lab Passed
- expect says true or false lab Passed
- private redirects need both team and local approval lab Passed
- a private initial address is refused before fetching lab Passed
The service refuses a site or one-off address on a private network (192.168.x, 10.x, .local, a bare name…) from every caller until the team approves it (Settings › Privacy).
The computer decides again for itself, and refuses unless the service said it's approved and it's listed on the computer (~/pocketqa-work/allow-hosts); it checks where a public name really leads, refuses a redirect onto its network, opens only http and https with no password and pages that are paths on the site, fails a flow the moment it leaves its site, and pins desktop Chrome to the address it checked (so a name can't change where it leads mid-test).
The same initial-address and redirect checks cover downloaded flow files and build fingerprints, including both approvals for private addresses.
An expect step answers only true or false. Its own localhost (a dev server) is always allowed.
The Grid on a lab computer. The WebDriver hub (lab/hub.py) listens on the computer itself and needs its own token, made at first start and readable only by that user. It refuses anything a web page open on that computer could send it (an Origin header, another Host, a body that isn't JSON), and any capability that names a program, its arguments, an extension, a profile, a browser to attach to or an app to download: a test needs none of them, and each would run code on the computer. Appium’s grouped options are flattened and checked before selecting the device; they cannot override the device the hub selected.
Checked by 7 tests before every release: all passed on the live release
- hub: a token is made, readable by this user only lab Passed
- nothing without it lab Passed
- a request from a web page (Origin) is refused lab Passed
- as is one by another name (DNS rebinding) lab Passed
- and no capability can start a program lab Passed
- nested Appium options cannot bypass the capability checks in either match set lab Passed
- safe grouped Appium options are normalized before choosing and forwarding a device lab Passed
Updates are signed. Each release is signed with an RSA key held only as a GitHub secret (RELEASE_SIGNING_KEY), never on the service. A computer carries the public half (lab/release.pub, from its install or its first update since the key was set) and takes an update only when the signature checks out, the archive's version is the one announced, it's newer than what it has, and every file in it lands inside the lab's own folder. A copy with no key takes no update at all. The installer carries the public key too, and installs (and --updates) only a download signed with it, saying the key's fingerprint as it does: compare it with this one, SHA-256 3566147f8c0dc519… (in full: 3566147f8c0dc5198f7f96dad66c05dd384e29476ac30c8fafa47efd40376729). So whoever changed the service still couldn't push code to computers that are installed, or roll them back to an old release. Packaging refuses to build a release without the key, or one whose signature doesn't match lab/release.pub.
Checked by 7 tests before every release: all passed on the live release
- a release that doesn't match its signature is refused installer Passed
- and so is one with no signature installer Passed
- the installer refuses a download that installer Passed
- a signed release whose files would land outside the lab folder installer Passed
- a copy with no release key takes no update installer Passed
- the agent updates itself to the newer, signed version installer Passed
- and never back to an older one, signed or not installer Passed
Installs are signed too. The installer the service hands out (/install.sh) is signed with the same release key, as it's served from that address, byte for byte (/install.sh.sig), and its SHA-256 is published beside it (/install.sh.sha256), as each release's are (/pocket-lab.tar.gz.sha256 and .sig). The setup page and the help offer "download, check, then run" next to the one-line command. The installer installs only a release signed with the key it carries; if one isn't, it stops and says nothing was installed. After every deploy, CI checks the live installer and release against their checksums, and the installer's signature against lab/release.pub. The checksum comes from the same service, so it shows the download arrived whole, not who made it; the signature, checked against the fingerprint above, shows who made it (/security/lab says how, step by step: openssl dgst -sha256 -verify release.pub -signature install.sh.sig install.sh says Verified OK).
Checked by 16 tests before every release: all passed on the live release
- signed with the release key, as releases are installer Passed
- a signature that fails for any other installer installer Passed
- and its SHA-256, under the name it downloads as installer Passed
- each release has its SHA-256 beside it, and it checks out installer Passed
- a whole download checks out installer Passed
- a changed one fails the check, before anything runs installer Passed
- it installs with a code: a good, signed release goes in installer Passed
- the installer refuses a download that doesn't match installer Passed
- saying nothing was installed, and what to do installer Passed
- the served checksum matches the served installer service Passed
- its signature is served beside it, byte for byte service Passed
- another address's signed installer is never served here service Passed
- and no signature is claimed service Passed
- the served installer's checksum matches the served installer end to end Passed
- and the release's matches the release end to end Passed
- the served installer and release are each signed with the release key end to end Passed