Import from Google Drive, and accepted edits write back

You can now import Google Docs, Sheets, and Slides into Shannon, and when you accept an edit on an imported Doc, Shannon writes it back to the original in Drive. The agent works on the same document your team opens tomorrow: no exporting, no pasting suggestions between windows, no second copy drifting out of date.

Shannon is the AI workspace I’m building. Its agent edits your documents directly, and every change lands as a tracked edit you accept or reject. Underneath it is one bet: Files form the foundation — the agent’s response is the document itself, and the file in front of you is the deliverable. With this release, that file can be the Google Doc your team already shares.

Import your Drive files without moving them

Connect Google Drive once, then choose “Import from Google Drive” and pick your files. They show up in your workspace next to everything else: Docs arrive as readable text the agent can work with, and Sheets and Slides come in alongside them. Importing doesn’t move anything. The file stays in Drive, which remains the one true copy; Shannon holds a text rendition for the agent to read.

Accepted edits land back in the Google Doc

Ask the agent to rework an imported Doc and its edits appear as tracked changes, the same as any file in Shannon: each one marked in place, waiting for your accept or reject. Accepting is what sends a change to Drive. Open the Doc in Google afterward and the edit is there, in the same file your team comments on.

I kept write-back deliberately narrow. It’s Docs-only for now (Sheets and Slides are import-only), and only accepted tracked changes flow back: typing directly into your Shannon copy edits it, not the Doc. The only path back to Drive is a change you accepted.

One click catches up with your team

There’s no live sync; you pull updates when you want them. If a teammate edits the Doc over in Google, the “Sync from Google” button in the editor header brings their latest version into your workspace. And if Drive moved on after Shannon last synced (a teammate edited while you were reviewing), Shannon holds the write-back instead of overwriting their work. The file gets a “Sync conflict” badge in the file tree, and “Sync from Google” catches your copy up. The held edit isn’t sent after that: it stays in your document’s version history, so you can re-apply it to the caught-up copy rather than lose it.

Under the hood

An imported Doc lives in Shannon as two views of one document. The agent reads a markdown rendition, because knowing what’s a heading and what’s bold makes for better edits. Write-back searches the Doc’s plain text — the words you’d see in Google, with no markdown syntax — so a change lands exactly where it should. A conflict check guards every write and holds off if Drive has moved since the last sync. And before every agent run, any stale imported Doc is re-pulled from Drive first, so the agent is never editing yesterday’s copy.

Try it at shannon.bot — no sign-in needed to look around. Connect Google Drive, import the Doc you’ve been putting off, and the next edit you accept will be waiting in Drive when your team opens it.