← back to the watches

The desktop app

The whole tool, in one folder, with the browser part already inside it. Nothing to install and no Node to set up.

It runs a small local server and opens the site at localhost:1931. Every page works offline. On macOS it can also reach into tabs you already have open — see the honest note about that below.

macOS

tested

Apple silicon & Intel

Download for macOS

Unzip, drag to Applications, then right-click the app and choose Open the first time — see below.

Windows

untested

Windows 10 & 11, 64-bit

Download for Windows

Unzip anywhere, then run Keep Every Page Alive.cmd. Closing the console window stops it.

Linux

untested

x86-64

Download for Linux

tar -xzf KeepEveryPageAlive-linux-x64.tar.gz && ./keep-every-page-alive

Clairvoyant mode: tabs you already have open

Everything above keeps any tab it opens for you. macOS builds go further: the same helper can also reach into tabs you already have open — across Chrome, Safari, Edge, Brave and Arc — and reload them in place, never in a pop-up. It's built on AppleScript, which exists on no other platform; on Windows and Linux, the browser extension does the same job one browser at a time instead.

The first time, macOS asks once per browser for permission to control it. Approve each prompt as it appears, or grant it later under System Settings → Privacy & Security → Automation. Firefox stays beyond the veil either way — it answers no AppleScript, so no census can see it.

Reloading needs nothing more. Hold in place — which the helper uses for course players — also needs each browser to allow JavaScript from Apple Events, which is off until you turn it on: in Chrome or Brave, View → Developer → Allow JavaScript from Apple Events; in Safari, Settings → Developer (turn on Show features for web developers under Advanced first; older Safari has it in the Develop menu); in other browsers, look in their own Developer menu.

Prefer just the helper, no app?

The macOS download above is this same helper already bundled with a Node runtime and the whole site — nothing to install. If you'd rather run one small file yourself instead: no dependencies, no account, and it only ever listens on localhost.

Download helper.mjs
  1. Open Terminal, go to where you saved it, and run node helper.mjs.
  2. Open localhost:1931 in any browser.
  3. Your open tabs appear. Tick the ones to keep, choose an interval, and press Keep selected alive.

Requires Node.js. Its clock runs outside the browser, so kept tabs keep refreshing even if you close this page.


The browser extension

The page you are reading can only keep tabs it opened itself — that is a browser security boundary, not a bug. The macOS helper above steps around it with AppleScript, on a Mac. The extension steps around it on any operating system, and adds one thing neither the page nor the helper can do.

What the extension addsany OS

Five permissions at install, none of which show a warning, and access to no website at all. Nudging a page, or the smart ladder, needs permission for that one site, asked for by name, at the moment you turn it on.

Installing it todaynot in the store yet

The Chrome Web Store listing is written and waiting to be submitted. Until it is live you load the extension yourself — this is the same package that will be submitted.

Download the extension
  1. Unzip it somewhere you intend to keep it — Chrome loads it from that folder every time it starts.
  2. Open chrome://extensions and turn on Developer mode, top right.
  3. Press Load unpacked and choose the unzipped folder.
  4. Pin the toolbar icon. On any page, click it, name the tab, pick an interval, and press Keep this tab alive.

Chrome warns you about developer-mode extensions every time it starts. That stops once this is in the store, and not before.

One number changes when it is packed

Chrome ignores its own 30-second floor on extension timers while an extension is loaded unpacked. A shorter interval appears to work now and quietly becomes about 30 seconds once the same code is installed from the store. That is why the shortest interval the extension offers is 31 seconds — the 17 this website allows is not deliverable there.


What “untested” means here

The Windows and Linux builds were assembled correctly — the right Node runtime for each platform, the whole site, the same code the Mac app runs — but neither has ever been launched on the operating system it is for. They were put together on a Mac. That is the plain truth and it seemed better to say it than to imply a testing that did not happen.

If one works, or doesn't, tell me and this label comes off or the build gets fixed. The macOS build has been run start to finish.


Your computer will warn you

None of these are code-signed yet, so both operating systems will say so. That is the correct behaviour and you should be suspicious of downloads in general — here is exactly what to expect and why.

macOS will say the app “cannot be opened because it is from an unidentified developer”, or that it is damaged. Right-click the app → Open → Open again. That path exists precisely so you can make an informed exception; double-clicking will not offer it.

Windows SmartScreen will show “Windows protected your PC”. Click More info → Run anyway.

Signing costs money per year on both platforms (an Apple Developer account, and a Windows code-signing certificate). It is on the list. Until then the warnings are real and I would rather explain them than pretend they will not appear.

Checking what you downloaded

SHA-256 for each file, so you can confirm the bytes you got are the bytes that were built. This proves integrity, not origin — it is not a substitute for a signature, and if someone replaced both the file and this page it would not save you.

SHA256SUMS.txt

macOS: shasum -a 256 KeepEveryPageAlive-macos.zip · Linux: sha256sum … · Windows: certutil -hashfile … SHA256

What it can and cannot do

Prefer not to download anything?

You do not have to. The site itself does the main job in any browser, with nothing installed at all.