When should you use it?
- A small bug in an app bothers you daily
- You can run scripts on your machine
- The vendor will not fix it
Not for: Work machines you may not modify; Apps whose license bans it
What do you need, and what do you get?
You need
- Description of the bug
- Steps to reproduce
- Permission to run scripts
You get
- Workaround that leaves app files alone
- Steps to undo it
- Notes for after updates
How does it work, step by step?
- Describe itWrite exactly what happens and when.
- ReproduceGive the agent steps so it can see the problem.
- Set the ruleTell it not to change the app's own files.
- Build the workaroundLet it create a hook, script or helper around the app.
- Keep an undoAsk for removal steps and recheck after app updates.
The prompt
Our own prompt, inspired by btx on Hacker News and written to work in Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
This app bothers me: {app}. What happens: {problem}. Steps to reproduce: {steps}. Find the cause and build a workaround that does not modify the app's own files, such as a script or hook. Give me install and removal steps, and note what might break after an update.
Inspired by btx on Hacker News: Comment in REA Reverse – Engineer Anything. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Updates can break workarounds; keep notes.
- Respect license terms and work IT policies.
- Expect some rounds of feedback before it gets it right.
Our take
Everyone tolerates a dozen small software annoyances because fixing any one of them used to cost an evening of reading APIs. btx's habit flips that trade: describe the irritation, let an agent investigate, and accept a few rounds of pushing it to do better. The detail worth copying is the constraint btx set for the Hyper-V fix, that the solution must sit outside the vendor's files. A wrapper, hook or helper script survives updates, can be removed in seconds, and avoids most licensing and support headaches that patching binaries would bring. Ask the agent to reproduce the problem first and to tell you exactly what it installs, where it runs at startup and how to uninstall it, then keep those notes in one file per fix. After each app update, recheck the list, since workarounds break quietly. On a work laptop, check what IT allows before installing hooks or background helpers, because security software may flag them. For anything touching credentials or network traffic, read the code before running it.
Where the time goes back: The small daily irritation is gone, and the app still updates normally.
FAQ
Why not patch the app?
Does it work first time?
Source and credit
Inspired by btx on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Comment in REA Reverse – Engineer Anything
- Creator
- btx on Hacker News
- Published on
- Hacker News
- Original date
- Oct 10, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.