Manus updates Google Drive connector with Workspace CLI actions for Docs, Sheets, and Slides
Manus added Google Workspace CLI support so one prompt can reply to Doc comments, edit individual Sheet cells, rename Slides, and reorganize Drive folders. Test it if your agent workflows already depend on Google Workspace data and approvals.

TL;DR
- Manus says its Google Drive connector now supports the Google Workspace CLI, expanding from basic file access to “precise actions” across Docs, Sheets, Slides, and Drive from a single prompt connector upgrade.
- The shipped actions are concrete and narrow enough to matter for agent workflows: Manus can reply to specific Doc comments, update an individual Sheet cell, reorganize Drive folders, and change a Slide title, according to the launch thread shipped actions.
- Manus’ announcement post positions this as a move from high-level file handling to granular edits inside existing Workspace assets, including paragraph insertion, slide reordering, and speaker-note updates announcement summary.
- Early user feedback in the launch thread shows the product handling comment resolution inside a live Google Doc, which is the kind of approval-loop task that usually breaks simple file-based automations user demo.
What shipped in the connector
Manus’ update adds Google Workspace CLI support to its existing Drive connector, so the agent can act inside Workspace apps instead of only creating or reading files. In Manus’ launch post, the company describes the change as managing “your entire workflow in Docs, Sheets, and Slides from a single prompt.”
The practical difference is action granularity. The capability list names four specific operations: reply to a Doc comment, update one Sheet cell, reorganize Drive folders, and rename a Slide. Those are narrower than generic “edit this file” commands and better suited to multi-step workflows where the agent has to touch an existing document without rewriting the whole asset.
How precise the new actions are
Manus’ full announcement says the CLI-backed integration supports more surgical changes than the tweet thread lists, including targeted text replacement in Docs, paragraph insertion, spreadsheet updates driven by cross-referenced data, adding or reordering slides, and updating speaker notes workflow examples. That suggests the connector is now exposed to lower-level Workspace operations rather than a few hardcoded templates.
A supporting user clip cited in the thread shows Manus “address and resolve all the comments” in a Google Doc user demo, which is a useful signal for teams using Workspace as the system of record for reviews and approvals. A separate reaction post adds one implementation detail: the integration reportedly reads Google’s Discovery Service at runtime to build available commands dynamically, though that point comes from a third-party summary rather than Manus’ own announcement runtime discovery.