Claude Google Docs: Add-on, Connector, Limits and ChatGPT

Claude works in Google Docs through Anthropic’s add-on, Claude for Google Workspace. It opens in a sidebar beside the doc you have open, where it can rewrite an executive summary, cut a long brief down, or turn a list of next steps into a table with owners and dates. It is in beta on Pro, Max, Ultra, Team and Enterprise.

The other Anthropic route is the Google Docs connector, which edits a Google Doc from inside a Claude chat. If you connected Google Drive and found Claude could read your docs but not change them, this is the reason: Drive reads, the Docs connector edits. Every fact about Anthropic, Google and OpenAI below comes from their own pages, read November 9, 2026.

The last route is ours. A Context Board Docs board holds pages inside pages that Claude, Claude Code and Codex all read and write, with each line signed by the agent that wrote it. It has no live link to Google Docs, and a later section says exactly what that means. Context Board is ours, so weigh the bias.

Every way to use Claude with Google Docs

Each route puts Claude in a different place, with different rights over your file. Pick the place first.

Claude’s routes all draw on your plan. Anthropic’s pricing page lists Pro at $20 a month, or $17 a month billed yearly, and Max from $100 a month. A long editing session counts toward the same limits as your chats, and our guide to Claude’s usage limits shows how fast they go.

Claude for Google Docs: the add-on inside a document

This is the route most searches for “Claude for Google Docs” mean. Anthropic released it in public beta on October 6, 2026, for Google Docs, Sheets and Slides at once. The Marketplace listing names Anthropic as the developer.

Set it up. From Anthropic’s help article:

1. Check that your Claude plan is Pro, Max, Ultra, Team or Enterprise, and that your Google account may install Marketplace apps.
2. Install Claude from the Google Workspace Marketplace. One install covers Docs, Sheets and Slides.
3. Open a doc and choose Extensions, then Claude, then Open Claude.
4. Allow the two permissions Google asks for, then sign in with your Claude account.

Use Chrome, Edge or Safari. Firefox is not supported in the beta: the sidebar loads, but actions don’t complete. If Claude is missing from the Extensions menu, Alt+/ (Option+/ on a Mac) and typing “Claude” finds it.

What it does in a doc. Anthropic’s examples:

• Rewrite an executive summary so it leads with the recommendation, in one paragraph.
• Cut a 14-page brief to 6 pages and keep every numbered requirement.
• Turn “Next steps” notes into a table with owner, action and due date.
• Check a contract for defined terms that are used but never defined.
• Make every heading sentence case and fix the numbering in one section.
• Answer questions about the doc without editing it. Select text first to point Claude at it.

How edits work. The default mode is Ask before edits: Claude says what it plans to change and waits for you to click Allow. Accept all edits lets ordinary content changes go through without stopping, though links, outside images, web addresses and access changes always ask. In Docs you can also ask Claude to propose text changes as cards, which you accept or reject one at a time. The launch post says each card highlights the passage it would change. Otherwise Claude’s edits land as direct edits, recorded in File, Version history under your name.

What it can’t do. It works only on the file you have open. It can’t open, create or copy other Drive files, export a PDF or share the file. It can’t read, reply to or resolve comments, or accept existing suggestions. It reads and edits every tab but can’t add, rename or reorder tabs. The sidebar has to stay open, because closing it stops the task, and Google stops any one operation after six minutes. Word files opened in Docs aren’t supported, so use File, Save as Google Docs first.

Chat history stays in your browser. Anthropic says conversations are saved per file in the browser. They don’t follow you to another computer, a private window or a copy of the doc.

Where your data goes. The open file, your messages and attachments go to Claude. Anthropic says it does not train on that content, and inputs and outputs are deleted within 30 days except as its retention article describes. The add-on asks Google for no Drive, Gmail or Calendar access, and it is not for protected health information.

The Google Docs connector: edit Docs from a Claude chat

The add-on brings Claude into the doc. The connector works the other way round: you stay in a Claude chat, and the doc opens beside it.

Anthropic’s Google Workspace connectors article treats Google Docs as its own connector, separate from Google Drive. With it on, Claude can:

• Edit a Google Doc live in a pane beside the chat, while you edit the same file.
• Create new Google Docs, Sheets and Slides files.
• Read and work with comments and suggestions.

The pane works on Claude on the web in Chrome, and in Claude Desktop when its built-in browser is on. Elsewhere, the file card has Open in Google.

Turn it on.

1. In a Claude chat, click the plus sign.
2. Hover over Connectors and switch on Google Docs.
3. Paste a doc’s link, or ask for a new doc and say “Google Doc”. A plain request for a “doc” makes a local file to download instead.

Claude reaches only the files your Google account can open, under your existing sharing. It re-reads the doc before each change, and Anthropic still advises checking the result in a busy file.

Is Claude’s Google Docs integration read-only?

