Mouse jiggler Chrome extension: what a browser tab can and cannot do

An extension lives inside the tab, not on the desktop

Everything a Chrome extension does happens inside the browser sandbox. It can dispatch mouse and keyboard events into a web page, keep a timer running, and ask Chrome to hold the screen awake. What it cannot do is move the physical pointer, because the operating system does not let a web page reach the input stack — that boundary is the entire point of the sandbox.

So the honest description of a Chrome jiggler is narrow but real: it convinces a web page that someone is interacting with it. Every claim beyond that runs into the same wall.

Why a desktop tracker never notices it

Hubstaff, Time Doctor, Insightful and the rest run as native applications, and they read the system idle clock — the time since the last real keyboard or mouse event as the operating system counts it. Synthetic events dispatched inside a web page are not input events at that level; they never reach it, and they never reset it.

That is why the reports do not move. The extension can be running perfectly, the page can be reacting to every simulated click, and the ten-minute block still comes back empty, because nothing was ever measured in the browser to begin with.

• System idle clock — untouched by anything inside a tab.
• Desktop tracker activity percentage — unaffected.
• Screen lock and screen saver timers — unaffected.
• A web app’s own away timer — this one an extension can reach.

What it genuinely does help with

There is a real use case, and it is worth stating clearly rather than dismissing the whole category. Web applications run their own away logic in JavaScript — a chat that greys you out after a few minutes, a training course that pauses the video, a dashboard that logs you out. That logic lives in the page, and an extension is exactly the right layer to reach it.

The Screen Wake Lock API is the second honest capability: a page can ask Chrome to keep the display from switching off. Useful for a long read or a recipe on a kitchen tablet, and unrelated to whether anything counts you as active.

• Keeping a web chat or dashboard from marking you away.
• Holding a video or course page from auto-pausing.
• Screen Wake Lock — the display stays on, nothing else changes.

The permissions question on those listings

Most of these extensions ask to read and change your data on all websites, because dispatching events into arbitrary pages requires exactly that. It is not necessarily malicious — the permission genuinely follows from the feature — but it is a very large grant for a very small job, and it applies to your mail, your bank and your work tools alongside everything else.

The category also turns over quickly: listings appear, get renamed, change owners and are pulled. An extension with broad host permissions that changes hands is a well-known way for something benign to become something else without you reinstalling anything. If a tab-level tool is what you need, prefer the narrowest permissions you can find and check who publishes it.

Background throttling is the other limit

Chrome aggressively throttles timers in tabs that are not visible, and suspends inactive service workers. A jiggler extension that works while you watch it can quietly stop once the window is minimised or the tab moves to the background — which is precisely the moment you wanted it running.

This is why so many listing reviews say it works for ten minutes and then stops. It usually is not a bug in the extension; it is the browser doing what it is designed to do with background work.

The Chromebook case, answered plainly

On ChromeOS an extension is often the only thing you can install, so the question is not academic. The answer is unchanged: an extension still cannot reach the system input layer, and ChromeOS will still count the device as idle. If a desktop tracker is what you are dealing with, ChromeOS does not have a route to what a native tool does.

The Linux container is not the loophole it looks like either. Crostini runs its own display server inside a container, so input generated in there stays in there and never reaches the ChromeOS idle clock. Running a Linux jiggler on a Chromebook keeps the container busy, not the device.

Extension, hardware dongle or native app

The three options are not competitors so much as three different reaches. An extension reaches one web page. A USB dongle reaches the input stack from outside, which works everywhere but produces one identical movement forever and can be spotted as an unfamiliar HID device on a managed machine. A native application reaches the same input stack from inside the system, which is why it is the only one of the three that can vary what it does and stop when you return.

Choosing between them is mostly a matter of what you are actually up against — a chat that greys you out, or a tracker scoring ten-minute blocks.

Where Reaction fits

Reaction is a native Windows and Linux application rather than an extension, which is what lets it work at the layer a tracker actually reads. It moves the pointer along curves, varies the key rhythm, scrolls and switches windows, and does all of it only while the machine is genuinely idle.

The trade is plain and worth stating: it needs a desktop you can install software on, so it has nothing to offer a Chromebook. Where a Chrome extension is the only thing available, the honest advice is to expect page-level effects and nothing more.