Shuffle again

A random mix from the whole library. Shuffle for a new set.

Life admin

Email, calendars, forms and paperwork · 213 ideas

Explain my situation and find the welfare payments I can claim

A builder used AI to make a 'describe your situation' tool over Australia's official welfare pages: it takes a one-sentence description, works in 24 languages and shows which Services Australia payments might apply, each linked to its official page. Across 43 test questions it invented zero payments and refused correctly 100% of the time, with payment recall of 0.76.

Life adminWent wrong

My daily email automation can draft but is never allowed to send

He set up an automation to email himself a daily update from his calendar. Every run fails at the send step with a safety block, even with his Gmail connector set to allow all tools, while asking in chat sends fine. He rebuilt it several ways and every version stops at the same point.

This one went wrong. See what happened before you try it.

Found an important message the user had missed in his inbox, then

X user someone (Charlie) gave the AI inbox access at the start of a deep personal-data experiment. In one of the standout moments, the agent surfaced an important message he had missed, drafted a response, co-edited it with him, and sent it — an agentic loop (find, draft, revise, send) rather than a one-shot draft.

The AI does his boring paperwork in his own logged in browser: reserve duty refunds, national insurance, flight check-ins

Outside code, his biggest win is boring paperwork. The AI filed his reserve duty refunds, sorted out his national insurance payments and did his flight check-ins, working in his own logged in Chrome. Each job is about ten minutes of work, which is exactly why he kept putting them off. He gives each area of his life its own folder with a CLAUDE.md and a notes file, so the money stuff does not mix with the rest.

Life adminWent wrong

Delete the test event, but confirm with me first

The developer set his calendar connection to 'confirm before any change', then asked the dot to delete the event it had just created. The dot deleted it in about 30 seconds with no confirmation screen, explaining that a clearly worded request counts as its own permission; the confirm-before-changes setting did not stop it.

This one went wrong. See what happened before you try it.
Show 10 more

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.