{{ message }}
Repository navigation
docs: Add guide on building custom extensions (e.g. browser plugins) #1936
Description
Context
In #1921 (and discussion #1920), a third-party stealth-browser integration example was proposed for the "Avoid getting blocked" guide. We decided not to feature fresh third-party tools directly in our docs, since a docs example is effectively an endorsement and we want to keep the bar at proven maturity and adoption.
Internal discussion: https://apify.slack.com/archives/C06ENBV1B9Q/p1779877268101609
Proposal
- Add a docs page describing how to build custom extensions for Crawlee — e.g. subclassing
PlaywrightBrowserPluginto integrate alternative browser backends, custom HTTP clients, etc. - Third-party projects can then host their own integration guides on their side and we can link to selected ones from this page, instead of maintaining tool-specific examples in our docs.
Activity
vedika333 commentedon Jun 8, 2026
"Hi, I'd love to work on this! I build Apify Actors and am familiar with PlaywrightBrowserPlugin. I can write the guide covering subclassing, a working code example, and the wiring with BrowserPool. Could you assign this to me or point me to the docs folder structure I should follow?"
vdusek commentedon Jun 9, 2026
Hi @vedika333, we do not assign issues to the community. However, you can try to come up with something. Currently, there are 4 extension points in Crawlee: Crawlers, HTTP clients, Storage clients, and Browser plugins. With the current docs structure, the part about extending the browser plugins should probably live in "Playwright crawler" guide.
docs: document Playwright browser plugin extensions (#2089)
docs: add guide on building custom extensions
docs: add guide on building custom extensions (apify#2106)