Zebkit – Chromium's engine as a library you link, not a runtime you live in

Re:Zebkit – Chromium's engine as a library you link, not a r... by rafram on Monday November 09, 2026 @09:56AM (#50426508)

This got auto-flagged for being AI-generated. It would be much better if you wrote this kind of thing yourself. Your motivations and personal perspective on the project are much more interesting than an LLM’s summary of the readme (which is also a pretty tough read).

[ Parent | on HN ]

Re:Zebkit – Chromium's engine as a library you link, not a r... by Riiiiichard on Monday November 09, 2026 @10:04AM (#50426640)

Short version:

It packages Chromium as a library you can embed directly into applications to add browser capabilities.

It’s trimmed down to be 33% smaller than Electron, with native browser automation APIs for AI agents that run 3–10× faster than tools like Playwright operating over CDP. It also directly exposes 7,000+ functions from Chromium’s bundled libraries for your application to use.

[ Parent | on HN ]

Re:Zebkit – Chromium's engine as a library you link, not a r... by apatheticonion on Monday November 09, 2026 @05:08PM (#50432960)

Agreed. I still write READMEs or anything human-consumable by hand.

The project is very interesting and opens up a lot of use cases - like a replacement for JSDOM in UI testing, a replacement for puppeteer/playwright in e2e testing, or even a base to build a single binary web browser MCP.

[ Parent | on HN ]