GPT DotFIELD GUIDE
Home/Integrations
Integrations

How to connect Google Drive to your ChatGPT Dot: setup, what it reads on its own, and what to do when a Sheet breaks or an upload is refused (OpenAI Dots)

Connect the Google Drive plugin in ChatGPT and your Dot can find, read and update Docs and Sheets with the same permissions. Setup, what it reads without being asked, fixes for broken Sheets, stalled transfers and refused uploads, and prompts to copy.

GPT Dot · Updated

The short version: what a Dot does well with Google Drive, how to set it up, where it gets stuck

A ChatGPT Dot (OpenAI Dots) works in Google Drive through the Google Drive plugin in ChatGPT: it can find files, read them and update Google Docs and Sheets, with the same permissions you gave that plugin (Connect computers and apps). Below are the verdict, the setup, the usual blockers with their fixes, and one message to start with; the named examples and the reports of what went wrong follow. To set up the Dot itself, start with getting started.

Is it worth connecting?

Yes, if your working documents already live in Drive. Finding and reading the right file worked for almost everyone who tried it: Vini Parizotto's Dot dug up a two-week-old planning doc without being told where to look, and Max Weinbach's does his expenses from email and Drive. Keeping a Doc or Sheet current on a schedule and spotting a clash between files also work well; Ted's Dot caught one candidate entered twice in a recruitment sheet. Three things need care. Once Drive is connected, the Dot also reads files there on its own, not only the ones you name. A file the Dot calls finished may not work in the app it is meant for, and moving big files between Drive and the Dot's own computer has stalled or failed. And an upload can be refused before it runs, even with Drive set to allow all actions, when the safety check isn't satisfied that the folder is meant for that data. Let it read, update and draft, and open the result yourself before you rely on it.

How to set it up in seven steps

  1. Connect the Google Drive plugin. In ChatGPT, open Plugins, find Google Drive and connect the Google account that owns the files. Since OpenAI unified Google's file apps, Docs, Sheets and Slides actions all come through this one plugin; if you connected the older separate Google apps, reconnecting Google Drive gives you the newer actions. Plugin connections are shared between ChatGPT, ChatGPT Work, Codex and your Dot (Dots privacy, security and safety FAQs), so a Drive connection you already have carries over. Adding the Dot to Slack or Microsoft Teams does not connect Drive, because channels and apps are separate connections (Meet dots).
  2. Decide how far it can see. The Dot can open everything that Google account can open, and it doesn't wait to be asked: a Dot looks for useful updates in permitted connected sources before you make a request and saves private notes about them, and you can't view or delete those notes one by one (Dots privacy, security and safety FAQs). padiwe2753's Dot opened a newer private thesis document without a fresh request and flagged a sentence pasted in by mistake (OpenAI Community), and 西岡賢一郎's pulled his next to-dos from meeting minutes that were just sitting in Drive (note). There is no setting that limits this background reading to chosen folders or switches it off while keeping Drive connected. If that is too much, do what Takemi Terashi did: give the Dot its own Google account and share one folder with it, so that folder is all it can see. Sharing another folder with that account widens its view again. To cut access, disconnect Google Drive on the Plugins screen; as Bluemediaworld's permissions guide notes, that stops new access but doesn't erase what the Dot already learned.
  3. Decide what it may change. Your existing app permissions apply to the Dot, so a read-only Drive connection stays read-only for it. Read the read and edit scopes before you approve. Flavio Copes's starter rules leave deleting shared Drive files to the owner; a custom rule under Settings > Personalization > Custom rules can make the Dot ask before it deletes, moves or shares anything. Saying it in the first brief works too: samuraijuku_biz told the Dot to check before changing any data, and it asked "may I apply these three wording changes to the original documents?" before touching them (note). An action that works in chat may need a separate approval when it runs as a scheduled task (Google Drive app and setup).
  4. Smoke-test on one file. Ask the Dot which Google account it is using and what it may do there, then ask for a summary of one named Doc and one small edit, and open the file to check the change.
  5. Put the files you want it to work on in Drive, not in a ChatGPT project or Space. In October, Sudhar couldn't get a Dot to reach files stored in a Space, and Cooper's Dot could read files from his other ChatGPT projects but not update them, so it handed him the text to paste back in by hand. In a connected Drive folder it can do both.
  6. Give it one working document. Dennis (@eekfuh) has his Dot and his other agents coordinate through one shared Google Doc, and u/DarthSilent keeps a task doc in Drive that his Dot works through in order. Working state kept in Drive is something you can open and back up yourself.
  7. Check your plan and, at work, your admin. A Dot comes with Pro outside the EEA, UK and Switzerland, with Business Premium in any supported region, and with Enterprise once an admin switches it on (How to get ChatGPT Dots; in Europe, see Dots in the EU and UK). On Enterprise and Edu, the unified Drive actions stay off until a workspace admin enables them, and a Google Workspace admin may need to re-authorise the scopes (Admin controls for apps). In Enterprise workspaces where it is enabled, owners and admins can also allow or block whole shared drives and turn off My Drive under Safety & Security Controls; these limits cover whole drives, not single folders or files, and they don't erase what was already retrieved into conversations or memory (Managing Google Drive access). A personal connection is live access to the account, not the synced Drive index that eligible workspaces can set up. If the connection expires, open the reconnect request before you continue.

