The Wish extension
One-tap adds to the family wishlists from any shopping site, for Chrome, Edge, Brave and other Chromium browsers. Each computer's extension is set to one person β click the Wish button on a product page and it lands on that person's default list, with the product's name, photo and price filled in. In the popup you can switch who it's for (Caleb can add something for Eli), and right-clicking any page or link gives an βAdd to Wishβ shortcut.
Set up on a home computer (recommended)
On a normal home computer this is the route that works: load the extension yourself and pair it with a connect code. Four steps, once per computer.
- On this site, open Settings β Browser extension and click Generate / regenerate code for the person whose computer this is. The code is shown once β keep that tab open until step 4.
- Download the extension (.zip) and unzip it into a folder you won't move or delete β Chrome runs the extension from that folder, so if the folder goes, the extension breaks.
- Open
chrome://extensions(in Edge:edge://extensions), turn on Developer mode (top-right), click Load unpacked and pick the unzipped folder. The π Wish button appears β pin it via the puzzle-piece menu if it hides there. - Right-click the Wish button β Options, paste the connect code from step 1 and click Connect. The options page now shows this computer is set to that person β done.
Updates: an unpacked extension doesn't update itself. When a new version
ships, download a fresh zip, unzip it over the same folder, then open
chrome://extensions and click the reload (β») button on the Wish
card. Your connect code stays put.
One quirk to expect: Chrome may show a developer-mode notice on startup (a prompt to disable developer-mode extensions). That's normal for unpacked extensions β it isn't an error, and you can dismiss it.
Managed computers (work, school, or domain-joined)
There's a slicker route for managed machines: a per-person setup file that installs the extension by browser policy and pre-binds it to the person β no code to paste, and it updates itself from this site. Why is it the second section? Chrome only lets policies force-install self-hosted extensions on enterprise-managed machines; on a home PC the policy lands fine, then Chrome declines the install. So the setup files below are for managed computers β home computers should use the route above.
Windows: download the person's wish-setup-<name>.reg
in Settings β Browser extension, double-click it and
approve the prompts (it needs administrator rights β it writes the browser policy keys
under HKEY_LOCAL_MACHINE), then restart the browser. The π
Wish button appears, already set to that person, and the extension's
settings page shows βSet by computer policyβ for them.
Mac: download the person's
wish-setup-<name>.mobileconfig in Settings and
open it β nothing seems to happen; macOS has quietly registered the
profile. Open System Settings β General β Device Management (on older
macOS: System Preferences β Profiles), select the
βWish Extension β <name>β profile and click Install.
macOS may warn that the profile is unsigned β that's expected for a
self-hosted profile; it's the file you just downloaded from this site. Then
fully quit and restart Chrome / Edge and the button appears, already set
to that person.
Both setup files carry a fresh connect code for that person, so downloading a new one
later retires their old code. To undo on Windows, delete the two
ExtensionInstallForcelist policy entries the file added; on a Mac, delete the
profile in Device Management (or ask Ian).
Add from a phone
Android: install Wish on the phone first (open
wish.carrgarage.com in Chrome β menu β Add to Home screen).
Once it's installed, Wish shows up in the share sheet: in Amazon or any
shopping app, tap Share β Wish and the item lands on your default list
with its name, photo and price filled in. (Amazon hides the link inside the shared text
rather than sending it as a URL β Wish digs it out automatically.)
iPhone: Safari can't put web apps in the share sheet, so iPhones use a one-time Shortcut instead. It takes two minutes, once per phone:
- Open the Shortcuts app, tap οΌ to make a new shortcut, and name it Add to Wish.
- Tap the shortcut's settings (β) and turn on Show in Share Sheet, set to accept URLs.
- Add the action Get Contents of URL. Set the URL to
https://wish.carrgarage.com/api/agent/itemsand the method to POST. - In that same action, add two headers:
Content-Type=application/json, andAuthorization=Bearerfollowed by the family agent token. The token is never shown inside the app β it's the same one the agent API uses, and Ian keeps it with the server settings; ask him for it and don't share it outside the family. - Set the action's Request Body to JSON with two
fields:
link= Shortcut Input, andperson= whose list it goes to, in lowercase βian,brittany,arthur,caleboreli. Leave the list out and it lands on that person's default list. - Optional but nice: add a Show Notification action after it with the text Added to Wish π, so you get a confirmation tap.
- Use it: in Amazon or Safari, tap Share β Add to Wish. Done β the item is on the list, priced and pictured like any other add.