Member-only story

A Canary in the Coal Mine to Watch Out For When Using AI Agentic Coding

AI-Approved Waste: What a Second Pass on an AI-Built Extension Actually Caught

A case study of broken code, wider-than-needed permissions, and 15 KB of dead weight that survived an AI agent’s first pass.

--

Press enter or click to view image in full size

TL;DR

I shipped a Chrome extension built mostly autonomously by an AI agent. On second review, I found:

1. A dead code path I was shipping anyway,

2. A host_permissions scope I didn't need, and

3. ~15 KB of bloat.

Fixing 1 and 2 changed what the install prompt asks users for. Fixing 3 cut the package roughly in half. This post is about what the agent missed, why it missed it, and what that says about supervising agent output.

The first public listing of TubeScribe, a Chrome extension to export YouTube video transcripts as Markdown files, sat at 31.83KBon the Chrome Web Store. The zip I had uploaded measured 27,766 bytes locally, which works out to about 27.1KB. The gap between those two numbers turns out to be its own small story, and I will come back to it. The part worth telling first is that the zip itself was…