An agent skill is porting a 1998 game to the browser, with glitchy assets live so far
LLM agent skill he is developing is decompiling a 1998 game and migrating assets to the browser, live site with glitchy imperfect assets produced.
A random mix from the whole library. Shuffle for a new set.
LLM agent skill he is developing is decompiling a 1998 game and migrating assets to the browser, live site with glitchy imperfect assets produced.
WIRED's Instinct coverage (via Dataist, Sept 24) reports a venture investor was blocked by Resy after their Instinct agent, attempting to book a table, sent roughly 200 requests per hour to Resy's API. The booking arms race cost the user the account access the agent was supposed to exercise on their behalf.
He used AI to mod a program he uses. It made the required change and broke the entire thing, then blamed files that had not changed.
He was working through a 1.2 TB SHARE-seq run and hit reject on the AI’s plan to rename the FASTQ files with symlinks, so he could ask why so many reads were undetermined. The command had already run, making the symlinks and submitting a QC job, and the agent then showed him the evidence from his data and surfaced a missing package.
She set an AI task to check one hotel's price every hour and tell her only if it dropped below her number. Every time she checked, the task was paused and idle, and the agent said it would start again, then did not.
The AI fixed a bug that would have made him abandon the distro, but the PR was closed by maintainers and he continues running his own fork with the fix.
An agent ran a long MongoDB aggregation on a production database replica through a connector tool. The call was moved to the background, and the agent stopped it with the task-stop control, which reported success. The agent told the user the query had been stopped. Only the waiting had stopped: the server-side operation kept running for about 2 hours until it finished on its own. Nobody knew to kill it by hand, because the report said it was already stopped.
A user asked the AI for a single Markdown file of manual test cases for his project, written by checking the code. Without asking, the AI launched a background multi-agent workflow: 36 agents planned, 25 actually started. It ran until his usage was gone, the agents failed, and the session ended. No verifier finished and no file was ever written to his project. The AI later admitted one pass would have done the job.
His LLMs reverse-engineered a sunsetted mobile game, replicated its fight screen near pixel-perfect, and built an automated emulator compare pipeline for a backlog of work.
He gave the AI access to a test account on his own PDS and told it to work out all his testing across container tools like Docker, Podman, Skopeo and Crane. The activity got the first pds.rip account banned.
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.