Auto Clicker: Real Clicks & Sequences

Auto clicker that actually registers — even on canvas games and strict controls. Build a sequence, or record it once and replay it.

Most auto clickers have the same problem: the counter climbs, and the page never reacts. You set twenty clicks a second. You watch the number double, then double again, then climb past a thousand. On screen, nothing has moved. Not a rate you can tune your way out of — the clicks simply are not counting. The reason is dull but total. An ordinary extension can only fire synthetic events, and a synthetic event arrives with `isTrusted = false`. Games, click-speed tests, and any control that asks "was this a person?" throw those away on arrival. Every auto clicker that does not solve this has the same ceiling, no matter what its counter says. Precision Auto Clicker is built around that failure, and around a second one: nearly every auto clicker clicks one point. ── CLICKS THE PAGE ACTUALLY RECEIVES ── Two engines, chosen per sequence. Precise engine Sends input through Chrome's own input pipeline, so it arrives as genuine mouse input. These are the clicks that land on canvas and WebGL games, on click-speed tests, and on any control that rejects synthetic events. Light engine Dispatches a full pointer and mouse sequence from the page itself. No debugger attachment, no browser notice, and the right choice for ordinary forms and buttons — it manages several thousand presses a second. Both engines implement every step type, so switching never changes what a step does. If the precise engine cannot attach, the extension tells you instead of quietly doing nothing. ── A SEQUENCE, NOT ONE POINT ── Add up to 500 steps; they run in order, one after another, then loop. Four kinds: • Press / Hold — press one point and keep it down for its hold duration (0 means press and release together) • Swipe — drag from one point to another, along a real travel path • Scroll — turn the wheel at one point, up or down by the amount you set; a page with its own scroll area (or a map) scrolls that instead of the whole page • Follow cursor — ignores any stored point and acts wherever your mouse is at the moment the step runs Every step carries its own timing: • wait before this step (the editor shows the same number on the next step as "wait after previous", so the two can never disagree) • hold duration — how long the button stays down • random offset, so repeated presses are not pixel-identical • random delay, so the rhythm is not machine-perfect With every wait and hold at 0, the sequence runs as fast as the engine allows rather than being paced by the extension's own bookkeeping. ── OR SKIP THE BUILDING: RECORD IT ── This is the part that saves the most time, and the reason most people upgrade. Press Record. Do the thing once, by hand, at the pace you would really do it. Press stop. The steps are there — presses, swipes and scrolls, in order, at the coordinates you actually hit, with the pauses you actually took and the holds you actually held. Three things make it safe to leave running while you work: • Only your own input is recorded. Events a page or a script fires at itself are not gestures, and are ignored. • The toolbar, the panels and the markers are not recorded. Those are you talking to the extension, not to the page. • Nothing is recorded while a sequence is running, so a sequence can never quietly record itself into a loop. A recorded step is an ordinary step. Drag it, retime it, delete it, run it at full speed. Recording is a way to get a sequence, not a separate mode with separate rules. ── SEE IT, AND CHANGE IT, ON THE PAGE ── The step list shows every step, numbered, with its point and timing. Drag a row to reorder and the numbers follow. Right-click any row — or any marker — to open its parameters in a small window you can drag anywhere, which closes again when you click elsewhere. Each step is drawn on the page with its number beside it, clear of the exact point it acts on. Both ends of a swipe are draggable and move independently, so a gesture can be reshaped one end at a time. A scroll step shows its direction and amount under its marker. A follow-cursor step gets a dashed, pulsing marker of its own — nothing like the X that marks a fixed point — which can be dragged out of the way and leaves the point it acts on completely alone. Nothing that destroys work happens by accident: removing a step or a saved sequence needs Shift held, and the button changes colour while it is. Hover any toolbar button and a tooltip tells you what it does and which key is bound to it. No unlabelled mystery buttons, no wall of text on the page. ── A TOOLBAR THAT STAYS OUT OF THE WAY ── • drag it by any part of it — the buttons still work, because a press only becomes a drag once you actually move • it remembers where you put it • collapses to a slim bar, or hides entirely and comes back from the toolbar icon • live action counter and actions-per-second readout • markers can be hidden in one click, so you can see the page without them • while a sequence is running the markers stop intercepting the mouse, so your own clicks still work The play button responds the moment you press it, not when you release — which matters when a sequence is running at full speed and you want it to stop. ── SETTINGS LIVE ON THE PAGE ── There is no separate settings tab. Engine, loop behaviour, start delay, cycle limit, marker visibility, hotkey bindings and Pro activation all open in a small draggable window over the page you are working on, so you never lose your place. ── SAVE AND SHARE SEQUENCES ── Save the sequence you are working on with one press and no dialog; the saved list names it for you. Each saved sequence can be applied, overwritten with the steps you have now, shared, renamed (double-click its name) or deleted — and the two destructive ones need Shift held. Share it as a `PAC-` code: the whole sequence travels inside the code, so it works on a machine that has never spoken to ours, and it imports the same sequence on the other end. Or export a `.pac` file (plain JSON inside) and import it anywhere. A file that is not one of ours is refused with a reason instead of half-loading. ── HOTKEYS THAT DO NOT FIGHT YOUR KEYBOARD ── Bind start/stop and add-step to whatever you like, including bare function keys. Ordinary keys require a modifier, so the extension never swallows your typing, and hotkeys are ignored while you are in a text field. Rebinding takes effect immediately on pages that are already open. ── OFF MEANS OFF ── The power switch at the top of the popup turns the extension off. Off here means off: the content script is unregistered, so pages loaded afterwards do not load it at all — no toolbar, no markers, no mouse tracking, nothing parsed into the page. On a page that already had it, turning the switch off removes the toolbar it drew and detaches every listener it attached, including the mousemove and scroll handlers that otherwise run on every pointer movement and every scroll. There is no "off but still watching". Turn it back on and it returns immediately in every tab you already have open — no reload, no restart. ── ONE THING WORTH KNOWING FIRST ── Automating clicks is fine wherever the site allows it, but it can break the rules of competitive or multiplayer games and cost you the account — check the rules of the game you have in mind before you point it at one. ── FREE, AND WHAT PRO ADDS ── Free, permanently: every step type, both engines, up to 500 steps in a sequence, hotkeys, the full marker and list editor, three saved sequences, and sharing. No click quota, no time limit, no nag screen. Try Pro for the first day. Recording, page-anchored points and the auto-stop timer are switched on for the first 24 hours after you install, so you can find out for yourself whether recording replaces the part you find slow. When that day ends the three switch off again and what they produced is removed: sequences you recorded, the points you anchored, and saved sequences past the free three. Steps you placed by hand, and those three saved sequences, are not touched. The countdown and the list of what will be removed are both shown in the settings window — nothing here happens quietly. What the free version does not do is build the sequence for you. You place the points, you set the timings, and for a routine you already know by hand that is the slow part. Pro adds: • Recording — do it once by hand and get the steps, with your own timings already on them • Agent Link — let an AI agent on your own computer (Claude, Cursor, any MCP client) find buttons on the page, build the sequence and run it for you • 50 saved sequences instead of three • an auto-stop timer, to end a long session after a set number of minutes • every future update ── AGENT LINK: LET AN AI BUILD IT ── Switch on Agent Link in the popup and run the small bridge program on your computer. The popup shows a pairing code; give it to your agent. From then on the agent can list the buttons on the page with their exact positions, build a sequence from them, run it, and read the log when something does not land. A bar on the page shows while an agent is connected, with a Disconnect button. It connects only to your own computer (127.0.0.1) — nothing goes to any server. On a Chromebook the start/stop key is Alt+Z and add-a-step is Alt+X, because the top row has no F6 or F7. Two ways to pay, for exactly the same features: • Once — $15, and it never expires • Subscription — $5 every 3 months, cancel any time There is one build, so a subscriber does not get a different feature set from someone who paid once; the difference is only whether it ends. Nine months of subscription costs the same as buying once, so past that point the one-off is the cheaper of the two — and it is the one that never bills you again. Refunds: 14 days, no questions asked. If it does not do what this page describes, say what did not work and you get your money back. ── PRIVACY ── The extension collects nothing. No analytics, no accounts. Your settings, steps and saved sequences are stored locally in your browser and never leave your device. If you never enter a licence, it makes no network requests at all — except the optional Agent Link, which talks only to a program on your own computer (127.0.0.1), never to a server. Two things worth being precise about, because a licence is involved: • A one-off licence is verified on your machine — it is a signed key, and the signature is the proof. It contacts our licence server once, when you first enter it, and never again. The reason is that a key which could be verified entirely offline also could not be limited to a device, so one buyer could publish theirs and anyone could use it; a one-off licence works on three devices, and counting them needs the server. The only things sent are the key and a random identifier for your browser profile, generated by the extension and derived from nothing about your machine. After that one exchange it works offline forever, and a failed attempt uses nothing up. • A subscription is checked against our payment provider about once a week, since only they know whether it is still being paid for. That check sends nothing but the key itself, and if it cannot go through, the subscription keeps working for two more weeks — being offline or behind a firewall will never switch off something you paid for. • The buy buttons open the store in a new tab. That happens only when you click it, and the extension itself sends nothing. Permissions, and why each one exists: • Read and change your data on all websites — the toolbar has to appear on whichever page you want to click on, and the light engine dispatches events into that page. The extension does not read page content. • Access the page debugger backend — used only while the precise engine is running, so mouse input can be generated through Chrome's input pipeline. Chrome attaches it when you start and detaches it when you stop, and Chrome's own "debugging this browser" notice is visible during that time. Use the light engine if you would rather that notice never appears. • Storage — to remember your settings, steps and saved sequences. • Scripting — to place the toolbar on a page that was already open when the extension was installed.