Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

lightcone-cli

License Python PyPI Tests

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

Create an ASTRA project and launch the built-in local compute offer; no compute configuration is needed. Configure resource offers for larger local allocations or Slurm:

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"
CLUSTER=$(lc compute launch --wait)
# Generate outputs with full provenance tracking
lc materialize "$CLUSTER"
lc compute down "$CLUSTER"

ASTRA specs are plain, structured YAML — they work well hand-written or drafted with any AI coding assistant.

→ Full getting-started guide

Capabilities

  • Multiverse analysis — declare methodological decisions with multiple defensible options; lc materializes 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; allocate local or Slurm Dask clusters explicitly with lc compute, then pass the cluster name or full ID to run or materialize
  • Publication view — declare a license and lc materialize maintains an RO-Crate of the project and its provenance, ready to archive or deposit

→ Full documentation

License

BSD 3-Clause — see LICENSE for details.

Metadata

Release files for lightcone-cli 0.5.0rc5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for lightcone-cli 0.5.0rc5
File Size Uploaded
lightcone_cli-0.5.0rc5.tar.gz 160.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for lightcone-cli 0.5.0rc5
File Interpreter ABI Platform
lightcone_cli-0.5.0rc5-py3-none-any.whl Python 3 none any Details

Total release size: 349.0 kB

Release files / lightcone_cli-0.5.0rc5.tar.gz

Download URL lightcone_cli-0.5.0rc5.tar.gz
Size 160.1 kB
Tags Source
SHA-256 checksum
How to use checksums
2627a1fd70e980d42c63d6576b454465088be3325be95eef55e368c2db128dbb
BLAKE2b-256 checksum
How to use checksums
6e56ddad847586052e5d2cfe57434dd3a16bae080721f4e57d3ca257fb06cbd4
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 Sep 29, 2026.

Transparency log

Release files / lightcone_cli-0.5.0rc5-py3-none-any.whl

Download URL lightcone_cli-0.5.0rc5-py3-none-any.whl
Size 189.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7c2fd74172167de1fb0ddd18ba01a0c6d03eba23c57c6c9cfcdd844bae8af43c
BLAKE2b-256 checksum
How to use checksums
d8149dd139187e99c4590085c9d777631a937a4ff3328d977ea3ae0231c0e04e
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 Sep 29, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page