AutoYou
Freemium
Users wanting fully private local AI
Getting a PyTorch model running on an iPhone used to mean guessing at export flags, fighting Core ML type mismatches, and hoping the runtime behaved the same way the Python prototype did — Apple's coreai-models exists to close that gap.
The repository ships three concrete layers: Python export recipes for popular Hugging Face models, reusable PyTorch primitives for authoring custom models in Core AI format, and a Swift package that slots those exported models into macOS and iOS apps. The CLI tooling lets you run models directly on a Mac before touching Xcode. Where the workflow breaks is at the edges of what the export recipes cover — models outside the supported Hugging Face roster require you to author your own export logic using the Python primitives, which assumes familiarity with both PyTorch internals and Core AI's model format. The skills directory adds coding-agent plugins, but the core offering is an export-and-runtime pipeline, not an autonomous agent loop.
Bottom line: Reach for this when your target is Apple silicon and your model is on the supported export list; plan for manual primitive authoring the moment you step outside that list.
Find your fit
More options in Local Inference Runtimes. Compare pricing, platforms, and features side by side.
Freemium
Users wanting fully private local AI
Freemium
Companies needing data-residency compliance
coreai-models is Apple’s open-source toolkit — BSD-3-Clause licensed, hosted publicly on GitHub — for converting models into the Core AI format required for on-device execution on Apple silicon. The pipeline moves in three steps: export a model from Hugging Face or another source using the included Python recipes, optionally author custom model logic using the reusable PyTorch primitives, then consume the exported artifact through the Swift package in a macOS or iOS application. A CLI layer lets developers test model inference locally on a Mac before any Xcode work begins.
The differentiating feature is the combination of export recipes and a first-party Swift runtime package in a single repository. Most third-party export tools stop at the file conversion step and leave the app-side integration to you. Here the Swift package is built directly on top of the Core AI framework, which means the handoff from Python export to Swift consumption follows a defined path the vendor maintains — rather than one you improvise per project.
The tool fits tightly scoped scenarios: a developer targeting Apple silicon who needs a supported Hugging Face model running in a native Swift app. It breaks when the model architecture falls outside the recipe library. At that point, teams write their own export logic using the Python primitives, which is documented but assumes non-trivial familiarity with PyTorch model internals. There is no API, no hosted service, and no GUI — the entire workflow runs locally from a cloned repository using uv-based Python tooling and Swift Package Manager.
The repository uses uv for Python dependency management and Swift Package Manager for the runtime side, with pre-commit hooks and a .swift-format config signaling active maintenance standards. The skills directory contains plugins designed to help coding agents work with Core AI effectively, though the vendor describes these as secondary to the export-and-runtime core.
Sign in to rate this tool or suggest an edit.