An Auto-clicker with a few advanced features and generally better performance than popular alternatives. Made for windows.
1.8k
Stars
120
Forks
52
Open issues
18
Contributors
AI Analysis
Blur Auto Clicker is a Windows-focused automation tool that performs mouse clicks at user-specified rates with claimed accuracy advantages over competitors. It serves a specialized niche of users requiring precise automated clicking for gaming, testing, or repetitive tasks, and is not a general-purpose application suitable for typical desktop users.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Windows auto-clicker with sub-second timing accuracy, gaining traction among power users six months after launch
Blur Auto Clicker is a Windows-only automation tool that performs mouse clicks and keyboard presses at user-specified rates (up to 500 CPS). It targets users frustrated with timing inconsistency in older auto-clickers—the core claim is that it reliably hits the speed you set, rather than drifting. Built in TypeScript using Tauri and Webview2, it offers both simple and advanced modes. Adoption appears concentrated in gaming and testing communities; the project is very young (created Dec 2025, only 6 months old) but shows active development and steady early growth.
Created December 2025 by Blur009, this is a recent entrant to a crowded auto-clicker space dominated by much older projects (AutoHotkey from 2003, KeymouseGo from 2016). The project explicitly positions itself as a performance alternative, addressing the specific complaint that existing tools don't maintain consistent CPS at high speeds.
1,736 stars in 6 months is rapid for a specialized automation tool. 55 stars in the last 7 days (as of 2026-06-29) suggests sustained interest. Growth appears driven by word-of-mouth in gaming/clicking communities (evidenced by Discord link in README) and technical appeal of the timing-accuracy pitch. However, absolute numbers remain modest relative to established competitors.
Adoption not verified at enterprise or large-scale level. Evidence suggests hobbyist/enthusiast adoption: Discord community link present (indicates some user congregation), GitHub download badge shown but specific count not provided in metadata. User base appears to be clicking-game players, test automation hobbyists, and users dissatisfied with legacy tools. No documentation of corporate use, integration into larger workflows, or testimonials from recognizable organizations.
Appears to be a Tauri-based desktop application (mentioned Webview2 RAM usage of ~100–200 MB). TypeScript codebase with separate Simple and Advanced UI modes. Based on README, likely uses platform-level mouse event APIs and system timer resolution management to achieve timing control. Build instructions exist (referenced BUILDING.md), suggesting professional structure; however, source code inspection not possible from metadata alone.
Not documented in README. No mention of automated testing, CI/CD pipelines, or test suite structure.
Last push 2026-06-28 (one day before evaluation date) indicates active, ongoing development. Repository is only 6 months old, so 'maturity' is not yet established, but the cadence appears healthy. Presence of CONTRIBUTING.md and BUILDING.md suggests maintainer interest in managing external input. Project is still pre-1.0 conceptually (v3.0.0 exists but project born in Dec 2025), so rapid iteration is expected.
ADOPT IF: you need reliable high-speed (200–500 CPS) clicking on Windows, value timing consistency over breadth of features, and are willing to accept a young project with limited ecosystem maturity. AVOID IF: you need cross-platform support, scripting-language integration, or require battle-tested stability in mission-critical workflows. MONITOR IF: you are evaluating for team/enterprise use—adoption patterns and stability track record need more time to establish before committing to this project for organizational purposes.
Independent dimensions
Mainstream potential
3/10
Technical importance
5/10
Adoption evidence
4/10
- Project is only 6 months old; long-term maintenance commitment unclear. Single maintainer visible (Blur009); bus factor is high.
- Unsigned installer triggers Windows SmartScreen warnings, creating friction for users not comfortable with security dialogs.
- Webview2 runtime dependency adds ~100–200 MB baseline memory and creates distribution/update complexity; not ideal for resource-constrained environments.
- CPS cap of 500 is artificial ceiling (Windows limit ~800); power users may hit this constraint quickly.
- No documented test coverage or CI/CD evidence; code quality and regression testing rigor unknown.
Likely to remain a viable niche tool for Windows clicking enthusiasts, with slow steady growth if maintainer continues active development. Risk of maintenance lapse if Blur009 loses interest (typical for young solo projects). Unlikely to displace AutoHotkey or KeymouseGo due to narrower scope and youth, but may consolidate a small but engaged user base around the timing-accuracy value proposition.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://autoclicker.blur009.com
- Language
- TypeScript
- License
- GPL-3.0
- Last updated
- 2d ago
- Created
- 7mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Top contributors
Similar repos
Nain57/Smart-AutoClicker
Klick'r is an open-source Android automation tool that uses image detection to...
taojy123/KeymouseGo
KeymouseGo is a lightweight Python-based desktop automation tool that records...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
Blur009/Blur-AutoClicker
this
|
1.8k | +42 | TypeScript | 7/10 | 2d ago |
|
Nain57/Smart-AutoClicker
|
3.5k | — | Kotlin | 7/10 | 23h ago |
 farzaa/clicky
|
7k | — | Swift | 7/10 | 2mo ago |
|
taojy123/KeymouseGo
|
10.4k | — | Python | 7/10 | 1mo ago |
 Xetera/ghost-cursor
|
1.6k | — | TypeScript | 7/10 | 2d ago |
 game1024/OpenSpeedy
|
16.5k | — | TypeScript | 7/10 | 2d ago |
Much older, larger ecosystem, supports Windows/Linux/macOS, scripting language-based, vastly larger community. Blur is Windows-only, GUI-first, and claims better timing accuracy at high CPS. AutoHotkey is more general-purpose; Blur is specialist.
Older, cross-platform (Windows/macOS/Linux), record-and-replay paradigm. Blur offers real-time control, explicit CPS tuning, and claims superior speed consistency. KeymouseGo broader in scope; Blur narrower but deeper on timing.
Android-focused, visual automation framework. Different platform entirely; not a direct competitor but illustrates fragmentation of auto-clicker category across OSes.
JavaScript library for browser automation, not a standalone tool. Different use case (web scraping / browser testing vs. desktop clicking). Similar stars to Blur but fundamentally different category.
