No, and unlike most unsupported sites, this one has a structural reason rather than a missing test pass. Modern Google Docs renders your document to a canvas element, not to DOM text. OpenCues' entire mechanism (reading your text from DOM nodes and painting highlights onto them) has nothing to attach to.
Why canvas rendering blocks it
The Chrome extension works by walking DOM text nodes to read what you've typed, and by using the CSS Custom Highlight API to paint cues inside the page's own text. Both halves require real text nodes: the repo's rendering docs state directly that the Highlight API only works on DOM text nodes. A canvas-rendered editor exposes pixels, not text nodes, so OpenCues can neither read your document through its normal path nor render a dim onto a word. This isn't a quirk to patch around; it's a different rendering paradigm.
What this means in practice
| Surface | Status |
|---|---|
| The Google Docs document body | Not supported: canvas-rendered, no DOM text |
| Gmail compose | Fully supported, the extension's most reliable surface |
| Plain inputs and textareas across Google properties | Reduced profile: single-answer blanks fill |
Honest workarounds
Draft the paragraph where OpenCues works (Gmail compose is closest in spirit to a document editor, and renders bold and italic properly), then paste into Docs. Yes, that reintroduces a copy-paste step, which is exactly the friction OpenCues exists to remove; this page won't pretend otherwise. For grammar specifically, Google Docs has its own built-in checking, and running OpenCues' grammar tooling on the draft before pasting composes fine with it.
Will this ever change?
Not by incremental extension work. Supporting a canvas editor would require a fundamentally different integration (Google's own APIs rather than DOM reading), which is a different project from the current extension architecture. The repo contains no work in that direction, so per the project's no-unshipped-claims rule, the honest status is: not supported, no timeline. Sites built on DOM-based editors (ProseMirror, Lexical, Quill, plain contenteditable) are where browser support grows.
Related: OpenCues on Gmail · The Chrome extension · OpenCues on Notion · GitHub repo