Comparison
browser-use vs chatwiki
Verdict
Pick browser-use if browser-use is a Python-based repository for AI agents designed for browser automation using Playwright; pick chatwiki if chatWiki specializes in deployment via Docker and offers a workflow management system for AI customer service robots using Vue.
Markdown twin · browser-use alternatives · chatwiki alternatives
GraphCanon updated Sep 18, 2026
8views this month
vs
Trust & integrity
| Signal | browser-use | chatwiki |
|---|---|---|
| Maintenance | Very active (2d since push) As of Sep 18, 2026 · github_public_v1 | Active (13d since push) As of Sep 17, 2026 · github_public_v1 |
| Provenance | Not a fork · Organization account As of Sep 18, 2026 · github_public_v1 | Not a fork · Organization account As of Sep 17, 2026 · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of Sep 18, 2026 · osv@v1 | Published findings As of Jul 15, 2026 · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- browser-use
- Agents that use the browser
- chatwiki
- AI knowledge base workflow Agent platform for RAG-based AI customer service robots
Stars
- browser-use
- 115k
- chatwiki
- 2.1k
Forks
- browser-use
- 13k
- chatwiki
- 324
Open issues
- browser-use
- 439
- chatwiki
- 6
Language
- browser-use
- Python
- chatwiki
- Vue
Adopt for
- browser-use
- browser-use is a Python-based repository for AI agents designed for browser automation using Playwright.
- chatwiki
- ChatWiki specializes in deployment via Docker and offers a workflow management system for AI customer service robots using Vue.
Persona
- browser-use
- -
- chatwiki
- -
Runtime
- browser-use
- -
- chatwiki
- -
License
- browser-use
- MIT
- chatwiki
- Other
Last pushed
- browser-use
- Sep 15, 2026
- chatwiki
- Sep 4, 2026
Categories
- browser-use
- AI Agents, Developer Tools
- chatwiki
- AI Agents, Evaluation & Observability
Trust and health
Maintenance
- browser-use
- Very active (96%)
- chatwiki
- Active (82%)
Days since push
- browser-use
- 2d
- chatwiki
- 13d
Open issues (now)
- browser-use
- 439
- chatwiki
- 6
Stars delta
- browser-use
- +5.7k (30d)
- chatwiki
- +40 (30d)
Open issues delta
- browser-use
- +82 (30d)
- chatwiki
- +2 (30d)
OSV dependency advisories
- browser-use
- No lockfile (source not queried)
- chatwiki
- Published findings
Full report
- browser-use
- Trust report
- chatwiki
- Trust report
Choose browser-use if…
- browser-use is primarily Python; chatwiki is Vue.
- License: browser-use is MIT, chatwiki is Other.
- Tags unique to browser-use: ai-agents, ai-tools, browser-automation, playwright.
- Also covers Developer Tools.
- browser-use ships Docker support for self-hosted deployment.
- When you need to automate browser actions with AI agents and prefer using Playwright for its robust capabilities in handling modern web applications.
When NOT to use browser-use
- If your project requires a different browser automation tool that is not Playwright, as browser-use is specifically tailored for Playwright integration.
- When detailed documentation and integrations provided by browser-use do not align with your project's specific needs or if you prefer a more generalized approach to browser automation.
Choose chatwiki if…
- chatwiki is primarily Vue; browser-use is Python.
- License: chatwiki is Other, browser-use is MIT.
- Tags unique to chatwiki: agent, ai, automation, rag.
- Also covers Evaluation & Observability.
- When you need an end-to-end workflow management system that is deployable with Docker
When NOT to use chatwiki
- Avoid if your project requires modification or removal of the 'ChatWiki' branding on frontend elements without a commercial license
- Not suitable for organizations that cannot comply with or afford additional restrictions specified in the ChatWiki Open Source License
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 Sep 18, 2026
- GitHub forks (browser-use/browser-use) · observed Sep 18, 2026
- Last push (browser-use/browser-use) · observed Sep 15, 2026
- License file (MIT) · observed Sep 18, 2026
- Decision facts (enrichment) · observed Sep 18, 2026
- Trust scan (lockfile / OSV) · observed Sep 18, 2026
- GitHub stars (zhimaAi/chatwiki) · observed Sep 17, 2026
- GitHub forks (zhimaAi/chatwiki) · observed Sep 17, 2026
- Last push (zhimaAi/chatwiki) · observed Sep 4, 2026
- License file (Other) · observed Sep 17, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 15, 2026
GitHub stars on cards: browser-use 115k · chatwiki 2.1k (synced Sep 18, 2026).
Common questions
- What is the difference between browser-use and chatwiki?
- browser-use: Agents that use the browser. chatwiki: AI knowledge base workflow Agent platform for RAG-based AI customer service robots. See the comparison table for live GitHub stats and shared categories.
- When should I choose browser-use over chatwiki?
- Choose browser-use over chatwiki when browser-use is primarily Python; chatwiki is Vue; License: browser-use is MIT, chatwiki is Other; Tags unique to browser-use: ai-agents, ai-tools, browser-automation, playwright; Also covers Developer Tools; browser-use ships Docker support for self-hosted deployment; When you need to automate browser actions with AI agents and prefer using Playwright for its robust capabilities in handling modern web applications.
- When should I choose chatwiki over browser-use?
- Choose chatwiki over browser-use when chatwiki is primarily Vue; browser-use is Python; License: chatwiki is Other, browser-use is MIT; Tags unique to chatwiki: agent, ai, automation, rag; Also covers Evaluation & Observability; When you need an end-to-end workflow management system that is deployable with Docker.
- When should I avoid browser-use?
- If your project requires a different browser automation tool that is not Playwright, as browser-use is specifically tailored for Playwright integration. When detailed documentation and integrations provided by browser-use do not align with your project's specific needs or if you prefer a more generalized approach to browser automation.
- When should I avoid chatwiki?
- Avoid if your project requires modification or removal of the 'ChatWiki' branding on frontend elements without a commercial license Not suitable for organizations that cannot comply with or afford additional restrictions specified in the ChatWiki Open Source License
- Is browser-use or chatwiki more popular on GitHub?
- browser-use has more GitHub stars (115,057 vs 2,078). Stars measure visibility, not whether either tool fits your constraints.
- Are browser-use and chatwiki open source?
- Yes - both are open-source projects on GitHub (browser-use: MIT, chatwiki: Other).
- Where can I find alternatives to browser-use or chatwiki?
- GraphCanon lists graph-backed alternatives at browser-use alternatives and chatwiki alternatives (browser-use markdown twin, chatwiki 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 chatwiki?
- browser-use: Very active. chatwiki: 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 chatwiki?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: browser-use trust report; chatwiki trust report.