The forum threads asking this usually have only Google Drive switched on. Per Anthropic’s article, the Drive connector searches and retrieves Google Docs and reads them as text only, so images inside a doc are skipped. It can create folders, upload files, and share, move or trash files with your approval, but it does not edit what a doc says. A doc you add from Drive also has to fit in Claude’s context window.

So use Drive to bring a doc into a chat, and the Docs connector to change it. Drive still does the searching, uploading and sharing for the Docs connector.

Plans. The article says the Google Workspace connectors are available to all users of Claude and Claude Desktop. On Team and Enterprise, an owner or primary owner has to turn them on for the organization first. Claude Code’s MCP docs list claude.ai connectors among the sources of its MCP servers, so a connector you set up on claude.ai can reach Claude Code too. Our guide to MCP explains the protocol underneath.

Want a doc that lives in Claude rather than Google? Claude’s own Docs template is an artifact, and our guide to Claude Artifacts covers how those are shared and stored.

ChatGPT and Google Docs

ChatGPT reaches Google Docs through one app, Google Drive. OpenAI’s Google Drive app article says Google Docs, Sheets and Slides actions come through the Drive app rather than separate apps.

Connect it.

1. Open Plugins or Apps in ChatGPT, whichever your version shows.
2. Find Google Drive and connect your account.
3. Sign in with the Google account that can open the files you need.
4. Review the permissions Google asks for, finish Google’s sign-in, and return to ChatGPT.

What it can do. OpenAI’s example prompts run from “Find the latest project plan in my Google Drive and summarize the next steps” to “Update this document with the action items from our meeting.” Reading and changing are separate permissions. The app can request different Google permissions for reading files, viewing file details, and creating or updating files, and any action that changes a file needs the matching permission and must be allowed in your workspace. ChatGPT may ask you to confirm before it acts.

Creating native Google Docs. That is the job of ChatGPT Work, OpenAI’s agent for longer tasks and finished files. Its documents article says Work supports native Google Docs, Sheets and Slides when the relevant Google Workspace app is enabled. The steps: connect the app, open Work, ask it to create or edit a Google Doc, choose the account or file, approve the action, then review the file in Google Docs. You can also save a doc you like as a template, from a .docx or a Google Doc link, and reuse its headings and tone for new files.

Plans. OpenAI’s Work and Codex article says Work is available on ChatGPT web and mobile for eligible paid plans. Google Drive itself depends on your plan, location and workspace settings, and in a managed workspace an admin may need to turn it on.

When it fails. OpenAI notes that finding a file’s name does not mean ChatGPT read its contents. Start a new conversation with Google Drive on, paste the doc’s link, and ask it to read that file. If Google blocks authorization at work, a Google Workspace admin has to approve the OpenAI app for the permissions your actions need.

A worked example: call notes to a proposal, and a decision log

Take a solo consultant with two Google Docs: Northwind call notes, written during a discovery call, and Decisions, a running log of what they have agreed with each client. The names are an example. Over one week, the routes split like this.

1. Monday, in the doc. They open Northwind call notes, select the Next steps list, and ask the add-on: “Turn this into a table with owner, action and due date.” Claude shows the change and waits. They click Allow.
2. Tuesday, in a chat. With the Docs connector on, they paste the link to the call notes and ask: “Make a Google Doc called Northwind proposal from these notes, with scope, timeline and a price section I fill in.” The new doc opens beside the chat, and they write the price while Claude drafts the timeline.
3. Wednesday, back in the doc. They open the proposal, select the summary and ask for it to lead with the recommendation. The add-on proposes it as a suggestion card, and they accept it.
4. Thursday, the decision log. In a chat, they ask Claude to add a line to Decisions: “Northwind: yearly billing, kickoff December 1.” The connector writes it into the log.

Every step worked. The gaps show up after. Add-on edits sit in version history under the consultant’s name, so the history can’t tell Claude’s lines from theirs. The add-on’s chat stays in that one browser. Codex, which they use for client code, and ChatGPT each connect to Google on their own, with their own permissions, so the decision log only stays current through whichever app they happened to open. Our guide to running a pipeline with Claude covers the client side of this work.

Claude Google Docs not working? What to check

Most failures come down to the plan, the browser, the connector you switched on, or an admin setting. Work down the list, from Anthropic’s two help articles.

1. Check the plan. The add-on needs Pro, Max, Ultra, Team or Enterprise.
2. Change browser. The add-on beta runs in Chrome, Edge and Safari. On Firefox, or with strict tracking protection, messages send and nothing happens. The connector’s live pane wants Chrome on the web, or Claude Desktop with its built-in browser on.
3. Claude reads but won’t edit. You have Google Drive on and Google Docs off. Turn on the Google Docs connector.
4. “This application is not allowed by your administrator.” Your Google Workspace admin restricts Marketplace apps. They can allowlist Claude under Apps, Google Workspace Marketplace apps, Settings in the Admin console, or install it for you.
5. “Access blocked: your institution’s admin needs to review Claude for Google Drive.” An admin goes to admin.google.com, then Security, Access and data control, API controls, Manage third-party app access, adds the app named Claude and sets it to Trusted. Reconnect after about 15 minutes. One approval covers Docs, Sheets and Slides.
6. “Claude for Google Workspace needs a Claude account.” You signed in before with an API key, Amazon Bedrock, Google Vertex AI or a gateway. The add-on takes a Claude account sign-in.
7. Every action fails. Several Google accounts are signed in to the browser. Open the doc in a window signed in to one account, such as a separate Chrome profile.
8. A long job stopped. Google stops an operation after six minutes, and closing the sidebar stops it too. Ask Claude to continue, or split the job.
9. Still stuck with the connector. In Claude, go to Customize, Connectors, select the Google connector, click Disconnect, then sign in again on your next request.

