When should you use it?
- An extension you rely on has no Safari version
- You use a Mac with developer tools
- It is for personal use
Not for: Publishing someone else's extension; Extensions with closed native parts
What do you need, and what do you get?
You need
- Installed Chrome extension
- Mac developer tools
- Agent with local access
You get
- Local Safari build
- Notes on what changed
- Install steps
How does it work, step by step?
- Locate the sourceHave the agent find the installed extension's files.
- Check the licenseConfirm you can modify it for personal use.
- PortAsk it to convert it to a Safari extension project.
- Install locallyBuild and enable it in Safari.
- TestCheck each feature you rely on.
The prompt
Our own prompt, inspired by jedberg on Hacker News and written to work in ChatGPT. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
The extension {extension} is installed in Chrome on this Mac. Find its source, check its license and tell me what it allows.
If personal modification is allowed, port it to a Safari extension, build it, and give me steps to enable it. List its permissions and any features that did not port.Inspired by jedberg on Hacker News: Comment in Apple's new 'Switch to Safari' campaign details why you should ditch Chrome. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Do not redistribute someone else's code without permission.
- Extensions read browsing data; review permissions.
- Updates will not arrive automatically.
Our take
jedberg's experiment shows how cheaply personal software can now be adapted: an extension port that once meant an afternoon with Apple's conversion tools and documentation took twenty minutes and a sliver of a monthly plan. The clever move was telling the model where the source already lived, in the installed Chrome copy, so it did not have to reconstruct anything. The boundary that keeps this healthy is personal use. Converting an extension you rely on for your own browser is very different from republishing someone else's work, so read the license and keep the port on your machine unless the author allows otherwise. Check the permissions the Safari version requests, because session and tab managers can read every page you visit, and make sure the port did not add network calls the original lacked. You also inherit maintenance: when the original updates or Safari changes its extension rules, you will need to port again. Keep the prompt and any fixes in a small folder so the next round takes minutes.
Where the time goes back: A missing extension stops being a reason to keep switching browsers.
FAQ
How long did it take?
What did it cost?
Source and credit
Inspired by jedberg 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 Apple's new 'Switch to Safari' campaign details why you should ditch Chrome
- Creator
- jedberg on Hacker News
- Published on
- Hacker News
- Original date
- Oct 13, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- ChatGPT
- 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.