cursor agents can now read, write, and act across google workspace

Cursor shipped Google Workspace plugins on August 3, 2026. Coding agents can now read, write, and act across Gmail, Google Drive, Google Calendar, Google Docs, Google Sheets, and Google Chat — six services in total, accessible without leaving the IDE. You install them from the Cursor Marketplace or the Customize page in a couple of clicks.

what each plugin can do

The six plugins cover meaningfully different surface areas. Drive lets agents search and browse your file hierarchy, open and download content, and create or organize files and folders. Gmail lets agents search mail, read threads, draft and send messages, apply labels, and manage threads. Calendar lets agents read your schedule, create and update events, and find free time across calendars.

Docs and Sheets round out the productivity core: agents can view, edit, and create documents and spreadsheets, update individual cells, and apply formatting. The Chat plugin adds access to Google Workspace team spaces and direct messages — read and send.

Installation works through the Cursor Marketplace (browse and add) or the Customize page inside the app. Once installed, plugins are available to any agent session.

what this actually changes

The practical shift is context. Before this, a Cursor agent working on a feature had access to your codebase, your terminal, and whatever web searches it could run. Now it also has access to the design brief in your Drive folder, the product requirements in a Doc, the calendar block that tells it the release is Thursday, and the email thread where the scope changed last week.

That closes a gap that has made agent workflows frustrating at the edges. You could get an agent to write the implementation, but you still had to manually pull the spec from Drive, paste the relevant context, and keep the agent oriented. With workspace access, that integration step moves inside the agent loop.

The write side matters too. An agent that can draft a status update email, update a tracking sheet, or log progress to a Chat space is doing something qualitatively different from an agent that can only write code. It is becoming part of the team's communication and coordination infrastructure, not just a code-generation tool.

the honest caveats

Workspace access means agents operating under your credentials on services that contain everything — email, files, calendar, messages. Cursor has not published a detailed data-handling spec for what these plugins transmit back to its servers versus processing locally. Before enabling them on anything sensitive, it is worth checking the Marketplace listing for each plugin's permissions scope and data policy.

For individual developers and small teams working in consumer-grade Workspace accounts, that threshold is lower. For anyone on Google Workspace for Enterprise with data classification requirements or contractual obligations around where data flows, it is worth more scrutiny before the plugins go into daily use.

the broader trend

Cursor's Google Workspace integration is the most visible example of a pattern playing out across the AI coding tool market: coding agents expanding their context surface beyond the repository. Microsoft already wired GitHub Copilot to Microsoft 365 (and vice versa) via the Graph API. Claude Code added image and PDF attachment for reading design assets. Kiro integrates with task trackers. The differentiator is no longer just which model handles code — it is which agent can assemble the full context a developer actually works inside.

Cursor's version is notable because it covers the Google side, which is where a lot of independent developers and startups actually live. If your stack is GitHub + Vercel + Google Workspace, this makes Cursor significantly more useful as an agent platform rather than just a code editor.