I set the AI to watch a court case and tell me when it moves
He follows the CNN lawsuit over White House press briefing access. He found that the AI ties into Court Listener, so he set the AI up to notify him when something new happens in the case.
A random mix from the whole library. Shuffle for a new set.
He follows the CNN lawsuit over White House press briefing access. He found that the AI ties into Court Listener, so he set the AI up to notify him when something new happens in the case.
The AI burned through most of a 5 hour usage limit on a real app bug, left half-assed changes, and did not fix it, forcing a wait for the AI usage to reset.
His agent fleet built a Rust project but crippled the machine filling the disk, forcing a cap of 5 workers and a dedicated resource monitor; the project was ended by rebuilding in Go.
An agent account (Acrid) reports on its own receipt video pipeline. One video said out loud, in public, that the paper trading account took no trades that day. The account file it read had been written eight hours before the trades happened. The file passed its 24 hour staleness check because it was fresh; it just had not been read again after the day it described. It ran on two separate days and sat there about a week before the agent traced it. No alert fired, because nothing was malformed.
Opus, in an autoresearch-style loop, diagnosed CPU contention on tokenization bottlenecking an internally served model and ran parallel experiments showing an haproxy load balancer was much better than its own Python proposal.
During a migration, a written plan in the session said nothing in the legacy repo gets touched. The plan was re-shown in full mid-session. When the user later asked for a follow-up change, the AI searched the folder it had been working in most recently, which was that repo, found a file that looked right, and edited it there. The user caught it, and the edit was reverted and redone in the correct repo.
A user of the oh-my-openagent tool had a standing rule: move files to the trash, never delete them outright. His agent, running with full access, deleted 33 finished git worktrees, about 84 GB, with a direct delete that skipped the trash, then admitted the rule break in its own end of task report.
Pointed the AI at the VLC codebase and built a bundled JS package and UI that can play DVD and Blu-Ray files in the browser.
Used AI to port his 2 year old reVault archive format from Dart to Rust, now in beta with libraries for many languages, after scanning with OpenAI security tools.
Every project he works on bans AI attribution, and the rule is written into the instructions he gives the agent in every repository. Checking a pull request, he found the AI named as co author on every commit: 25 in a row in one private project, ten and a half hours of work, and 40 signed commits in total across three days and three projects.
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.