A bounty-funded agent fix is merged into VisiData, and review shows what its acceptance test missed

According to the pull request, maxfain posted a 2 USDC task asking an agent to find an open issue in a project with a written policy welcoming AI help. An agent picked VisiData issue #3224, a docs page whose asciinema player rendered at 0px, and wrote a spec. A second task, paid 1 USDC, produced the patch; his timeline shows it delivered three minutes after an agent claimed it. He says he reviewed and tested the diff himself before opening the PR, and the PR discloses the agent provenance.

Reviewer midichef then pointed to five more broken players on three other pages, and wrote that an easy fix like this "doesn't help with the main bottleneck, which is testing the specific build of the visidata.org site." maxfain agreed. The task had been limited to one file and accepted on "a few greps plus a diff check", which is why the other five were missed. A second agent patch fixed them. His reported check is a headless Chrome render showing 1/3/1/1 players mounting on the four pages, against 1/0/0/0 on the unpatched tree. He adds that this is not the real site build.

Maintainer saulpw first asked who the "I" in "How I tested" was, since the text read as AI-generated. He then merged, writing that "the load-bearing gate is human attention after bot work", and advised keeping bot and personal accounts separate; maxfain said he will. After the merge, commenter BroadlyWhitaker argued for reverting the commit and banning the user. On Hacker News the submission had 14 points a little under two hours after it was posted (read about 03:08 UTC, September 24), and much of the discussion was about the AI-written PR text rather than the code.

Why it matters: The first patch was accepted by its own test and still missed five of the six broken players, because the test was a grep and the scope was one file. When you hand small tasks to agents, the acceptance check is what you are paying for, and a cheap task does nothing for a maintainer whose real cost is building and testing the site. The maintainer's rule is simple enough to adopt: agent work is welcome once a named human has looked at the result, and the account speaking makes clear which one is talking.