When I introduced my Remy, the Google Docs skill for Claude, back in August, the article ended with a promise: Update it when Google published the suggestions API officially. Now, here we are!
Untel recently Remy proposed its changes as coloured markup — mint for insertions, pink strikethrough for deletions — because the one thing everybody actually wanted, native Google Docs suggestions with the familiar Accept/Reject buttons, was locked away in Google’s Workspace Developer Preview Program. Preview terms forbid shipping that capability in a public tool. So I wrote: the moment Google makes it generally available, Remy gets it.
That moment came. In October Google promoted the suggested-edits and comments endpoints of the Docs API to general availability — and Remy 0.9.0 was out two days later.
What changes for you
Everything Remy proposes now lands as a real suggestion, exactly as if a human collaborator had switched their Google Doc to “Suggesting” mode:
- Every insertion, deletion, replacement and formatting change gets the native Accept ✓ / Reject ✗ buttons in the document.
- The suggestions are clearly attributed to your Remy robot account — you always see who proposed what.
- You review on your phone, in the browser, wherever — it is plain Google Docs, no special tooling on the reviewing side.
And my favourite part: suggestions work on comment-only links. Until now you had to grant Remy’s robot account Editor rights so it could write markup. With 0.9.0 a commenter link is enough for Remy to propose full-blown edits. You can let Remy loose on a document while structurally guaranteeing — via Google’s own permission system — that it cannot change a single character without a human clicking Accept. That is the trust model I wanted from day one – you do not have to give the AI full access to all your GDrive documents.
What happened to mint and pink?
The coloured markup is still there, demoted from default to option. Say “use markup” (or pass --markup) and Remy works the old way. It also remains the automatic fallback for the rare cases where suggestions are not available.
One of those cases deserves honesty: during the beta we observed a Google API quirk where a suggestion write can silently be applied as a direct edit instead. Remy therefore probes every document with a zero-width test suggestion before its first real write, verifies afterwards that the write really arrived as a suggestion, and rolls back and switches to markup if it did not. Deterministic code, no surprises — the same philosophy as everywhere else in Remy’s ~2,500 lines of Python.
Nothing to do if you already run Remy
Remy checks GitHub once a day for new releases, so existing installations offer the update by themselves. New here? Installation is still one pasted prompt in the Claude app (Code window):
Install the Remy plugin for me: run "claude plugin marketplace add dirkpaessler/remy" and then "claude plugin install remy@remy-marketplace"; after that, find the installed plugin's remy.py and run its install-mcp command so Chat and Cowork are covered too (install uv first if it is missing). If claude is not on the PATH, use the CLI bundled inside the desktop app.
Everything else from the August article still holds: Remy runs entirely on your machine, talks only to Google’s APIs and (for the version check) to GitHub, uses a robot account instead of your personal login, and the code is open — github.com/dirkpaessler/remy.
A heartfelt thank-you to the beta testers who ran the preview build for the past two months and reported every oddity, screenshot by screenshot. You are the reason 0.9.0 could ship with the Accept button on by default.
