--- title: "automa vs page-assist" type: "comparison" canonical_url: "https://www.graphcanon.com/compare/automaapp-automa-vs-n4ze3m-page-assist" tools: ["automaapp-automa", "n4ze3m-page-assist"] --- # automa vs page-assist *GraphCanon updated Sep 20, 2026* ## Verdict Pick automa if automa is known for its ease of implementation and browser agnostic design enabling users to streamline tasks on multiple platforms; pick page-assist if a Chrome and Firefox extension enabling local AI model-assisted web browsing, built with TypeScript under an MIT license and requiring Bun for development. [automa](https://www.goautoma.com/extension) reports 22k GitHub stars, 2.3k forks, and 377 open issues, last pushed Mar 2, 2026. [page-assist](https://chromewebstore.google.com/detail/page-assist-a-web-ui-for/jfgfiigpkhlkbnfnbobbkinehhfdhndo) has 8.2k stars, 784 forks, and 364 open issues, last pushed Sep 19, 2026. Figures are from public GitHub metadata via [automa's repository](https://github.com/AutomaApp/automa) and [page-assist's repository](https://github.com/n4ze3m/page-assist). | | [automa](/tools/automaapp-automa.md) | [page-assist](/tools/n4ze3m-page-assist.md) | | --- | --- | --- | | Tagline | A browser extension for automating your browser by connecting blocks | Use your locally running AI models to assist you in web browsing | | Stars | 21,619 | 8,220 | | Forks | 2,341 | 784 | | Open issues | 377 | 364 | | Language | Vue | TypeScript | | Adopt for | Automa is known for its ease of implementation and browser agnostic design enabling users to streamline tasks on multiple platforms. | A Chrome and Firefox extension enabling local AI model-assisted web browsing, built with TypeScript under an MIT license and requiring Bun for development. | | Persona | - | - | | Runtime | - | - | | License | Other | MIT | | Categories | Developer Tools | Developer Tools | ## Trust and health _Sourced signals - not a safety guarantee. No winner column._ | | [automa](/tools/automaapp-automa.md) | [page-assist](/tools/n4ze3m-page-assist.md) | | --- | --- | --- | | Maintenance | Slowing (36%) | Very active (96%) | | Days since push | 195d | 0d | | Open issues (now) | 377 | 364 | | Open issues delta | +5 (30d) | +12 (30d) | | Owner type | Organization | User | | Full report | [trust report](/tools/automaapp-automa/trust.md) | [trust report](/tools/n4ze3m-page-assist/trust.md) | ## Decision facts: automa - **Adopt for:** Automa is known for its ease of implementation and browser agnostic design enabling users to streamline tasks on multiple platforms. ## Decision facts: page-assist - **Adopt for:** A Chrome and Firefox extension enabling local AI model-assisted web browsing, built with TypeScript under an MIT license and requiring Bun for development. ## Choose when ### Choose automa if… - automa is primarily Vue; page-assist is TypeScript. - License: automa is Other, page-assist is MIT. - Tags unique to automa: automation, browser-automation, firefox-extension, hacktoberfest. - If you are working with Chrome or Firefox browsers and require the capability to interconnect blocks to automate repetitive, browser-based actions. ### Choose page-assist if… - page-assist is primarily TypeScript; automa is Vue. - License: page-assist is MIT, automa is Other. - Tags unique to page-assist: chat-application, localllm, ollama, open-source. - page-assist ships an MCP server manifest. - You need to integrate your own locally developed AI models into a browser environment ## When NOT to use automa - When specific automation tasks demand customization via coding rather than block connectivity since Automa is more suited for visual scripting. - If your project involves non-browser-based workflows, as Automa's functionality is limited to browser extensions like Chrome and Firefox. ## When NOT to use page-assist - If you require cloud-hosted AI services, as page-assist focuses on local model use - When the development setup demands a specific build tool other than Bun or npm - In environments where installation of additional software such as Ollama is restricted ## Common questions ### What is the difference between automa and page-assist? automa: A browser extension for automating your browser by connecting blocks. page-assist: Use your locally running AI models to assist you in web browsing. See the comparison table for live GitHub stats and shared categories. ### When should I choose automa over page-assist? Choose automa over page-assist when automa is primarily Vue; page-assist is TypeScript; License: automa is Other, page-assist is MIT; Tags unique to automa: automation, browser-automation, firefox-extension, hacktoberfest; If you are working with Chrome or Firefox browsers and require the capability to interconnect blocks to automate repetitive, browser-based actions. ### When should I choose page-assist over automa? Choose page-assist over automa when page-assist is primarily TypeScript; automa is Vue; License: page-assist is MIT, automa is Other; Tags unique to page-assist: chat-application, localllm, ollama, open-source; page-assist ships an MCP server manifest; You need to integrate your own locally developed AI models into a browser environment. ### When should I avoid automa? When specific automation tasks demand customization via coding rather than block connectivity since Automa is more suited for visual scripting. If your project involves non-browser-based workflows, as Automa's functionality is limited to browser extensions like Chrome and Firefox. ### When should I avoid page-assist? If you require cloud-hosted AI services, as page-assist focuses on local model use When the development setup demands a specific build tool other than Bun or npm In environments where installation of additional software such as Ollama is restricted ### Is automa or page-assist more popular on GitHub? automa has more GitHub stars (21,619 vs 8,220). Stars measure visibility, not whether either tool fits your constraints. ### Are automa and page-assist open source? Yes - both are open-source projects on GitHub (automa: Other, page-assist: MIT). ### Where can I find alternatives to automa or page-assist? GraphCanon lists graph-backed alternatives at [automa alternatives](/tools/automaapp-automa/alternatives) and [page-assist alternatives](/tools/n4ze3m-page-assist/alternatives) ([automa markdown twin](/tools/automaapp-automa/alternatives.md), [page-assist markdown twin](/tools/n4ze3m-page-assist/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/automaapp-automa-vs-n4ze3m-page-assist.md) mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers. ### Which is better maintained, automa or page-assist? automa: Slowing. page-assist: 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 automa and page-assist? GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: [automa trust report](/tools/automaapp-automa/trust); [page-assist trust report](/tools/n4ze3m-page-assist/trust). --- **Machine-readable endpoints** - JSON: [`/api/graphcanon/graph?tool=automaapp-automa`](/api/graphcanon/graph?tool=automaapp-automa) - 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/_