Comparison
browser-use vs llm-wiki-agent
Verdict
Pick browser-use when pricing: This tool is provided under the MIT license which means you can use it freely but there are no guarantees or formal support unless included in separate agreements.; pick llm-wiki-agent when tags unique to llm-wiki-agent: ai-agent, automation, claude-code, codex.
Markdown twin · browser-use alternatives · llm-wiki-agent alternatives
GraphCanon updated today
vs
Trust & integrity
| Signal | browser-use | llm-wiki-agent |
|---|---|---|
| Maintenance | Very active (0d since push) As of 1d · github_public_v1 | Very active (0d since push) As of 1d · github_public_v1 |
| Provenance | Not a fork · Organization account As of 1d · github_public_v1 | Not a fork · Organization account As of 1d · github_public_v1 |
| Security (OSV) | No lockfile As of 1d · none | No criticals As of 1d · osv@v1 |
Tagline
- browser-use
- Make websites accessible for AI agents. Automate tasks online with ease.
- llm-wiki-agent
- A personal knowledge base that builds and maintains itself. Drop in sources — Claude (or Codex/Gemini) reads them, extracts knowledge, and maintains a persistent interlinked wiki. Works with Claude Co
Stars
- browser-use
- 104k
- llm-wiki-agent
- 3.2k
Forks
- browser-use
- 11k
- llm-wiki-agent
- 368
Open issues
- browser-use
- 296
- llm-wiki-agent
- 2
Language
- browser-use
- Python
- llm-wiki-agent
- Python
Adopt for
- browser-use
- browser-use is a Python-based toolset that facilitates web task automation and enhances website interaction accessibility for AI agents using browser automation techniques.
- llm-wiki-agent
- -
Persona
- browser-use
- -
- llm-wiki-agent
- -
Runtime
- browser-use
- -
- llm-wiki-agent
- -
License
- browser-use
- The MIT License provides great flexibility and permissiveness for both open-source and proprietary software projects.
- llm-wiki-agent
- MIT
Last pushed
- browser-use
- Jul 11, 2026
- llm-wiki-agent
- Jul 11, 2026
Categories
- browser-use
- AI Agents, Developer Tools
- llm-wiki-agent
- AI Agents, Developer Tools, LLM Frameworks
Trust and health
Open issues (now)
- browser-use
- 296
- llm-wiki-agent
- 2
Security scan
- browser-use
- No lockfile
- llm-wiki-agent
- No criticals
Full report
- browser-use
- Trust report
- llm-wiki-agent
- Trust report
Choose browser-use if…
- Pricing: This tool is provided under the MIT license which means you can use it freely but there are no guarantees or formal support unless included in separate agreements..
- Requirements: Min 2 GB RAM; Requires Docker; Playwright installation and configuration needed for full functionality..
- Tags unique to browser-use: ai-agents, browser-automation, llm, playwright.
- When you need to automate interactions with websites in a straightforward manner, especially if your use case already leverages Playwright under the hood.
When NOT to use browser-use
- Avoid using browser-use if your automation workflow requires features that are exclusive to a different framework or library, such as specific functionalities only available in Selenium, as browseruse
Choose llm-wiki-agent if…
- Tags unique to llm-wiki-agent: ai-agent, automation, claude-code, codex.
- Also covers LLM Frameworks.
- Leaner open-issue backlog (2).
When NOT to use llm-wiki-agent
- AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism.
- Developer Tools: A gateway is overkill when you're pinned to a single provider and model.
- LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (browser-use/browser-use) · observed Jul 11, 2026
- GitHub forks (browser-use/browser-use) · observed Jul 11, 2026
- Last push (browser-use/browser-use) · observed Jul 11, 2026
- License file (MIT) · observed Jul 11, 2026
- Decision facts (enrichment) · observed Jul 11, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- GitHub stars (SamurAIGPT/llm-wiki-agent) · observed Jul 11, 2026
- GitHub forks (SamurAIGPT/llm-wiki-agent) · observed Jul 11, 2026
- Last push (SamurAIGPT/llm-wiki-agent) · observed Jul 11, 2026
- License file (MIT) · observed Jul 11, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: browser-use 104k · llm-wiki-agent 3.2k (synced Jul 11, 2026).
Common questions
- What is the difference between browser-use and llm-wiki-agent?
- browser-use: Make websites accessible for AI agents. Automate tasks online with ease.. llm-wiki-agent: A personal knowledge base that builds and maintains itself. Drop in sources — Claude (or Codex/Gemini) reads them, extracts knowledge, and maintains a persistent interlinked wiki. Works with Claude Co. See the comparison table for live GitHub stats and shared categories.
- When should I choose browser-use over llm-wiki-agent?
- Choose browser-use over llm-wiki-agent when Pricing: This tool is provided under the MIT license which means you can use it freely but there are no guarantees or formal support unless included in separate agreements.; Requirements: Min 2 GB RAM; Requires Docker; Playwright installation and configuration needed for full functionality.; Tags unique to browser-use: ai-agents, browser-automation, llm, playwright; When you need to automate interactions with websites in a straightforward manner, especially if your use case already leverages Playwright under the hood.
- When should I choose llm-wiki-agent over browser-use?
- Choose llm-wiki-agent over browser-use when Tags unique to llm-wiki-agent: ai-agent, automation, claude-code, codex; Also covers LLM Frameworks; Leaner open-issue backlog (2).
- When should I avoid browser-use?
- Avoid using browser-use if your automation workflow requires features that are exclusive to a different framework or library, such as specific functionalities only available in Selenium, as browseruse
- When should I avoid llm-wiki-agent?
- AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism. Developer Tools: A gateway is overkill when you're pinned to a single provider and model. LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves.
- Is browser-use or llm-wiki-agent more popular on GitHub?
- browser-use has more GitHub stars (104,191 vs 3,182). Stars measure visibility, not whether either tool fits your constraints.
- Are browser-use and llm-wiki-agent open source?
- Yes - both are open-source projects on GitHub (browser-use: MIT, llm-wiki-agent: MIT).
- Where can I find alternatives to browser-use or llm-wiki-agent?
- GraphCanon lists graph-backed alternatives at browser-use alternatives and llm-wiki-agent alternatives (browser-use markdown twin, llm-wiki-agent markdown twin), ranked by typed relationship edges rather than popularity votes.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, browser-use or llm-wiki-agent?
- browser-use: Very active. llm-wiki-agent: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for browser-use and llm-wiki-agent?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: browser-use trust report; llm-wiki-agent trust report.