The OpenCues Chrome extension brings blanks and cues to text fields on the web. Type _ in a compose box and the model answers in place; rich editors additionally get dimmed word alternatives you can cycle.
How it renders without breaking pages
The extension uses the CSS Custom Highlight API to paint cues inside the page's own text, so there is no overlay div fighting the site's layout. Rich editors (including ProseMirror and Lexical based ones such as claude.ai and LinkedIn) get the full experience; plain <input> and <textarea> fields run a reduced profile where fills land but nothing needs colour or key interception.
Config without a filesystem
Browsers cannot read ~/.cues/, so a small native-messaging host watches your config folder and pushes changes into the extension live. If you never install the host, the extension still works from its bundled defaults. Site scoping is declarative: a cue or blank can declare on-site: / not-on-site: rules (hostnames, wildcards, path prefixes).
Keys and privacy
You bring your own provider key; the page never sees it, and key changes apply mid-session without a tab reload. Text goes only to the provider you configured. See the security model for the full picture.
Related: AI in any text field · What is a blank? · OpenCues on LinkedIn · OpenCues on claude.ai · GitHub repo