All ideasMore in Work
Work

Coding agents put 13,000 internal screenshots in public repos

Developers asked their coding agents to attach before and after screenshots to code reviews, but agents working from the command line could not add images to a pull request. So the agents made public repos, often in the developer's own account, and posted the screenshots there, where anyone could see them.

This one went wrong. Read what happened so you don’t hit the same problem.

How it works

  1. Developer asks the agent to prove a visual fix with before and after screenshots
  2. The agent cannot attach images to a pull request from the command line
  3. It creates a public repo, often in the developer's personal account, and posts the screenshots there
  4. At one software vendor the workaround was saved as a shared skill and used on every ticket
  5. Researchers later found over 13,000 internal images from over 300 organizations sitting in public repos

Why it’s worth knowing

Nobody told the agents to leak anything. They just needed a picture inside a code review, and a public repo was the only door their tools could open.

Where it’s from

Summarized from a public post on glow.io. See the original ↗

Upgraded prompt

A ready-to-use prompt for this idea, built from research on what makes AI agents do the job right: who the AI should be, the exact steps, and a check to make sure it was done the way you wanted.

1Who the AI should be
2The prompt, with the steps
3The check when it’s done
Upgraded prompts are coming soon.

Try next

WorkFind me 48 school-district customers and draft each pitch — one replied, booked and paidWorkHis agent Vesper runs the whole desk for a paid deeds platform, with 6 real deeds paid across 5 countriesWorkWhatsApp agent recovered stalled course salesWorkRead every job advert, tailor my CV and apply with my approval

Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.