Bridge for PrusaLink

Bridge for PrusaLink lets web apps you trust send G-code to your own PrusaLink printers over your local network. The web app talks to this extension; the extension talks to the printer. Printer addresses and credentials are stored only in the extension and are never exposed to any web page. How it works - Add your printers in the extension's options: each one's LAN address and an API key (or HTTP Digest, or none behind a trusted proxy). Host permission for that printer is requested at add time. - When a site first asks for access, the extension shows a consent prompt with the browser-verified origin. You pick which printers to share and whether to confirm each print. - The site can then upload and start prints, read status, and cancel — but only for printers you granted, and it never sees a URL or secret. It receives only a name, model, and status. Details - Per-origin consent. No site can reach a printer without your approval, and you can revoke access any time from the popup. - Per-print confirmation (on by default) and a global "pause all" kill switch. - Least privilege: no built-in printer addresses; the extension requests access only to the exact host you enter. - Works with plain G-code and binary .bgcode. Supports API-key and HTTP Digest. For developers: web apps integrate a zero-dependency client library (npm: @tibordp/prusalink-bridge) and communicate over postMessage. Unofficial. Not affiliated with or endorsed by Prusa Research. PrusaLink and Prusa are trademarks of Prusa Research a.s., used here only to describe what the extension talks to.