Colab Cola packages Python scripts, modules, dependencies, and inputs into reproducible jobs. Submit them to Google Colab, monitor execution, and recover verified results from Google Drive — without building a notebook launcher yourself.
python -m pip install colabcola
Requires Python 3.12+. See Development for source installation and testing.
Quick start
1. Connect your Google account
colabcola login --profile research
Colab Cola guides you through execution-project setup and authorization. New profiles use the bundled production Desktop OAuth client by default; providing your own is optional. First-time Google consent and some Console steps require your participation. Setup guide
2. Package an existing Python workload
colabcola package --profile research \
--save-colaml experiment.colaml -- python train.py
The packaging guide collects data, dependencies, hardware needs, outputs, and optional checkpoint configuration. It creates a .colajob plus a reusable .colaml recipe, without executing your code.
3. Run it on Colab
colabcola run --profile research \
--colaml experiment.colaml \
--run-dir ./runs/experiment-1
Colab Cola checks the job and account, stages inputs, supervises the Colab runtime, publishes results to Drive, verifies recovered files, and releases the runtime it owns. Keep the supervising computer online while the run is active.
To prepare offline, add --prepare-only. To verify launch prerequisites without uploading or allocating compute, use --preflight-only. Repeating the same command with the same run directory reconnects to the existing run rather than starting a new one.
What Colab Cola provides
| Capability | Description |
|---|---|
| Python-first jobs | Package scripts, modules, local files, pip requirements, and wheels. |
| Managed runtime lifecycle | Allocate, execute, monitor, and release Colab runtimes within declared bounds. |
| Durable results | Persist logs, checkpoints, and artifacts to Google Drive with integrity verification. |
| Failure recovery | Resume checkpoint-aware workloads on a replacement runtime after confirmed runtime loss. |
| Repeatable workflows | Reuse .colaml recipes, named account profiles, and durable run journals. |
| Automation-friendly output | Structured command results alongside human-readable terminal progress. |
Python workload + inputs
│
▼
colabcola package ──► .colajob / .colaml
│
▼
colabcola run
│
▼
Google Colab
│
▼
Google Drive + verified results
Platform support
| Host platform | Status for v0.1.0 |
|---|---|
| Windows / PowerShell | Live-tested: installation, login, CPU execution, artifacts, automatic checkpoint recovery, and owned-runtime cleanup. |
| Ubuntu via WSL2 | Previously tested for managed execution and recovery; WSL2 is optional for Windows users. |
| Native Linux | Expected to work; independent release validation pending. |
| macOS | Not yet supported for managed login and execution. |
Requirements: Python 3.12 or newer, a Google account with access to Colab and Drive, and any one-time OAuth/Cloud project setup described in the setup guide. Accelerator availability depends on Google Colab. The Windows recovery acceptance test used CPU runtimes; it does not establish that every GPU or runtime configuration works.
Checkpoint recovery is opt-in: your workload must write restorable state and accept a checkpoint manifest. A runtime lost before publishing its latest checkpoint cannot recover its unsaved in-memory progress. Compute limits are bounded requests, not guaranteed billing ceilings.
Documentation
| Guide | Contents |
|---|---|
| First-time setup | Illustrated Google account, OAuth, Cloud project, and login walkthrough. |
| Packaging | .colajob format, dependencies, inputs, outputs, and checkpoints. |
| Recipes and managed workflows | .colaml, run directories, offline preparation, and automation. |
| Execution and recovery | Supervisor behavior, Drive persistence, failure recovery, and limits. |
| Legacy controller | Earlier notebook-based/manual execution workflows. |
| Development | Local builds, tests, and contribution workflow. |
| Design | Technical architecture and integrity contracts. |
Development
Colab Cola is distributed as a Python package. Release checks cover clean wheel/source installs, complete regression tests, platform behavior, license notices, and the verified runtime lifecycle. See Development and Packaging for current details.
Colab Cola is an independent project and is not affiliated with or endorsed by Google. Google Colab and Google Drive remain subject to their own availability, policies, and limits.
Metadata
Release files for colabcola 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| colabcola-0.1.0.tar.gz | 879.1 kB | With provenance | Details for colabcola-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| colabcola-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for colabcola-0.1.0-py3-none-any.whl |
Total release size: 1.1 MB
Release files / colabcola-0.1.0.tar.gz
| Download URL | colabcola-0.1.0.tar.gz |
|---|---|
| Size | 879.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
859c004332ec0430b3dc0931b111515116613a9a0bab970f509010bd5ba8322f
|
|
BLAKE2b-256 checksum How to use checksums |
5f8805ae63ca7ab0660d9f3d7763f666602a462f6158df77e63ef6af1729f1b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / colabcola-0.1.0-py3-none-any.whl
| Download URL | colabcola-0.1.0-py3-none-any.whl |
|---|---|
| Size | 268.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed4c28ae748a9181dfb1131f94f1aa0d3fc4538ca19d16eac4b68b3652a9ffcd
|
|
BLAKE2b-256 checksum How to use checksums |
b7ee6a5688fbdd310cf4de1bc9c74fbd6d605154d0057cb94ed9998ac2d09a5d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logSecurity for colabcola 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for colabcola-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.