A browser extension cannot read your disk. A small local process bridges the gap: it watches ~/.cues/ and pushes your configuration into the extension, live. Without it, the extension still works from a copy baked in at build time.
Edits reach every open tab in about 300ms, no page refresh.
Installed once with opencues install chrome-host, the host process watches ~/.cues/. When a file changes it rebuilds the bundle and hands it to Chrome, which stores it and broadcasts the change; every open tab reloads its configuration at once. The same pipe runs local scripts for the extension, which is how volume _ can read and set a real device from inside a web page.
| Step | Command or action |
|---|---|
| build and load the extension | opencues install chrome |
| copy the extension's id | chrome://extensions, Developer mode: the 32 letters under the name |
| install the host | opencues install chrome-host --extension-id <id> |
| reconnect | reload the extension once |
The extension falls back to the copy baked in at build time.
A user who installs the extension and never runs the host still gets the shipped configuration: spelling, formality, the lookup blanks. The baked copy is static; it refreshes when the extension is rebuilt, or on demand with opencues sync chrome. The live host replaces it the moment it connects.
Entries marked not-on-host: chrome are dropped from the bundle rather than shipped broken, using the same filter every host applies to decide what it can support. Script-backed entries stay in the bundle with their script bytes stripped: the page never runs a script itself, the host runs it from disk.