# Show HN: Strunk – revise Google Docs from Claude without breaking comments > Source: > Published: 2026-09-01 08:32:12+00:00 # Human feedback, without leaving Claude Strunk brings each Google Docs comment back to the tool that holds your context, then writes your approved edits onto the exact spans your reviewers marked, leaving their comments intact. Nothing changes until you approve it. > **Pull comments.** Elwyn wants this paragraph tightened. Choose the direction, and I'll draft the revision. - Clarify the point - Cut the length - Strengthen the claim Reply with 1, 2, or 3. The round trip ## A marked-up draft, without the copy/paste. The reviewer gets a normal Google Doc. You get each comment back in the AI tool that still has the context to make the right edit. ### Publish the draft William sends The Elements of Style from his AI tool to a native Google Doc Elwyn can review. ### Bring back reviewer comments Elwyn's comment returns to the AI tool with the exact text he highlighted, so William can revise with context. ### Decide how AI should revise William reviews Elwyn's comment in his AI tool and chooses how to tighten the passage. ### Update the Google Doc seamlessly William asks Strunk to update the Google Doc, and Strunk applies the revision while preserving the comment thread. Catch the AI tells ## Your voice, even when AI does the drafting. You care how your writing reads, and an AI left alone reaches for a flat, hedging register that isn’t yours. Strunk holds every draft, revision, and reply to the rules you write by. What your reviewer opens is the draft you would have written with more time. [Set your writing rules](/sign-in?returnTo=/account/writing&placement=writing_rules) The AI default The problem isn’t the writing, it’s the review loop. How you write The review loop is the problem. The Elements of Style ## Get the second draft first. Turn on the ten rules from the book Strunk is named after and your AI tool writes to them from the start, so the prose arrives already cut. - Omit needless words - Prefer the active voice - Be definite and specific - Cut intensifiers - Prefer the plain word [Browse the rules](/sign-in?returnTo=/account/writing&placement=strunk_rules) As drafted 24 words There is no question but that the review process has a tendency to be the thing which ends up slowing the whole team down. Omit needless words 7 words The review process slows the team down. Security ## Security, with narrow access. Strunk only moves the review loop you ask it to move. Sign-in, Google Docs access, and stored data are kept deliberately limited. ### WorkOS handles sign-in You sign in through [WorkOS](https://workos.com/security), a SOC 2 Type 2 certified provider with GDPR and CCPA compliance, third-party penetration tests, and external code audits. WorkOS manages the Google connection, so Strunk never sees your Google authentication tokens. ### Only docs you choose Strunk can work with docs it creates, or docs you explicitly open with it. It cannot browse the rest of your Google Drive. ### No stored document content Strunk does not store document bodies, titles, URLs, or reviewer comments. It only keeps the small record needed to update the right doc later. ### No access to your AI tool workspace Strunk only answers the tool calls your AI tool sends to it. It does not fetch your chats, files, environment variables, or workspace context. Pricing ## Three documents free. Then $9 a month. What you get - Unlimited revisions on every document you publish - Bring reviewer comments back to your AI tool - Update the same doc after you approve edits - Reply to and resolve reviewer comments ### Free Start here$0 Your first 3 documents, with unlimited revisions on each. No card required. [Start free](/sign-in?returnTo=/account&placement=pricing) ### Pro $9/mo Unlimited documents. $90/yr if you pay annually, which is two months free. [Get started](/sign-in?returnTo=/account&placement=pricing) FAQ ## Short answers before you install. ### Do reviewers need Strunk? No. Reviewers comment in the Google Doc you share with them, just like they normally would. ### Is this another document editor? No. Strunk is the bridge between your AI tool and Google Docs. You still write where your context lives and review in Docs. ### Which AI tools does Strunk support? Strunk has install paths for Claude, ChatGPT, and Codex. Each uses the same remote MCP review workflow: publish, pull comments, decide, update, reply, and resolve. ### What Google access does it need? Strunk uses Google's limited drive.file permission. It can work with docs it creates or docs you explicitly open with it. The rest of your Drive stays out of reach. ### How is Strunk less invasive than a default Drive connector? Most Drive connectors search across files, so they often need broad read access. Strunk serves a narrower review loop: publish this doc, pull comments from this doc, update this doc. That lets it use picked-document access instead of asking to browse everything in Drive. ### Does Strunk store my docs? No. Strunk does not store doc bodies, titles, URLs, or comment text. It only stores the minimal mapping needed to update the right Google Doc. ### Will updates break existing comments? No. Strunk updates the existing doc instead of replacing it, so reviewer comments stay in place. ### Who approves revisions? You do. The AI tool can draft a response and revision, but Strunk only applies changes after you approve them there. ### What counts as a document? One Google Doc that Strunk publishes or connects for you. Revisions don't count: publish, pull comments, and re-publish the same document as many times as you need. Your first 3 documents are free. ### What happens if I cancel? You keep access until the end of the period you've paid for. After that your existing documents keep working: you can still pull comments, reply, resolve, and publish revisions to them. You just can't start new ones. Ready for the next marked-up draft ## Install once. Run every review from your AI tool. [Get started free](/sign-in?returnTo=/account&placement=footer)