This release is a pre-release and may not be stable for production use.
lightcone-cli
lightcone-cli (lc) is the execution layer for
ASTRA (Agentic Schema for Transparent
Research Analysis). Describe your analysis in an astra.yaml
specification and lc takes care of the rest — execution, environments,
and provenance.
Quick Start
lightcone-cli only requires you to have uv installed on your environment, and will take care of everything else. See how to install uv here: https://docs.astral.sh/uv/getting-started/installation.
Then to install lightcone-cli:
uv tool install lightcone-cli
Once the CLI is installed, you can use it to create an ASTRA project and generate outputs like so:
lc init my-analysis
cd my-analysis
# describe your analysis in astra.yaml, write your scripts,
# declare what they import through normal uv interactions:
uv add numpy
# When you are done with your edits, commit:
git add -A && git commit -m "First analysis"
# Use the lightcone CLI to generate your outputs with full provenance tracking
lc materialize
ASTRA specs are plain, structured YAML — they work well hand-written or drafted with any AI coding assistant.
Capabilities
- Multiverse analysis — declare methodological decisions with multiple defensible options;
lcmaterializes your analysis across every universe you define - Provenance by construction — every output is committed to git together with a content-addressed manifest and a re-runnable run record; git-annex carries the bytes, so results travel with the repository
- Locked, isolated execution — a project's environment is
pyproject.toml+uv.lock; recipes run in it under a sandbox (Landlock on Linux, Seatbelt on macOS) that keeps undeclared files out and stray writes contained - Containers and HPC — declare
[tool.lightcone.image]and recipes run in a content-addressed image archived in the repository itself; a SLURM allocation is detected and used automatically, every node included - Publication view — declare a license and
lc materializemaintains an RO-Crate of the project and its provenance, ready to archive or deposit
License
BSD 3-Clause — see LICENSE for details.
Release files for lightcone-cli 0.5.0rc1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| lightcone_cli-0.5.0rc1.tar.gz | 123.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lightcone_cli-0.5.0rc1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 268.4 kB
Release files / lightcone_cli-0.5.0rc1.tar.gz
| Download URL | lightcone_cli-0.5.0rc1.tar.gz |
|---|---|
| Size | 123.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
481ddac128bdd371a5d1850cae5302e04afca73540ef65ce552fa1e12839cdee
|
|
BLAKE2b-256 checksum How to use checksums |
0d5c251b309681ce202a6e9f94202294a0d6ce89c42970fbc21750165412eb4d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 21, 2026.
Transparency logRelease files / lightcone_cli-0.5.0rc1-py3-none-any.whl
| Download URL | lightcone_cli-0.5.0rc1-py3-none-any.whl |
|---|---|
| Size | 145.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c7a4b2c6fe8ffc3f96bc92eff13c3564b828a09a1088ad14cdabefbe20a7968f
|
|
BLAKE2b-256 checksum How to use checksums |
d22155ba637cdce613588787e540e345f536a4a0cbda597ee1d427678595b496
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 21, 2026.
Transparency log