The browser extension

Load it from the FlowKy Chrome build, then open it from the toolbar or the side-panel menu. It is a Chrome side panel, so it sits beside a page rather than covering it.

Signing in connects it

There is no key to paste. The panel reads your flowky.ai session cookie, so signing in to the website on the same browser is what connects the extension — that is the entire step. The cookie is exchanged server-side for a scoped, revocable token; the cookie itself is never stored.

If you are signed out, the panel shows a Connect button rather than pretending to work.

The VS Code bridge

The browser and the editor talk over a local WebSocket on 127.0.0.1. Nothing in that channel leaves your machine. Copy the pairing code from the VS Code extension into the panel's Settings tab, once. The panel reconnects on its own afterwards, including after Chrome has evicted its background worker.

Checking it worked

The panel's status line shows the bridge state. Press Capture on any page: a full-page screenshot should arrive in VS Code. If the panel reports that the background worker did not wake up, reload the extension at chrome://extensions — that is a known Chrome behaviour after long idle periods, and the panel now retries before showing you the message.