AIHawk vs dots
The two are close in size: 32.3k stars for AIHawk, 32.3k for dots. Over the days we have tracked them AIHawk moved +6.6% and dots +3534.3%, so dots is growing faster right now.
AIHawk leads on model freedom. dots does not take any axis by a clear margin.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
Drives a real, patched Firefox browser over MCP or OpenRouter so the agent can click, type and read actual web pages for automation rather than relying on APIs or scraped data.
- Stars
- 32.3k
- Tracked growth
- +6.6%
- Maturity
- ●●●●●
- Last commit
- 5d ago
- Language
- TypeScript
- License
- MIT
- Cost to run
- Your OpenRouter API key or assistant-provided model
Provides a real, patched Firefox engine that presents a consistent, human-like fingerprint (no WebDriver flags) so the agent interacts with sites without obvious automation traces.
- Stars
- 32.3k
- Tracked growth
- +3534.3%
- Maturity
- ●●●●●
- Last commit
- 5d ago
- Language
- TypeScript
- License
- MIT
- Cost to run
- Your OpenRouter API key
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | AIHawk | dots |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● No repo access | ●●●●● Single page only |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● None mentioned | ●●●●● None mentioned |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Config & flags | ●●●●● CLI flags & options |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Cloud API key | ●●●●● Cloud via OpenRouter |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● OpenRouter / MCP | ●●●●● OpenRouter only |
Setup ease What it takes to get a first useful run out of it. | ●●●●● Config + API key | ●●●●● Install + API key |
Which one to pick
Pick AIHawk if…
Real browser automation — pick AIHawk when you need an agent that interacts with complex web pages (mouse, keyboard, real page rendering) and can integrate with your assistant or OpenRouter.
- Model freedom: OpenRouter / MCP (3/5 against 1/5)
Pick dots if…
Anti-detection browser — pick dots when you need a local agent that emulates a consistent human identity (screen, fonts, timezone, pointer events) and preserves profiles while using models via OpenRouter.
What people want from each one
Questions people ask
Is AIHawk better than dots?
AIHawk leads on model freedom. dots does not take any axis by a clear margin. AIHawk is worth picking when real browser automation — pick AIHawk when you need an agent that interacts with complex web pages (mouse, keyboard, real page rendering) and can integrate with your assistant or OpenRouter.
Which of AIHawk and dots keeps my code private?
AIHawk: Cloud API key (3/5). dots: Cloud via OpenRouter (3/5).
What does each one cost to run?
AIHawk: Your OpenRouter API key or assistant-provided model. dots: Your OpenRouter API key.
Full profiles: feder-cr/AIHawk and feder-cr/dots. Everything else in Browser agents.