MacroX started with a simple frustration: too much time spent doing the same browser actions over and over — filling the same forms, clicking through the same UI flows, entering the same data in the same fields, day after day.
Existing solutions were either too technical (Selenium, Playwright), too expensive, or too clunky. MacroX is the browser automation tool that should have always existed: point, click record, done.
MacroX injects a lightweight content script (recorder.js) into the active browser tab when you start recording. It listens for DOM events — clicks, key presses, scroll, input changes — and stores them as a timestamped event log in chrome.storage.local.
During playback, the event log is replayed by dispatching the same events back to the page in the correct order, with the correct timing, scaled to your chosen speed. A visual cursor overlay shows you exactly what's happening.
Navigation-safe playback is handled by the background service worker: when a macro triggers a page navigation, the background detects the new page load and resumes playback from the correct event index — seamlessly continuing the macro across page boundaries.
MacroX requests only the permissions it genuinely needs:
| Permission | Why it's needed |
|---|---|
| storage | Save macros, hotkeys, and settings locally on your device. Nothing leaves your browser. |
| activeTab | Access the tab you're currently recording or replaying on. |
| scripting | Inject the recorder script into a tab when you press Record (required for tabs opened before the extension was installed). |
| sidePanel | Render the MacroX UI in Chrome's native side panel — so you can manage macros without leaving the page you're working on. |
| tabs | Identify the active tab, resume playback after cross-page navigation, and open the upgrade page. |
| <all_urls> | MacroX must work on any site you choose to automate. The extension cannot know in advance which sites you'll use — this permission is fundamental to its core purpose. |
MacroX was designed with a strict principle: your data never leaves your device.
chrome.storage.local — on your machine, in your browser→ Read the full Privacy Policy
chrome://) and the Chrome Web Store itself are blocked by browser security policy, but everywhere else is fair game.<input type="password"> field. Password values are never captured or stored.storage.local API. Uninstalling the extension removes all stored data.