Skip to main content

6 docs tagged with "human-in-the-loop"

View all tags

It Assumed the Platform Wouldn't Let Us

A schema field named defaultToReminders was read as proof that YouTube and TikTok require manual publishing. Its value was false on both channels. Ten posts were configured to send phone notifications instead of publishing.

It Assumed tools/ Was Where Tools Go

Asked to capture design notes for a scanner, the agent filed them under tools/. That directory is only for portfolio-site automation — a convention that existed nowhere in the repo, because the README meant to state it was empty.

It Decided My Homepage Was Unbuilt

Asked to bring internal docs up to date, the agent read a 15-month-old planning doc and declared the feature unbuilt. It had shipped months earlier — including the exact session-tracking code the doc sketched.

The Grep That Never Worked

An article generated with an LLM recommended a command as the canonical way to list kitty keybindings. The command returns nothing, and always did. It sat published for months on one of my better-performing pages.

The Third Line of Output Was Invented

Two lines of real terminal output, then a third that was never printed by anything. It was heading into a video whose entire premise was that the output is real.

Why This Folder Exists

A running case file of assumptions a coding agent made that didn't hold — recorded in a fixed format so the collection can eventually answer when a human actually needs to be in the loop.