A software company ported 65 open-source projects with AI and finished them
Akka ported 65 OSS projects with AI, finished ports.
A random mix from the whole library. Shuffle for a new set.
Akka ported 65 OSS projects with AI, finished ports.
Diana gave the AI Fable 5.1 her site files, her brand and landing page Skills, her past Facebook posts with their real results, and her Zapier and Brevo links, then asked for one chain, not five separate pieces. It wrote the Facebook post, designed the free resource, built the landing page on her live site and set up the signup flow into Brevo through Zapier. The page is live. She made one fix to the page layout. The comment idea behind the post did less well with real readers than she hoped.
Her business folder was a mess and file names did not show which files were still live on her site. The AI checked each file's fingerprint instead of its name, moved 288 files, and deleted none.
Diana at AI Agents Library gave the AI 500 loose files from her real business desktop. It proposed a folder plan first, she approved it, and it filed 490 where she wanted them, held 10 back for review instead of guessing, and caught all 48 exact duplicates and all 34 renamed ones.
Creator Amie Tollefsrud gave the AI access to her Instagram analytics and asked for growth advice; after three clarifying questions about audience and positioning, the AI delivered an 'Instagram Growth Plan' PDF. Screen recordings show an executive diagnosis (1.85M accounts reached), audience positioning, four content pillars, keyword clusters, carousel and story blueprints, and a 7-day action checklist.
He sends audio messages to his AI. It transcribes them locally on the graphics card in his home server, so his voice notes become text without leaving the house.
Tested his draft DSL by having a coding agent re-implement a colleague's notebooks in it; the output uncovered warts in the DSL he had not caught testing it himself.
Analyzer agents audited and trimmed skill files, cutting about 18 percent then about 600 more lines, and extracting bash into scripts turned up bugs.
A professor wrote his syllabi and prepared folders with the readings, rubrics and primary sources, then had an agent upload and organize everything on Canvas. Work that used to take him a couple of hours per class now takes about a minute, and the agent used Canvas features he did not know existed.
He runs AI with DeepSeek on his own project. It started by opening issues when it found problems; he has since given it the access to submit pull requests with the fixes, and it now does both.
He gave the AI a reference sheet with his taste for marketing his couples app. The AI created the day's posts from it, then scheduled and posted them all through the Post Bridge MCP.
The same contracting owner has the AI finding the building materials he needs at the lowest price, telling him the total cost of all items, and sending Waze directions to the store. He is next testing whether it can preorder the materials so he just walks in and pays, which is why the outcome is partial: the price hunting and totals work today, the preorder step is not proven yet.
A builder runs AI as a night shift for his side project. Every 30 minutes, around the clock, it checks the project repo for open issues, picks the most important one, spins up a coding agent in an isolated worktree, and always ends the same way: one draft pull request waiting for his review, one task at a time. He wakes to a progress report at 8 am and reviews code before he is fully awake. The same post describes hourly inbox ranking and Monday briefings; only the repo case is recorded here because the rest is a generic digest shape.
His AI server checks what the current shipped Micro.blog app versions are and whether an app is in review. It updates the public help page by itself.
Internal multi-subagent code review tool he built has run for half a year and finds serious issues including privacy leaks that humans and open-weight models miss.
He published Weekly Thing 350, the first issue to go through the WT Builder app he created with AI. Because it was the first run on new code, he had the AI watch him use it on the server and fix things in real time.
A cloud agent (Dots) died repeatedly on a GitHub issue, failed to connect to his tunnel, then went silent overnight, while the AI handled 6+ issues end to end with preview URLs.
An LLM generated an entire compiler for his new language over 7 months of iterating and fixing, generating WASM runnable in a browser playground the LLM also built.
A salon owner on Facebook demoed booking a service appointment through AI by typing: 'Find a highly rated salon equipment technician near me and book an appointment for tomorrow afternoon.' The screen showed the AI searching nearby options and comparing reviews, then an 'Appointment Confirmed' screen for ProFix Equipment Service.
Told the AI to figure out their GitHub to Forgejo migration and it worked, a much smaller problem than expected.
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.