BrowserKitten – Selection‑First Web Agent for Chrome
BrowserKitten is a Chrome MV3 unpacked extension that lets developers programmatically interact with the current tab, execute JavaScript, and manage session artifacts without a server. 2,881 GitHub stars in 35 days since player-yn/browserkitten was created (81.5/day). 1 source across 1 channel. Automatically detected
30Fact cited ·Analysis our interpretation ·Estimate forward-looking · [n] links to the source
6 claims drafted by openai/gpt-oss-20b were kept because each quote was found verbatim in its source; 1 unverifiable claim was discarded. Statements marked AI await human review.
What happened
- Fact The extension requires Chrome 135+ and can use sys.eval or page‑identity fetch on Chrome 138+ when Allow User Scripts is enabled.[1]AI
Needs Chrome 135+. On Chrome 138+, enable Allow User Scripts on the extension details page if you want sys.eval or page-identity fetch
- Fact The extension stores the OpenAI‑compatible API key in chrome.storage.local and does not rely on a hosted model.[1]AI
paste an OpenAI-compatible API key (BYOK; stored in chrome.storage.local)
- Fact There is no build step; the repository contains no package.json and can be loaded directly via Load unpacked.[1]AI
There is no package.json and no build step. Needs Chrome 135+.
- Fact Release packaging is performed with a Python script that zips the extension into dist/pawwork.zip.[1]AI
Release packaging: python scripts/packextension.py --zip dist/pawwork.zip
- Fact The GitHub repository player-yn/browserkitten was created on 28 Aug 2026 and had 2,881 stars on 2 Oct 2026.[1]
- Fact Its description reads: “Paw Work - selection-first web agent for Chrome: select on the live page, describe the outcome, take away an editable office file. BYOK, sandboxed, no server.”[1]
- Fact That is 2,881 stars in 35 days, an average of 81.5 per day.[1]
Why it matters
- Analysis Clone the repository, load it as an unpacked extension, provide an OpenAI API key, and use the side‑panel to send tasks to the current tab.AI
- Analysis Automatically detected from public activity data. Not yet reviewed by an analyst.
Should I care?
What changed?
- Fact The extension requires Chrome 135+ and can use sys.eval or page‑identity fetch on Chrome 138+ when Allow User Scripts is enabled.[1]AI
Needs Chrome 135+. On Chrome 138+, enable Allow User Scripts on the extension details page if you want sys.eval or page-identity fetch
- Fact The extension stores the OpenAI‑compatible API key in chrome.storage.local and does not rely on a hosted model.[1]AI
paste an OpenAI-compatible API key (BYOK; stored in chrome.storage.local)
Who is affected?
- Analysis Developers building Chrome extensions or web automation tools who need a lightweight, server‑less agent for interacting with web pages.AI
What can developers do with it?
- Analysis Clone the repository, load it as an unpacked extension, provide an OpenAI API key, and use the side‑panel to send tasks to the current tab.AI
Is it production-ready?
Insufficient evidence
Analysis Not assessed.
What would make it important?
Not yet assessed.
What could prevent adoption?
Not yet assessed.
Technical change
- Fact The extension requires Chrome 135+ and can use sys.eval or page‑identity fetch on Chrome 138+ when Allow User Scripts is enabled.[1]AI
Needs Chrome 135+. On Chrome 138+, enable Allow User Scripts on the extension details page if you want sys.eval or page-identity fetch
- Fact The extension stores the OpenAI‑compatible API key in chrome.storage.local and does not rely on a hosted model.[1]AI
paste an OpenAI-compatible API key (BYOK; stored in chrome.storage.local)
- Fact There is no build step; the repository contains no package.json and can be loaded directly via Load unpacked.[1]AI
There is no package.json and no build step. Needs Chrome 135+.
- Fact Release packaging is performed with a Python script that zips the extension into dist/pawwork.zip.[1]AI
Release packaging: python scripts/packextension.py --zip dist/pawwork.zip
Architecture
No architecture has been documented for this signal.
Developer impact
Developer implications have not been assessed yet.
Difficulty has not been estimated yet.
Adoption & momentum
No adoption indicators recorded.
Timeline
First seen by the Astrava pipeline[1]
Limitations & risks
- Fact The extension cannot interact with restricted pages such as chrome:// or the Web Store, returning NEEDPAGE.[1]AI
Restricted pages such as chrome:// and the Web Store return NEEDPAGE
- Fact Using sys.cdp requires closing DevTools on the target tab to avoid CDPBUSY errors.[1]AI
Close DevTools on the target tab before using sys.cdp (otherwise CDPBUSY)
- Analysis Generated from activity metrics only; verify the linked sources before acting on it.
Competing approaches
No competing approaches documented yet.
Who is building on it
No independent projects or organisations are documented as building on this yet.
Evidence & sources
Primary source (1)
Published by the people who built it: release notes, repositories, papers, official docs.
- [1]Player-YN/BrowserKitten repository(opens in a new tab)
Paw Work - selection-first web agent for Chrome: select on the live page, describe the outcome, take away an editable office file. BYOK, sandboxed, no server.
Secondary source (0)
Independent reporting, third-party benchmarks, integrations by other projects.
None recorded.
Community signal (0)
Discussion threads and social posts. Evidence of attention, not of correctness.
None recorded.
How the score of 30 was calculated
| Factor | Share of maximum | Points |
|---|---|---|
| NoveltyRubric level 2/4 (Moderate). Heuristic (automated): first published 35 days ago. | 7.5/15 | |
| Technical significanceNot yet assessed. Requires analyst review; not assessed automatically. | 0/15 | |
| Developer relevanceRubric level 1/4 (Low). Heuristic (automated): no installable package detected; developer-facing topic. | 3.8/15 | |
| Adoption velocityIndependent integrations: unknown (0 pts). GitHub stars: 81.5 per day since creation; full marks at 1000/day, log-scaled (3.2/5). | 3.2/10 | |
| Community momentumFewer than three periods of activity data, or no baseline activity to compare against. | 0/10 | |
| Source credibilityPrimary source present; mean source-tier weight 1.00 (primary 1.0, secondary 0.7, community 0.35). | 10/10 | |
| Cross-source confirmationNo independent publisher has confirmed this yet. | 0/10 | |
| Evidence strengthMet 2/4: primary source ✓, runnable artifact (code, weights or package) ✓, reproducible or independent benchmark ?, technical documentation or paper ✗. 1 unknown (scored 0). | 5/10 | |
| Time to impactNo time-to-impact estimate yet. | 0/5 | |
| Hype penaltyNo hype indicators detected. | 0 | |
| Breakout Score | 30 |
Low confidence (0.48) — 60% of measured factors have data. 0 independent non-community publishers. At least one primary source. Evidence strength 5/10. Capped at Low: no independent, non-community source yet.
An analytical ranking derived from observable signals using model breakout-v1.2. It is not a prediction and not a measure of quality. How it works