OpenCues runs in six places, all reading the same ~/.cues/ configuration: Claude Code, OpenCode, Gemini CLI, a shell wrapper, a Chrome extension, and a system-wide Windows host.
A file written once applies everywhere.
The terminal hosts read ~/.cues/ directly. The browser cannot read your disk, so opencues install chrome-host installs a local process that watches the folder and pushes changes to the extension; an edit reaches open tabs without an export step.
| Host | Surface | Feature set |
|---|---|---|
| Claude Code, OpenCode, Gemini CLI | the coding terminal's input | full |
shell (oc-shell) | an input box over your own terminal | full |
| Chrome: rich editors (Gmail, Reddit, ChatGPT) | contenteditable fields | full |
Chrome: plain <input> / <textarea> | search boxes, plain fields | non-cycling blanks only |
| Windows: native text fields | Notepad, Explorer, Win32/WinForms/WPF apps, system-wide | full |
| Windows: Chromium-embedded apps | Slack-class apps | reduced; blanks-only for some |
on-host: and not-on-host: in the cue's config.
By default a cue or blank runs on every host. Its config file can restrict that: the shipped more-formal cue carries not-on-host: claude-code, gemini-cli, opencode, so sentence rewrites run in the shell input box, and in the browser only on the sites its on-site: allow-list names (LinkedIn and web email), but not while you type instructions to a coding agent. on-site: scopes by hostname and wildcard patterns.
Features that need per-word colour are disabled there.
A plain <input> or <textarea> draws its own text; the extension cannot recolour words inside it. Features that depend on the dim and selected states (word cues, cycling) are disabled on those fields at registration, rather than left enabled and failing on use.
in a rich editor
in a plain field
Underscore blanks that need no cycling work in both: the request is typed and the answer is inserted. Blanks whose value is stepped or picked (volume, the settings blank) stay off there, and word cues stay off entirely.