Your coding agent, next to your Google Doc.
The problem. Writing a long paper in Google Docs keeps running into two walls. Either you don't know the advanced feature that would do the job, or Google Docs doesn't do it well at all: numbered references that stay right as the paper changes, cross-references, one term or one format kept consistent across sixty pages. Google has Gemini in there, and it still left us fixing reference numbers by hand. So Docs puts the coding agent you already have next to your paper. It knows Google Docs, sees the whole document, fixes the hard parts in place — reference numbers included — and answers your comments.
What it does about it
- Sits beside the document, in a second window or in Chrome's side panel, and reads the document's structure — headings, sections, the runs of text — so it can reason about the whole thing.
- Does the hard parts — the ones that need an expert of the tool, or that the tool lacks — in place through Google's own Docs API: numbered references kept in order as you add and move them, cross-references that point where they should, a term or a format made consistent across the whole paper, a rewrite of a section, a table of contents that matches the headings.
- Answers comments: mention it in a comment while the app is open and it replies there.
- Runs on the coding agent already on your computer — Claude Code, Codex or the Gemini CLI — on your own subscription. The document goes to Google as it always did; nothing goes to us.
How you get it
Docs runs through PriorStates Hub and is installed from the marketplace in Desk. Today it needs a Google OAuth client you create in your own Google account (a few minutes; the app walks you through it), because Google's document scopes are the sensitive kind; the tokens stay on your computer.
Early: built for our own papers first. If you write long documents in Google Docs and are willing to set up Google access once, it is ready for you; a one-click sign-in follows when Google has verified the app.