take-me-cloud
take-me-cloud is a CLI for working with Lightning AI studios from your shell. It can list every studio you can access, sync Lightning SSH entries into ~/.ssh/config, create or replace studios from a local config file, and bootstrap a fresh studio for repository work.
Introduction
The CLI authenticates with Lightning AI through LIGHTNING_API_KEY and either LIGHTNING_USER_ID or LIGHTNING_USERNAME. It uses those credentials to discover your organizations, teamspaces, and studios.
Installation
pip install take_me_cloud
uv tool install take_me_cloud
For development:
pip install -e .
Configuration
Create ~/.config/take_me_cloud_config.yaml with a Lightning AI section:
Lightning AI:
machine_default: T4
cloud_provider: AWS
teamspace:
- name: rwth-gut/skillcomp
owner_type: org
- name: vaishnavahari/myml
owner_type: user
machine_default: CPU
teamspace entries are shown interactively when you create a studio. Each entry must use owner/teamspace naming.
Usage
List studios
take-me-cloud --list
take-me-cloud -ls
The output is grouped by teamspace and shows the studio name, owner, machine type, and current state.
Sync SSH config
take-me-cloud --lock-ssh
This preserves non-Lightning SSH hosts, removes stale Lightning entries, and writes the current accessible studios into ~/.ssh/config.
Create or replace a studio
take-me-cloud --create-replace my-studio
The CLI prompts for a teamspace from the config file, deletes any existing studio with the same name, starts the replacement with the configured machine type, and appends common setup commands to ~/.bash_history.
Go studio
take-me-cloud --go-studio my-repo
This creates or replaces a studio, clones svaichu/my-repo into the studio home directory, writes .vscode/settings.json, and installs the requested VS Code extensions on the remote environment.
Version
take-me-cloud --version
take-me-cloud -v
Development
Run the tests with:
uv run python -m unittest discover -s tests -v
Project Layout
take_me_cloud/base.py: Lightning helpers and SSH/config logictake_me_cloud/cli.py: Argument parsing and command dispatchtests/: Unit tests for the core flows
Metadata
Release files for take-me-cloud 0.1.3
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 |
|---|---|---|---|---|
| take_me_cloud-0.1.3.tar.gz | 12.6 kB | With provenance | Details for take_me_cloud-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| take_me_cloud-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for take_me_cloud-0.1.3-py3-none-any.whl |
Total release size: 22.3 kB
Release files / take_me_cloud-0.1.3.tar.gz
| Download URL | take_me_cloud-0.1.3.tar.gz |
|---|---|
| Size | 12.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b782e18d665b0416dd4654e62be0e28567fc23818bcd08984a4c6161b16ac19a
|
|
BLAKE2b-256 checksum How to use checksums |
877bfcc9f5d727f06f1a62d0cf7a26cfdb5707a8bf62da4b47c0244837d8dada
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 17, 2026.
Transparency logRelease files / take_me_cloud-0.1.3-py3-none-any.whl
| Download URL | take_me_cloud-0.1.3-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7ed6911548f0230e78546a848a3a90e338b88681fecc1fcb34a40109a8f151a5
|
|
BLAKE2b-256 checksum How to use checksums |
3821db0004c1e3e0d18bdc6bd4929da67a2cc585963c36eaef6ffeb920e8ff71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 17, 2026.
Transparency logSecurity for take-me-cloud 0.1.3
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for take_me_cloud-0.1.3.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 May 17, 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.