A random mix from the whole library. Shuffle for a new set.
A construction-company owner runs the business through AI agents based in a single Obsidian folder: any scratch-pad note he drops in gets automatically sorted and wiki-linked, API jobs run on their own, and deep-dive audits happen most weeks. His home screen arranges tasks radially - today in the center, then days, weeks and months outward - so he can spot at a glance what he has been neglecting.
He is a delivery driver who employs a worker. Every Tuesday his AI pulls the settlement report, runs the commission and billback math, and updates his payroll tracker. The job used to eat a chunk of his evening each week. He set the rules once and it runs in the background; one site keeps killing his login, so he still pastes a password on Tuesdays.
His coding agent now records the demo video for its own PRs.
A non technical founder, who spent 25 years in banking, has six AI agents running his small business magazine: a CEO agent, trend scout, researcher, writer, SEO agent and publishing agent. He has caught real errors, including a sales agent that wrote a full report for a fake email address and a CEO agent that burned money by waking up too often.
Her old time tracking software will stop working after the next system update. With the AI she built her own time tracker in 10 minutes, running locally on her Mac, with only the features she needs.
The solo maintainer of the karasu modeling language runs dependency updates through an AI skill that investigates each Dependabot PR before anyone merges: release notes, the diff between tags, publisher or ownership changes, install-time scripts, lockfile edges and known advisories, written up as merge, hold or reject recommendations in a design doc. In the week of Oct 10–17 three triage rounds fed 88 merged PRs (16 from Dependabot) and 12 architecture decision records, and the process caught a rebuilt lockfile silently moving a package off the reviewed version.
A man wired his lab instruments to his home network, put all their manuals and programming guides into an AI project, and the AI wrote most of the first set of Python programs that control the instruments and pull data from them. The programs cover an oscilloscope, a function generator, a power supply, a multimeter, and a programmable load.
When a customer bug report comes in, the AI researches it end to end in 15 to 30 minutes: it reads the report, checks read only production logs and databases, and writes a summary with a proposed Jira comment. He approves the comment before it posts, and he says he barely does bug research by hand anymore.
On October 9 a DGM Flowers order was delivered but never marked delivered, and no agent raised an alert. Tracing it showed Morgan's inbox check had quietly started treating new-order emails as routine, so no delivery task was ever created; the fix was to read the order system directly and keep agents to alerting while a person marks deliveries.
Opus 5 pointed at his own app created a similar exploit to a known file-upload attack in 3 minutes, showing the app was vulnerable.
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.