--- title: "browser-use vs chatwiki" type: "comparison" canonical_url: "https://www.graphcanon.com/compare/browser-use-browser-use-vs-zhimaai-chatwiki" tools: ["browser-use-browser-use", "zhimaai-chatwiki"] --- # browser-use vs chatwiki *GraphCanon updated Sep 20, 2026* ## 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. [browser-use](https://browser-use.com) reports 115k GitHub stars, 13k forks, and 439 open issues, last pushed Sep 15, 2026. [chatwiki](https://chatwiki.ai) has 2.1k stars, 324 forks, and 6 open issues, last pushed Sep 4, 2026. Figures are from public GitHub metadata via [browser-use's repository](https://github.com/browser-use/browser-use) and [chatwiki's repository](https://github.com/zhimaAi/chatwiki). | | [browser-use](/tools/browser-use-browser-use.md) | [chatwiki](/tools/zhimaai-chatwiki.md) | | --- | --- | --- | | Tagline | Agents that use the browser | AI knowledge base workflow Agent platform for RAG-based AI customer service robots | | Stars | 115,057 | 2,078 | | Forks | 12,667 | 324 | | Open issues | 439 | 6 | | Language | Python | Vue | | Adopt for | browser-use is a Python-based repository for AI agents designed for browser automation using Playwright. | ChatWiki specializes in deployment via Docker and offers a workflow management system for AI customer service robots using Vue. | | Persona | - | - | | Runtime | - | - | | License | MIT | Other | | Categories | AI Agents, Developer Tools | AI Agents, Evaluation & Observability | ## Trust and health _Sourced signals - not a safety guarantee. No winner column._ | | [browser-use](/tools/browser-use-browser-use.md) | [chatwiki](/tools/zhimaai-chatwiki.md) | | --- | --- | --- | | Maintenance | Very active (96%) | Active (82%) | | Days since push | 2d | 13d | | Open issues (now) | 439 | 6 | | Stars delta | +5.7k (30d) | +40 (30d) | | Open issues delta | +82 (30d) | +2 (30d) | | Full report | [trust report](/tools/browser-use-browser-use/trust.md) | [trust report](/tools/zhimaai-chatwiki/trust.md) | ## Decision facts: browser-use - **Adopt for:** browser-use is a Python-based repository for AI agents designed for browser automation using Playwright. ## Decision facts: chatwiki - **Adopt for:** ChatWiki specializes in deployment via Docker and offers a workflow management system for AI customer service robots using Vue. ## Choose when ### 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. ### 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 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 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 ## 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](/tools/browser-use-browser-use/alternatives) and [chatwiki alternatives](/tools/zhimaai-chatwiki/alternatives) ([browser-use markdown twin](/tools/browser-use-browser-use/alternatives.md), [chatwiki markdown twin](/tools/zhimaai-chatwiki/alternatives.md)), 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](/compare/browser-use-browser-use-vs-zhimaai-chatwiki.md) 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](/tools/browser-use-browser-use/trust); [chatwiki trust report](/tools/zhimaai-chatwiki/trust). --- **Machine-readable endpoints** - JSON: [`/api/graphcanon/graph?tool=browser-use-browser-use`](/api/graphcanon/graph?tool=browser-use-browser-use) - LLM index: [/llms.txt](/llms.txt) - Full corpus: [/llms-full.txt](/llms-full.txt) _GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_