Skip to content

Save to Google Docs

Connect your Google account once and agent output can leave the app as a real, editable Google Doc — headings, links, and formatting included.

  1. Open Settings → Google and click Connect Google.
  2. Your system browser opens Google’s sign-in. Pick the account you want files saved into and approve the single Drive-files permission.
  3. The browser shows “Google connected” — back in the app, the tab now shows your account with a Disconnect button.

Sign-in uses Google’s standard flow for desktop apps (your password is only ever typed on google.com). The app stores its tokens encrypted on this device.

Once a transcript has content, a Docs button appears in the agent window’s actions row (next to Copy and Export). One click:

  • converts the transcript’s markdown into a real Google Doc (headings become headings, links stay clickable),
  • files it under Mastery HQ → <workspace name> in your Drive,
  • and opens the new Doc in your browser.

Once connected, Google destinations appear across the app (each button only renders while you’re connected):

  • Command Center -> Sheets - the dashboard’s export range lands as a real Google Sheet (same columns as the CSV export).
  • Benchmark -> Doc / Sheet - after a run, save the full markdown report as a Doc or the leaderboard as a Sheet.
  • Sprint Board -> cloud button - next to the project name; saves a board snapshot (columns, cards, statuses) as a Doc.
  • Agent transcript saves leave a record - after a Docs save, a “Saved to Google Docs: ” line is added to the transcript so the URL stays findable later.
  • Settings -> Setup shows an Accounts group with your GitHub and Google connection state at a glance.

Read files back, keep running logs, archive automatically

Section titled “Read files back, keep running logs, archive automatically”

Three more Drive powers once you’re connected:

  • Read a saved file back into a conversation — type drive <query> in any agent pane (like recall). The newest matching file Mastery HQ created comes back as text (Docs as Markdown, Sheets as CSV) and rides along with your next message. The app still only sees files it created.
  • Grab any Drive file with drive pick — Google’s file picker opens, you choose a file, and that specific file becomes readable to the app (that’s the official escape hatch in the files-it-created permission — you grant access one file at a time, by picking it). Needs a one-time API key from your Cloud Console pasted into Settings → Google.
  • Running logs instead of one-off exports — the Command Center’s Log row button appends one summary row (date, ships, active hours, spend, runs, success rate) to a Command Center metrics log Sheet that grows over time.
  • Auto-archive transcripts — flip the toggle in Settings → Google and every clean agent run silently saves its transcript to Docs, leaving the link in the pane. The Docs sibling of the GitHub auto-maintenance policy.
  • Privacy by construction — the connection uses the drive.file scope: the app can only see files it created. It cannot list, read, or modify anything else in your Drive.
  • The same primitive understands spreadsheets (CSV → Google Sheet); more surfaces arrive in future releases.
  • Disconnecting (Settings → Google) forgets the tokens on this device. Files already saved stay in your Drive — they’re yours.