All ideasMore in Hobbies

Rebuild your own broken connector and finish the weekly update

A user's notes MCP was down - his own mistake - when his agent decided finishing the request mattered more: it researched the Joplin API, wrote, refactored, and debugged a 400-plus-line Python tool across five files, then used it to read his notes and write its weekly update markdown into Joplin as planned.

How it works

  1. Weekly update task starts
  2. Notes MCP is down
  3. Agent researches the Joplin API
  4. Writes and debugs a 400-line replacement tool
  5. Reads the notes
  6. Writes the weekly update in markdown

Why it’s worth knowing

The connector broke, so the agent manufactured a new one - 400 lines, five files, debugged - just to deliver a routine weekly note on time.

Where it’s from

Summarized from a public post on news.ycombinator.com. See the original ↗

Upgraded prompt

A ready-to-use prompt for this idea, built from research on what makes AI agents do the job right: who the AI should be, the exact steps, and a check to make sure it was done the way you wanted.

1Who the AI should be
2The prompt, with the steps
3The check when it’s done
Upgraded prompts are coming soon.

Try next

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.