Where it gets stuck, and what worked

  1. A file is "done" in chat but broken in the app. Diana's Dot said a workbook had passed 27 formula checks; in Google Sheets some formulas weren't supported and were replaced by their last values. Ask for a native Google Sheet that uses only functions Sheets supports, and have the Dot open it in Sheets and list any warnings before it calls the job done. Diana kept the structure and asked for the formulas to be fixed rather than starting over.
  2. Numbers without labels. aoma23 found that the work that mattered was saying which numbers, for which target and which period, and keeping blog traffic apart from app usage. Ask for a notes tab that says what each number is, where it came from and the date range, and check the numbers yourself.
  3. Big files stall between Drive and the Dot's computer. COOLak's 514 MB upload timed out, and soon afterwards the cloud computer stopped responding, though COOLak doesn't claim one caused the other. sbosell's 52 MB archive was visible in Drive but never reached a Codex cloud task. In both cases search and file details kept working. Keep the original where it is until the copy is confirmed, and tell the Dot to stop after a set time instead of retrying.
  4. A Google security alert after a browser sign-in. Signing in to Google in the Dot's own browser is a separate route from the plugin, and Google blocked COOLak's first attempt as suspicious; a retry with Google's phone approval worked. Most Drive jobs only need the plugin, so tell the Dot to ask before it signs in and to give you the exact time it tried. BoomBigNose also had to sign in to Sheets by hand once.
  5. A tidy-up stops partway. HinaKira's Dot stopped a Drive cleanup and said plainly that it had moved 0 files, and the most useful thing it found was a folder anyone with the link could edit. Ask for a plan with file counts and a sharing check first, and let it move files only after you approve.
  6. Files sit in a ChatGPT Space or another project. Sudhar's Dot couldn't reach Space files, and Cooper's could read project files but not update them. Move those files into a Drive folder the Dot can open.
  7. Context only the Dot can see. Taichi keeps personal notes as linked Markdown files in a Drive folder instead of the Dot's memory, so he can read them, back them up with his Mac and take them to another assistant later. Two-way sync to his iPhone brought deleted files back, so he switched to one-way sync from Drive to the phone.
  8. The Dot finds a file but can't use what's in it. Seeing a file name or its details doesn't mean the contents were read, and reading the text and handing you a downloadable copy are separate steps. Check that the connected account can open the file in Drive, paste the file's link and ask the Dot to read that file, and ask for a download separately, naming the format (Google Drive app and setup).
  9. An upload is refused before it runs. RooneySimpson's Drive was set to allow all actions and the target folder was owner-only and unshared, yet two backup files of recovery data were refused because a broad backup instruction didn't authorise sending that data to that folder; a 101-byte test file to the same folder went through and read back (#56854). Auto-review checks planned actions against your instructions before they run, and neither the plugin setting nor a custom rule switches it off (Dots privacy, security and safety FAQs). Be specific: in your own message, name the files and the exact folder they should go to. If it is still refused, ask the Dot for the exact reason, don't let it retry in a loop, check the folder before any new attempt, and keep a copy somewhere else in the meantime.
  10. Files made in chat can't be delivered. When the Dot's chat attachments failed with "hosted apps tools/list request failed with HTTP status 403" from 20 October, Armywas and NuLL_00 had the Dot upload the files to their own Drive and downloaded them from there; for NuLL_00, normal attachments worked again on 22 October (OpenAI Community).

What it can do, and what it can't yet

It can:

  • find and read the right file without being told where it is (Vini Parizotto, Justin Coats)
  • do expenses from email and Drive, and turn receipts and letters dropped into one folder into claims and dated summaries (Max Weinbach, Takemi Terashi)
  • keep a status table or a Sheet current and point out what it doesn't reflect yet (@ai.team_official, BoomBigNose, shuntabi6)
  • notice a change to a Sheet before its next scheduled check, and ask before it writes changes back to the source documents (samuraijuku_biz)
  • notice a mismatch across files, such as one candidate entered twice (Ted)
  • work through a task list kept in a Google Doc (u/DarthSilent, Dennis)
  • make something from a folder, such as a music video from 20 photos and a song (Aj Keng)
  • point out a folder that anyone with the link can edit (HinaKira)
  • hand you finished files through your own Drive when chat attachments fail (Armywas, NuLL_00)

It can't yet, or not reliably:

  • move large files between Drive and its own computer (COOLak, sbosell)
  • promise that a workbook's formulas will work in Google Sheets (Diana)
  • reach files stored in a ChatGPT Space, or update files in your other ChatGPT projects (Sudhar, Cooper)
  • keep itself to one folder by its own choice; only the connected account's access does that (Takemi Terashi)
  • limit its background reading to files or folders you pick, or stop it while Drive stays connected; workspace admins can only allow or block whole shared drives (padiwe2753, 西岡賢一郎)
  • upload whatever you call a backup just because Drive is set to allow all actions (RooneySimpson)

One message to start with

Tell me which Google account you're using for Drive and whether you're allowed to edit there. Work only in [folder link], and tell me whenever you open a Drive file I didn't name. When a file there changes, update [Doc or Sheet] and add a dated line saying what you changed and which file you used. If you can find a file but can't read it, ask me for its link. Build spreadsheets as native Google Sheets with functions Sheets supports, then open them in Sheets and list any warnings before you tell me they're done. Before you upload, move, delete or share anything, send me a plan with file names, file counts and the target folder, and wait for my yes. If an upload is refused, tell me the exact reason and don't retry on your own. If a transfer hasn't finished after [10] minutes, stop and tell me what arrived. Don't sign in to Google in your own browser unless I ask.

Examples, by job

Find and read the right file

Vini Parizotto, @viniparizottomkt, Dot "Doletas" (Instagram, Portuguese, 30 September 2026). In his screen-recorded test, Vini asked the Dot to review projects related to "Black" in his workspace. Without more guidance it searched his files, found an old Drive document from 16 September with his "Planejamento de 16 de setembro", and reported back with it.

Max Weinbach, @mweinbach (X, 30 September 2026). Max's basic test for any personal agent is whether it can do his expenses on its own with access to his email and Google Drive. He says his Dot got it right after the first correction and has kept doing it well since. Another agent he tried did the first three days and then lost track.

Justin Coats, Dot "Donna" (YouTube, I Have Some Questions podcast). In a live screen-share demo with host Erik Berglund, Justin's Dot reads his Drive, updates a run of show with source links, and hands the work back finished. The episode also covers where trust still breaks and why he keeps a human in the loop.

Copyable ask:

Use my Google Drive account [email]. Find the most recent documents about [project or client], open the three that matter most, and tell me in five lines what was decided, what is still open, and who owns each item. Link every file you used. Read only; don't edit, move, or share anything.

Keep a Doc or Sheet current

Robleh, @robjama, Dot "dottie" (X, 1 October 2026). Robleh spent an hour stuck in Toronto traffic and finished his main task of the day by talking it through with his Dot while it worked in a Google Doc. He says voice is far better now that it works with connected apps.

BoomBigNose (YouTube, Thai, 2 October 2026). In his live demo, the Dot turned a meeting-notes file into a Google Sheet that separates what was confirmed from what was only proposed, with action items and their sources. He still had to sign in to Sheets by hand once.

@ai.team_official (Instagram, Korean, 5 October 2026). This AI consulting team's account describes its daily split: when a new deliverable lands in Google Drive, the Dot points out what the work-status table doesn't reflect yet, and when an email moves a deadline, it asks before changing the date in Notion. They approve from their phones and keep deep single-document work in regular ChatGPT chats.

旬之旅人 @shuntabi6 (Threads, Traditional Chinese). shuntabi6 wrote that large-data research that used to take about 75 minutes of reading and layout now leaves him about 15 minutes of review: the Dot spends about 10 minutes producing the Excel table, then he confirms it. In the same post, his morning news patrol went from about 20 minutes of manual work to no wait at all; that part is covered on the morning brief page.

Copyable ask:

Every weekday at [time] [time zone] until [end date], check the folder [Drive link] for new or changed files. Update the "Status" tab in [Sheet name] so each deliverable has its current state and a link, and add a dated line under "Changes" for anything you edited. If a file and the sheet disagree on a date, don't pick one: message me with both. Confirm the schedule before you start.

Catch mistakes across files

Ted, @tedzted (Threads, Traditional Chinese, 30 September 2026). Ted gave his Dot Asana, Google Drive, and Gmail. While they talked about something else, it noticed an interview in Asana for the next day, went through his Google files, and found two rows in the recruitment spreadsheet that looked like the same candidate at 3 PM on different dates. It asked him to check. HR confirmed it was the same person and one form had not been updated.

Use Drive as a shared task list

Dennis, @eekfuh (X, 29 September 2026). After weeks of using Dots at home and at work, Dennis shared three tips. One of them is to give your Dot and your other agents access to one shared Google Doc and tell them to coordinate through it.

u/DarthSilent (Reddit, r/OpenAI). He runs one Dot on its cloud computer all day on large engineering jobs, from CAD models to load calculations. For the queue, he puts a doc with tasks in his Google Drive and asks the Dot to work through them one by one. He still reviews the engineering output himself.

Brandon Carter (YouTube). In his test of three personal agents, one prompt had the Dot collect every video-editing and content skill he uses in Codex into a folder, write a document explaining what each one is for and how to use it, and upload the whole set to his Google Drive.

Copyable ask:

Treat the Google Doc [link] as your task list. Each morning, take the first unchecked task, do it, and write under it what you did, the file links, and anything you need from me. Check it off only when it is finished. If a task is unclear, leave a question under it and move to the next one.

Make something from a Drive folder

Aj Keng, Dot "Hero" (YouTube, Thai). On one phone call from Koh Tao, Aj Keng asked his Dot to build a music video from the 20 photos and the song in his Drive folder. It delivered a 47-second vertical video with icons and hand-lettered text. He gave feedback on the first version without repeating the brief, and the second version had bigger text, zooms, and cuts on the beat. He says results still need checking before he relies on them.

Rui Fu, @raycfu (Instagram; sponsored post tagged #chatgpt_partner). Rui connected his Google Drive so the Dot could learn his teaching style and how he converts members, then gave it one ongoing goal: improve the onboarding for his Skool community. In week one it saw visitors weren't reaching the outcomes section and drafted a landing page with member projects at the top. After he approved it, he reports conversions rose 15%.

Hub for research, Slack and a daily newsletter

Cimarronosky @chief4ndr35 (X, 13 October 2026). In a reply about how he stays updated, he says he crosses sources with his Dot in a Google Drive: the Dot and collaborators send messages there to improve presentations and to share information mined from X posts that are useful to him. The Dot then prepares a Slack message and a daily newsletter so he can keep up without chasing every feed himself.

Copyable ask:

Use Google Drive folder [link] as the hub. When new notes or files land there about [topic], update the working Doc, draft one Slack DM to me with the three most useful points, and append a short section to my daily newsletter draft [Doc link]. Don't post to Slack channels or send email unless I say so.

One shared folder as the Dot's whole view

Takemi Terashi, CEO of Talent Cloud (blog, Japanese, 12 October 2026). In Terashi's write-up the Dot runs on a Google account created only for it. The work Gmail, Calendar and Slack are not connected, and the only thing that account can open is one Drive folder shared with it. Receipts go in and a finished expense claim comes back to the same folder; photos of letters from the tax office, the pension office and the city go in and come back as sorted summaries with deadlines, plus drafts for anything that has to be returned. Client project folders, worked on in Claude Code and Codex, are never shared. Terashi points out two things about this setup. The Dot can't see outside the folder only because that account can't, not because of a Dot setting, so adding other files to the account or sharing another folder widens what the Dot sees. And app connections are shared between the Dot, ChatGPT, ChatGPT Work and Codex, so once the Dot's account is connected, the other features in the same ChatGPT account can use it too, within the permissions granted. The expense and letter jobs are on invoices, expenses & budgets and errands & life admin.

Copyable ask:

Work only from the Google Drive folder [link]. When a new receipt or scanned letter lands there, read it, write a one-line summary with the amount or deadline and the file name, and save your draft (claim form or reply) back into the same folder. Don't open other folders, and don't send or submit anything; I'll check each item against the original and approve it.

Where Drive work went wrong, and what people did about it

The examples above show Drive jobs that worked. The reports below cover where Drive work went wrong, grouped by where the trouble started.

Files that looked finished but weren't

  • "Passed 27 formula checks" in chat, broken formulas in Sheets. Diana of AI Agents Library tested a Dot named Sparky on 30 September and 1 October with Google Drive, Docs and Sheets connected. Diana asked for a review-production workbook, and it came back with four tabs, filters, data validation, three charts and a dashboard, and said it had passed 27 formula checks. When Diana opened it in Google Sheets, some formulas were flagged as unsupported and replaced by their last calculated values, and some conditional highlighting rules weren't supported either. Diana scored the task 7.5 out of 10 and would keep the structure and ask the Dot to fix the formulas rather than rebuild it (review).
  • A table of numbers is only as good as its labels. aoma23 (Japanese blog, updated 7 October) had a Dot put blog traffic and sign-up numbers into a spreadsheet so changes could be tracked later. The work that mattered was saying which numbers, for which target and which period, and checking that blog traffic and app usage weren't mixed together. aoma23 checked the numbers personally and notes that a finished table isn't the same as the numbers improving (post).

Large files between Drive and a computer

  • A 514 MB upload that took the cloud computer down with it. On 9 October, COOLak's Dot tried to move a file of about 514 MB to Google Drive through the connector. The transfer timed out after 300,001 ms, before Drive returned a successful upload. Within minutes even simple shell reads stalled, and over the next two hours the Dot's cloud computer went from "starting" to "failed" despite every recovery step it could try. Chat, web research and Drive metadata reads kept working, and Drive showed the target folder still empty. COOLak notes that the timeout came first but cause and effect aren't established, and that the files had been saved elsewhere, so nothing new was lost (#52509).
  • Drive could see the file, the cloud task never got the bytes. On 2 October, sbosell's Dot, "chief", filed a report on Sam's behalf. A Codex cloud task needed an archive of 52,006,903 bytes from the connected Drive. The metadata read worked and the connector returned transfer references. In a restricted cloud environment the download got a 403 because the transfer hosts weren't on its allowlist, which the report calls expected. After an approved unrestricted environment was started, the fetch timed out and no bytes arrived (#50277).

Signing in to Google from the Dot's browser

  • The connector and a browser sign-in are two different routes. On 8 October, COOLak asked a Dot to do a task that needed a Google sign-in in its cloud browser. The password went through the secure entry form next to the conversation, which COOLak liked. Google then showed a "Suspicious sign-in attempt prevented" alert, and COOLak had to ask the Dot whether that attempt was its own and compare times by hand without getting a clear answer. A later retry with the same form plus Google's phone approval worked, and the signed-in Drive page was confirmed in the live browser (#52326). BoomBigNose's demo above also needed one manual Sheets sign-in.

Keeping your own context in Drive

  • A "Personal" folder of Markdown files instead of the Dot's memory. Taichi, host of the Japanese podcast 超実践AI論, keeps personal information in a Google Drive folder called Personal, as Markdown (.md) files that link to each other. Taichi handed old iPhone notes to the Dot and had it sort them into that folder. The reason: information kept in the Dot's memory or on its computer is awkward to look at directly and hard to take with you if a better assistant comes along, while a Drive folder stays under the owner's control. The Google Drive desktop app mirrors the folder to a Mac, so a full Mac backup also covers the Dot's edits. Taichi tried two-way sync to an iPhone, but deleted files reappeared, so the setup switched to one-way sync from Drive to the phone and edits now go through the Dot by voice whenever something needs editing (episode).

A cleanup that stopped at zero moves

  • An honest "0 files moved", and a folder anyone with the link could edit. Japanese creator HinaKira (YouTube, 7 October, sessions on 5 and 6 October) asked his Dot to tidy his Drive. The job stopped partway, and the Dot reported plainly that it had moved 0 files instead of claiming progress. Along the way it found a folder that anyone with the link could edit and told him about it. In the same test, a separate job gathered the prompts and post ideas scattered across 12 of his files into two lists, 300 prompts and 150 ideas, and left the original files where they were; he plans to check the contents as he uses them.

Files it read without being asked

  • A private thesis it opened on its own. padiwe2753 (OpenAI Community, 17 October) connected Google Drive, and without a fresh request the Dot opened a newer version of a private thesis document, reread it and flagged a sentence that had been pasted in by mistake. The catch was useful, but padiwe2753 hadn't expected the Dot to open that file and asked for three things: choosing which files or folders it may read in the background, a history of the files it read proactively, and a switch to turn that reading off (thread).
  • To-dos from minutes it was never handed. 西岡賢一郎 (note, Japanese, 21 October) connected mail, calendar and Google Drive. The Dot pulled his next to-dos out of meeting minutes that were simply stored in Drive, which saved him work. He then looked for a way to limit which folders or files it reads and to stop the background research on its own while keeping Drive connected, and found neither; what the Dot has read stays in its context and can't be viewed or deleted item by item. He also notes that the research tools themselves can't send messages or change files (post).

Uploads refused, and Drive as the way out

  • A backup refused twice, a test file accepted. On 25 October, RooneySimpson asked a Dot on the Windows web app to back up its recovery data to Google Drive. The plugin was set to "Allow all actions", and the target folder was owned by him alone and not shared. An 89,585-byte JSON file was refused because the data counted as sensitive and "the broad backup instruction does not authorize disclosure to this specific destination"; a 419,350-byte package was refused about 15 seconds later as a retry of the same thing. Twelve minutes later a 101-byte text file went into the same folder and read back correctly. Copies of the data were already on GitHub, so nothing was lost. He asks for the refusal to say what evidence is missing and how to supply it (#56854).
  • Drive as a delivery route when chat attachments broke. From 20 October, Armywas (Windows web) couldn't get Word or Excel files from the Dot: delivery failed with "hosted apps tools/list request failed with HTTP status 403". Uploading the files to Armywas's own Google Drive with permission and downloading them from there worked, and the files checked out. NuLL_00 used the same private Drive route on 21 October, and by 22 October normal attachments were working again for NuLL_00 (thread).

Prompts to copy for these problems

Swap in your own names, folders and limits.

Native Sheet, checked in Sheets (avoids formulas that only work in chat)

Build this as a native Google Sheet in [folder link], not an Excel file. Use only functions Google Sheets supports. Before you tell me it's done, open it in Sheets and list any formula or formatting warnings. Add a "Notes" tab saying what each number is, where it came from, and the date range.

Big file, original kept (avoids a stalled transfer taking work with it)

Before you move [file] between Drive and your computer, tell me its size and keep the original where it is. If the transfer hasn't finished after [10] minutes, stop. Don't retry in a loop. Tell me what arrived and what didn't, then check that your computer still runs a simple command before doing anything else.

Plugin first, sign-in only on request (avoids an unexplained Google security alert)

Use the Google Drive plugin for my files. Don't sign in to Google in your own browser unless I ask. If you think you need to, tell me first, and afterwards give me the exact time you tried so I can match it to any Google alert. Report the result as signed in, blocked, or waiting on me.

A folder I own (avoids context only the Dot can see)

Keep what you learn about me in Markdown files in my Drive folder [Personal], one file per topic, all linked from index.md. When you change a file, add a dated line at the bottom saying what changed. Never delete anything there; move old files to an Archive folder.

Plan first, sharing check included (avoids a half-finished tidy-up)

Before you move anything in [Drive folder], send me a plan: which files go where, and how many. Also list every file or folder that anyone with the link can open or edit. Move nothing until I approve the plan. Afterwards, tell me how many files you actually moved, and which ones failed and why.

Named files, named folder (avoids an upload refused for a vague instruction)

Upload only [file names] to the Google Drive folder [folder link]. I own this folder and it isn't shared. If the upload is refused, tell me the exact reason and what would need to change, and don't retry on your own. Before any new attempt, check what is already in the folder. Afterwards, list the files that arrived with their sizes.

More on what the Dot's own computer keeps and loses is on cloud computer, errors and stalls are covered on Dots not working, and approvals and sign-ins are explained on what is Dots and getting started. For Codex cloud environments, see Codex orchestration.

Related

Copy this task brief

How do you use Google Drive with a ChatGPT Dot? Start with the verdict, the setup, where it gets stuck and how to fix it, and one message to copy; then Docs, Sheets and Drive examples and the reports of where Drive work went wrong.
Download Markdown ↓

Sources & further reading