Why it mattersA page-selection agent that returns editable files replaces the copy-paste-and-clean-up loop developers hit every time they pull data out of a rendered dashboard or a client-side table.
Player-YN published PawWork on 28 August as an MIT-licensed Chrome MV3 extension, and the repository is at 1,388 stars as of today, nine days later.
The pitch is small. Turn Paw Mode on, click images, tables, text blocks, or links on a page you already have open, type the outcome you want in the side panel, and PawWork returns an editable Word document, spreadsheet, slide deck, or a live canvas file. The author calls this "selection-first": the agent starts from what you point at, so it never has to guess which part of the page you meant.
What is actually new
The unusual piece is what the model produces. The model writes code that assembles the file, and that code runs inside the extension in a QuickJS virtual machine after being compiled with a packaged copy of esbuild-wasm. The README states the sandbox never sees chrome.* APIs, the live page DOM, or any other session's files, and that no executable code is fetched from a CDN. Everything is BYOK: chat, image analysis, and web acquisition each take your own API keys, held in the extension.
The author is direct about the limits. PawWork will not roam the web unattended, will not fill out forms or complete a checkout on your behalf, and will not replace Excel, PowerPoint, or a full browser-RPA tool. The work surface is the live canvas beside the page, and you check what came back before you keep it.
1,388 stars in nine days, from one solo developer
1,388 stars in nine days is genuine traction for a Chrome MV3 extension from a single developer, and the README lists the commit ranges that produced each showcase file. The project is one solo developer, so the pace of pushes since launch is worth watching before it lands in a team workflow.
The extension runs local: after Load unpacked in Chrome's developer mode, it uses the API keys you paste, and PawWork's server-side code path is documented as "no server." That makes it easier to trial inside a company that would refuse a browser extension routing page data through a vendor.
For a working developer, the workflow that changes is the one where you already switch to a browser to grab a rendered figure, a filtered dashboard, or a table only rendered client-side, then patch it together in a document by hand. PawWork sits in the same spot, but returns a file you can hand off.
Source
Player-YN/PawWork_ZhuaZhua on GitHub. Star count and repository dates via the GitHub REST API, checked 2026-09-06.
Source: GitHub
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually shipping with them. Short, and only when there is something worth reading.
