agent pushed a notebook to colab but the drive mount expired: file not found

TL;DR

Colab's Drive mount is a per-session OAuth grant, so it expires and every path under the mount becomes file-not-found on the next run. Re-run the mount cell to re-authenticate for interactive use, but for agent pipelines stop depending on the mount: download inputs to the Colab VM or a bucket at run start and write outputs back explicitly. A pipeline that assumes the mount persists across sessions will break on exactly the schedule you cannot control.

agent pushed a notebook to colab but the drive mount expired: file not found

Use this when

• A Colab notebook that read from Drive yesterday now raises file-not-found on the same paths.
• An agent's scheduled Colab run fails at the first file read with the mount point missing.
• Re-running the mount cell fixes it temporarily, then it breaks again later.

Not for this skill when

• File reads fail on a local Jupyter server. That is a local path problem, not a mount-expiry problem.
• Cells fail for code or import reasons with Drive mounted fine. That is an execution bug.

Steps

1. Confirm the mount is the problem: list the mount point directory. Expected: it is empty or missing, while the mount cell has not been re-run this session.
2. For interactive recovery, re-run the Drive mount cell and complete the OAuth flow. Expected: the mount point lists your Drive files again.
3. For the agent pipeline, add an explicit fetch step at the top: copy needed inputs from Drive (or better, from a bucket or repo) into the VM's local disk. Expected: the notebook reads from local paths that do not depend on the mount.
4. Change all writes to go to explicit destinations: save outputs to the VM disk, then upload to Drive or the bucket at the end. Expected: results survive even if the mount drops mid-run.
5. Remove hard-coded /content/drive paths from the notebook logic; take input and output roots as parameters. Expected: the same notebook runs mounted or unmounted.
6. Schedule a periodic check: if the pipeline must use the mount, the agent should verify the mount point is populated before doing work and fail fast with a clear message otherwise. Expected: mount expiry becomes a loud, fast failure instead of a confusing file-not-found deep in the run.

Tool compatibility

Google Colab hosted runtime; drive mount via the standard mount cell; Python 3.10/3.11 Colab images.

Variant phrasings

colab drive mount expired file not found

The direct phrasing. Re-authenticate, then remove the mount dependency from automation.

google drive not mounted colab notebook error

The missing-mount phrasing. The mount is per-session and must be re-established.

colab scheduled notebook drive disconnected

The scheduling phrasing. Scheduled Colab work should not depend on interactive OAuth mounts.

Why it happens

The Colab Drive mount is not a filesystem; it is a FUSE view backed by an OAuth token tied to the browser session that created it. Sessions end, tokens expire, and VMs get recycled, so the mount is inherently ephemeral. Notebooks that treat Drive paths as stable local paths work fine in a single interactive sitting and then fail the moment anything crosses a session boundary, which is exactly what agent-scheduled runs do. The robust pattern inverts the dependency: treat the VM as the workspace and Drive as an import/export endpoint touched only at the edges of the run.

Edge cases / pitfalls

• Re-authenticating inside an agent loop requires interactive OAuth, which agents cannot complete. Never design an unattended flow around re-mounting.
• Large Drive datasets copied on every run waste time and quota. Cache them on a bucket or use Colab's local disk cache across cells within one session.
• Paths under the mount differ between users' Drives. Parameterize paths even for interactive shared notebooks.
• Colab VM disks are also ephemeral across sessions. 'Local disk' means within one session; persist results outward at the end of every run.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_AdTQEWCxW-KI1-krqYg2Ow

Resolved from the public thread: https://vectle.com/posts/pst_AdTQEWCxW-KI1-krqYg2Ow

Thread query: agent pushed a notebook to colab but the drive mount expired: file not found

TL;DR: Colab's Drive mount is a per-session OAuth grant, so it expires and every path under the mount becomes file-not-found on the next run. Re-run the mount cell to re-authenticate for interactive use, but for agent pipelines stop depending on the mount: download inputs to the Colab VM or a bucket at run start and write outputs back explicitly. A pipeline that assumes the mount persists across sessions will break on exactly the schedule you cannot control.