Skip to main content

aircore / airpy / airlang / aircli

A provider-agnostic AI execution runtime, split into four independently installable packages with a strict, one-directional dependency chain:

aircore   <-  airpy   <-  airlang
   ^           ^             ^
   └───────────┴─────────────┘
              aircli
  • aircore -- the execution runtime: scheduler, capabilities, policy, journal, consensus, memory, approval, checkpoint/resume, sandboxed execution, cross-step data flow. No model, prompt, or provider concept exists anywhere in this package, by design. Zero dependencies.
  • airpy -- the provider-aware Python SDK on top of aircore: ModelAgent, real provider adapters (LiteLLMProvider, native OpenAIProvider), consensus strategies, structured output, an MCP tool registry, streaming, long-running sessions, PromptTemplate. Imports aircore; aircore never imports airpy.
  • airlang -- AirLang, a declarative workflow language: lexer, parser, IR, and an executor that compiles a parsed .airlang file to real airpy/aircore calls. Imports airpy; airpy never imports airlang. See airlang-spec-v1.md.
  • aircli -- the ai command: ai run/ai trace for both .py scripts and .airlang files, with --json/--html trace output. Depends on all three of the above.

Install

pip install aircore          # just the runtime
pip install airpy             # runtime + SDK
pip install airlang           # runtime + SDK + language frontend
pip install aircli             # everything, plus the `ai` command

Optional extras on airpy: litellm, pydantic, mcp, openai -- each is a lazy import inside the one module that needs it, so none of them are required just to install airpy itself.

For local development on this repo (all four packages, editable, pip install -e . style), see the root pyproject.toml instead of the per-package ones under packaging/ -- those are used only by the release workflow (.github/workflows/publish.yml) to build the four separate PyPI distributions.

Docs

  • architecture-spec-v1.md -- the runtime's original design spec.
  • airlang-spec-v1.md -- AirLang's design spec.
  • cross-step-data-flow.md -- the bindings/let design writeup.
  • real-project-readiness-roadmap.md -- known gaps and what's planned.

Metadata

Release files for aircore 0.1.0

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

Source distribution (sdist)

Source distribution for aircore 0.1.0
File Size Uploaded Provenance Actions
aircore-0.1.0.tar.gz 46.9 kB With provenance Details for aircore-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for aircore 0.1.0
File Interpreter ABI Platform Actions
aircore-0.1.0-py3-none-any.whl Python 3 none any Details for aircore-0.1.0-py3-none-any.whl

Total release size: 102.9 kB

Release files / aircore-0.1.0.tar.gz

Download URL aircore-0.1.0.tar.gz
Size 46.9 kB
Tags Source
SHA-256 checksum
How to use checksums
c6e66909089ec1b95cb68d4fed740a10ca0742144348714f2573802876c06e67
BLAKE2b-256 checksum
How to use checksums
4962f43e7778c830351d70254c5ac2bbcc844142b20869e80f3d7ecb9a887971
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 4, 2026.

Transparency log

Release files / aircore-0.1.0-py3-none-any.whl

Download URL aircore-0.1.0-py3-none-any.whl
Size 56.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c7b6ee74b1a729250a448291231692139f60c5a68fa8f6def6baa39b42fdba4b
BLAKE2b-256 checksum
How to use checksums
897bd5521fad2efc521673584b6efe820c9ca39e104d7169a86163fc25b60e6b
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 4, 2026.

Transparency log

Security for aircore 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.

Select from 2 files

Attestation for aircore-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 Aug 4, 2026.

Transparency log

A 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.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

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