Docs every agent can read and write: the Docs board

Every route above is one AI on one Google file, with the permissions that AI was given. That fits most document work. It stops fitting when your docs are where several agents keep things current: a decision log that Claude adds to from a chat and Codex reads before it writes code, or call notes your agents all search, and you want to see who wrote which line.

Context Board is a web app at board.contextbolt.com, a workspace you share with your AI agents. A Docs board holds plans, notes and specs as pages inside pages, and any app you connect over MCP reads and writes them: Claude, Claude Code, Codex and Cursor. ChatGPT writes to a board on Business and Enterprise/Edu workspaces, where OpenAI’s custom MCP article allows write actions. On other ChatGPT plans, use Claude or Codex for the writing.

Client notes Live Example

PagesFrom Google Docsnow

• Northwind proposalFrom Google Docs1 page
• Decisionsdecisions.docx1 page
• Call notesA folder of .docx files6 inside
• Onboarding planonboarding.docx1 page

Board activitynow

• Claude wrote on the page Decisions3m
• Codex wrote on the page Onboarding plan20m
• Claude made the page What we heard1h
• You edited Northwind proposal2h

This week

• Import the call notes
• Send Northwind the proposal
• Log the pricing decision

PagesFrom Google Docsnow

9

That is an example board with example names. What a Docs board gives you:

• Pages inside pages. Nest a page in a page, drag it somewhere else, fold a branch away, and link any page with [[.
• Blocks. Type / for headings, to-dos, toggles, tables, a page inside, or a live widget from your board.
• Agents that write. Your agent reads a page as Markdown and writes at the end, after a part, in place of a section, or as a new page inside another.
• A name on every line. Each write glows once in the agent’s color with its name, and Board activity lists it with Undo. Turn on Agent colors and every line an agent wrote keeps a thin line in its color.
• Page history. The last 100 changes to a page, kept for 30 days, each with who made it. Restore this version puts one back.
• A way back out. Download a page as Markdown, or share the doc as a small website with each page at its own address.

How it relates to Google Docs. There is no live connection. In Google Docs you choose File, then Download, and pick Microsoft Word (.docx), then drop the file into Import. The Google Docs and Word import keeps headings, bold, italic, links, lists, tables and pictures, up to 60 pictures in one import. It keeps a document’s structure, not its look, so fonts, sizes and colors stay behind. For many docs at once, it reads a .zip of your Drive from Google Takeout, and folders become pages holding pages. The pages are a copy: edits on the board stay on the board, and later changes in Google Docs don’t follow.

Set one up.

1. In Google Docs, choose File, Download, Microsoft Word (.docx).
2. In Context Board, choose New board, then Import a document, and drop the file. The preview shows the pages it will make, and Undo import takes it all back.
3. Connect your agent once. For Claude Code or Codex, link your computer with the one line from Connect. For the Claude app, add the board’s address and click Allow.
4. Ask for the work: “Read the six call pages and write a page called What we heard.” The new page lands with a link to each call it came from, signed by the agent.

Context Board is free for 3 days, then $12 a month for every kind of board, docs, sheets, slides and dashboards included. Your agents work on the plans you already pay for, so there are no AI credits to buy.

What you give up. It is not Google Docs. There is no live sync, and teammates who work in your Drive won’t see the board’s copy. If your doc stays in Google and one Claude is enough, the add-on is the lighter choice. Moving off Notion as well? Our Notion alternatives for solo founders who use AI compares the options, and Context Board vs Notion puts the two side by side.

Which way to pick

Pick by where the doc lives and who has to touch it.

• Your doc lives in Google and you edit it daily: the Claude for Google Workspace add-on. Select text, ask, allow.
• You start in a Claude chat, or want a new doc made for you: the Google Docs connector, with Drive on for finding files.
• You only need Claude to read a doc: the Google Drive connector.
• You work in ChatGPT: connect Google Drive and use Work to create or edit the doc.
• Several agents keep the same docs current, beside the rest of your work: a Context Board Docs board, imported from your .docx download.

If your numbers sit in Google Sheets too, our guide to Claude and Google Sheets covers the same add-on in a spreadsheet. Otherwise, install the add-on, open a doc you know well, and ask it to turn one list of next steps into a table.