This is a local (desktop) automation tool you run on Windows. It bundles several utilities: an auto-writer (types messages), an auto-clicker (region or point clicks), hotkeys, a scheduler, Python-based custom scripts, macro recording, plugins scanning, and a small dashboard. The app is designed to run offline, keep settings & logs on your machine, and prioritize user control.
Settings, logs, themes and macros are stored locally on your PC.
Run small Python scripts for flexible automation (script sandboxing & safety discussed below).
Plugins are scanned for suspicious keywords before being loaded; the UI provides a safe scan mode.
Type a list of messages, configure per-character delays, and send them automatically. Supports patterns (placeholders like index or timestamp), randomized delays, and previewing typed output in the UI.
Target a screen region (drag-to-select) or a single point. Supports clicks-per-second, burst modes, total click limits, and in-app simulation preview so you can test without performing system clicks during previews.
Bind global or app-level hotkeys to start/stop features, toggle profiles, run scripts, or trigger macros. Supports modifier keys and user-configurable bindings.
Run tasks at times (HH:MM) or recurring patterns. The scheduler can start scripts or built-in tasks in the background and keeps logs of executions.
Record high-level user actions to a macro file, save as JSON, and replay later. Useful for repeatable multi-step desktop flows.
Scans third-party plugin files for suspicious tokens and gives a warning if risky patterns are found. The app flags potential issues rather than silently executing unknown code.
The application is a desktop GUI program that stores configuration and state locally. It has multiple component folders (themes, plugins, macros) and uses local files to persist user data. Most features run in background threads so the UI remains responsive. A small script runner executes Python scripts; optional libraries may be used for input automation (e.g., simulating keypresses and mouse clicks) only if present.
On first run the application requires the user to accept a Terms of Use dialog. The terms emphasize responsible usage: you must only automate tasks on systems you own or have permission for. The app includes a local ban/warning mechanism tied to a device identifier; repeated policy violations can mark a device as banned in the local ban DB. Administrators can inspect and manage warnings locally (there is a developer tools view for authorized developer HWIDs).
By design the app stores settings and logs on the local machine. Nothing is uploaded to remote servers by default — there is no cloud telemetry unless the user explicitly enables error reporting or sharing.
A: The desktop build described here is distributed free in the current state. Check the installer page for version details and any licensing notes.
A: No — by default it stores files and logs locally. Any network calls would require explicit opt-in or custom scripts with network code.
A: The app scans plugin files for suspicious keywords and either flags them or refuses to load them automatically. It also logs a warning locally.
A: The app issues warnings to a device identifier if various policy checks are triggered. Warnings accumulate locally; repeated infractions can mark a device as banned inside the local ban DB. Developer HWIDs are whitelisted for development and testing flows.
A: Some features rely on optional libraries for simulating keyboard/mouse events and charting. If those are missing the app falls back to preview or disables those specific features and informs you.
Questions, bug reports, or requests — the project has a contact point listed below. For privacy and security concerns, include logs and environment information when you request support.