Hardware vs software mouse jiggler: which one gets caught

Why 'hardware or software' is the wrong first question

People sort mouse jigglers by their carrier because that is the visible difference: one is a physical device, one is a program, one lives in a browser. That split matters for how you set the thing up, whether it needs admin rights, and whether IT can see it — all real concerns we come back to below. It just is not the split a tracker cares about.

A time tracker sits on the operating system's input layer. It sees that a mouse-move event arrived, that a key went down, that the active window changed — and nothing about the origin of any of it. From that vantage a hardwired dongle and a well-behaved app are indistinguishable in principle; what separates them in practice is the shape of the input each one produces. That shape is the whole story of this article.

The USB dongle: nothing installed, one fixed motion

A dongle plugs into a USB port and physically nudges the mouse — or sits under it as a small motorised pad — so the operating system reads an ordinary pointing device. Nothing is installed, no administrator rights are needed, and it works the same on a locked-down laptop as on a home machine. For a lot of people that zero-install property is the entire appeal.

The trade-off is that the motion is hardwired and blind. The dongle repeats one path at one cadence for as long as it is plugged in, with no idea what is on screen, whether a call is happening, or whether you have come back to the desk. It never clicks, never types, and never switches windows, because it has no way to. Over ten minutes that looks like input; over a full day it looks like exactly what it is.

• No install and no admin rights — works on a managed laptop.
• One repeating path at a fixed cadence, for hours.
• No clicks, no keystrokes, no window changes — ever.
• Endpoint policies may still log an unknown USB device.

The desktop app: a pattern you can shape

Software has to be installed, which on a managed laptop is a genuine limitation and sometimes a hard stop. What you get in exchange is control over the shape of the input. A well-built presence app can vary the trajectory and speed of the cursor, follow curved rather than dead-straight paths, mix in navigation keys and scrolling, and switch between windows — the small irregularities that make input read as a person rather than a motor.

It can also be aware of context in a way no dongle can. Reaction, for example, starts only when the computer is genuinely idle and steps aside the instant you touch the mouse, and it holds a natural level of presence inside a range you set instead of one repeating motion. That awareness — knowing when to act and when to disappear — is the practical difference between hardware and software, far more than the install itself.

The browser-tab mover: free, but only while focused

Online mouse movers are the lightest option of all: open a page, and the tab drives the cursor with no download and no install. For keeping a single screen awake while you read on the same tab, they do the job.

The limit is focus. A browser tab can only move the cursor while it is the active, foreground tab, so the moment you switch to a document, a video call, or another app, the motion stops — and that quiet stretch away from the browser is precisely the window a tracker is measuring. As a presence tool it covers the least useful part of the day and goes silent for the rest.

What the tracker actually records

No mainstream tracker inspects whether a movement came from a USB device or a running process. It stores input events — moves, clicks, scrolls, keystrokes — together with the active window and, on many tools, a periodic screenshot. That is the entire evidence base, and it is identical whether the input was hardware or software in origin.

Which is why the carrier is a red herring and the pattern is everything. Evenly spaced events, an unchanging path, movement with no clicks anywhere near it, and a window that never changes all read the same regardless of what produced them. A jiggler gets noticed not because it is a dongle or an app, but because its output is too regular to be a hand.

• Input events: moves, clicks, scrolls and keystrokes.
• The active window, and often a periodic screenshot.
• Not the device or process that produced the input.

Why a mechanical pattern is what gives it away

The signals that draw a second look are all about regularity. Identical gaps between events, a cursor that traces the same short segment over and over, hours of movement without a single click, and an active window frozen on one app are the fingerprints of a machine, not a person. A dongle produces all four by design; a crude script produces most of them; a careful app avoids them by varying its behaviour.

This is also why a flat, maximal line is more suspicious than a modest one. Real work has pauses and bursts built in, so a report pinned at the top of the scale for hours reads as automation, whereas an uneven mid-range line reads as a person. The full mechanics of what pattern-based detection looks for are covered in the detection write-up in the related links.

The managed-laptop reality: admin rights and USB policy

Away from patterns, there is a purely practical axis: what your machine will even allow. A dongle needs a free USB port and nothing else, but endpoint-security tools on corporate machines can log or block unknown USB devices, so 'nothing installed' does not always mean 'nothing seen'. An app needs a normal install, which some managed laptops restrict outright, and a browser mover needs only a browser but pays for it in coverage.

Weigh those constraints honestly against how you actually work. If you cannot install software, a browser tab or a dongle may be all that is available; if you can, an app is the only option of the three that can vary its behaviour and respond to whether you are actually there.

• Dongle: any free USB port, but may trip endpoint USB policy.
• App: needs install rights some managed laptops withhold.
• Browser mover: no install, but stops the moment the tab loses focus.

Where Reaction fits

Reaction is the software option, and it is built for one narrow job: the stretches when you step away from the keyboard but the session should stay alive — the coffee, the stretch, the school run. Instead of one hardwired motion it keeps a natural, human-like level of presence inside a range you set, using varied cursor paths, a living keyboard rhythm, occasional scrolling and window switches.

Crucially, it runs only while the machine is genuinely idle and stops the moment you touch the mouse, so it fills real breaks rather than sitting on top of your work. It cannot make low-input work look like high-input work while you are actually at the desk — that is a limit of the metric, not a feature — and it is meant to be used within your agreements; see the acceptable-use note below.