Skip to content

Download AnyInfer

v0.1.1

Every merge to main with a version bump produces a GitHub Release carrying the packages below, built by the release workflow.

Python wheel

For applications. Published to PyPI; installing from the repository is byte-identical.

pip install anyinfer
# or, straight from the repository:
pip install "anyinfer @ git+https://github.com/anthturner/AnyInfer@main"

Latest release

Demo app bundle

Self-contained — unzip and run, no Python required. Fully offline, no credentials needed.

Windows (x64)
macOS (Apple silicon) · macOS (Intel)
Linux (x64) · Linux (arm64)

Or with Python already installed:

pip install "anyinfer[demo]" && anyinfer-demo

Sidecar bundle

The OpenAI-compatible service, self-contained for integrations that do not use Python.

Windows (x64)
macOS (Apple silicon) · macOS (Intel)
Linux (x64) · Linux (arm64)

Or with Python already installed:

pip install "anyinfer[serve]"
anyinfer serve --config anyinfer.json

Sidecar documentation

Installation

pip install anyinfer

The core depends on only httpx2 and jsonschema; everything else is an extra. See installation and extras for which extras you need.

Notes

  • Unzip the demo bundle, then run the anyinfer-demo executable inside. The bundled BUNDLE-INFO.txt records the exact version. Bundles never embed llama-server binaries or model weights — install a runtime explicitly and let the local subsystem acquire verified model artifacts when needed.
  • Unzip the sidecar bundle and run anyinfer-serve --config anyinfer.json from inside it. It includes the HTTP frontend and built-in dependency-free adapters. Integrations that require an optional provider SDK, such as GitHub Copilot or Entra authentication, should install the Python distribution with the corresponding extra.
  • On 32-bit Windows (x86) there is no standalone demo bundle — PySide6 publishes no 32-bit Qt builds — but the library wheel itself is pure Python and runs there fine.

Previous releases and checksums

The releases page keeps every prior version with its changelog, generated from the pull requests that landed between releases, plus the checksums for every attached asset. The versioning and branch policy is documented in the release strategy.