Update Safari Extension

Use the least invasive route that can test the change. A successful build and a successful live Safari check are separate evidence.

Choose the runtime route

Check git status --short --branch -uall and inspect Safari Settings > Developer/Extensions. Record whether Voyager is temporary or app-installed and enabled before changing it.

• Web extension: TypeScript, React, CSS, manifest, or bundled assets that stay inside the extension use the temporary route below.
• Native or signed app: Swift, entitlements, Sparkle, signing, packaging, or any call to browser.runtime.sendNativeMessage require native-app.md. Temporary extensions cannot launch the containing-app handler, including iCloud sync, Safari Google Drive authorization, and native notifications.
• Native behavior: For Drive authorization, notification delivery/clicks, or account-scoped sync verification, also read native-behavior.md.

Default: temporary extension

1. Run bun run build:safari. This builds dist_safari and verifies Safari resource wiring.
2. In Safari Settings > Developer > Temporary Extensions, click Voyager's Reload. If absent, choose Add Temporary Extension… and select dist_safari.
3. Reload the target Gemini, AI Studio, ChatGPT, or Claude tab once to load the current content script.
4. Open the Voyager popup and test the changed behavior.

Safari removes temporary extensions after 24 hours or when Safari quits. Re-add dist_safari; a routine UI refresh does not require signed installation.

Safety and recovery