Send from your browser

1. Download the ZIP above and extract it to a folder you will keep. The extracted folder must contain manifest.json.
2. Type chrome://extensions into Chrome’s address bar. In Edge, use edge://extensions; in Brave, use brave://extensions.
3. Turn on Developer mode, choose Load unpacked, and select the extracted folder containing manifest.json.
4. Pin PasserJack from your browser’s Extensions menu for easy access to its settings and recent sends.

This is not a Chrome Web Store installation. If your organization disables Developer mode or unpacked extensions, use the web app and follow its browser policy.

The 0.1.0 download above uses an API key. Newer builds may show Sign in to PasserJack in extension Settings. When available, use it, check the account on the consent screen and confirm the destination email in the extension. Browser sign-in requires the deployment owner to enable the installed extension ID; the button alone does not mean it is enabled.

1. Open PasserJack’s account menu, choose Settings, then Agents and API keys.
2. Create a dedicated key named for this browser with read and write access, then copy it. Read permission covers your whole ordinary Board. Leave Edit anything off to limit changes to items this key creates.
3. Open the extension’s popup and choose Settings. Keep the PasserJack address as https://passerjack.com unless you use your own deployment.
4. Open Advanced API key if shown. Paste your key, choose Test this key, and confirm the displayed email belongs to the intended account.
5. Choose Save. Right-click a link on an ordinary web page, select the PasserJack send action, and confirm it arrives on your board.

The key or sign-in tokens are stored in this browser profile on this device, never browser sync. In newer builds, Disconnect removes the local connection and attempts to revoke browser sign-in. If that fails, revoke it from Agents and API keys. API keys always need separate revocation there. Check the destination after connecting or changing accounts.

• A link or page becomes a link card.
• Selected text becomes a note, with its source page recorded.
• An image is downloaded and attached when permission and your plan allow it. Files and images require a paid plan.

The extension tags sends with from-browser by default. Change or remove that tag in its settings. Sending to the vault is optional; plaintext reaches the server for encryption and cannot be read back by the extension. Titles and other metadata remain readable on the server. See how vault capture works.

The extension requires context menus, local storage, notifications and access to PasserJack. Builds with browser sign-in also request Identity to open the sign-in window; they do not request your Chrome profile email. When it needs to download an image, it can ask for access to the image’s host. If you decline, the extension sends the image address as a link instead and reports that result.

The optional Let me send images from any site setting grants broader image-download access. Leave it off to decide per site. You can remove permissions from your browser’s extension settings.

Manual installations do not receive automatic store updates. To update, replace the files in your extension folder with a newer download, then choose Reload for PasserJack on your browser’s extensions page. Keep the folder in place while the extension is installed.

If a send fails, open the popup for the message, test your key again, and check its write permission and your account limits. Some browser pages and image hosts restrict access. Confirm the item arrived before retrying to avoid duplicate saves.

To uninstall, remove PasserJack from the browser’s extensions page and revoke its dedicated API key in PasserJack.