ACR: Adaptive Cognitive Runtime
A local-first AI orchestration runtime that runs entirely on your own machine. Persistent memory, a skill system, task/agent orchestration, and multi-provider model routing, all on SQLite, with no cloud account, API key, or telemetry required to try it. Point it at your own local Ollama models when you want real inference, or keep it on the zero-config mock provider indefinitely; ACR never assumes you're online or paying for anything.
pip install acr-runtime
acr db upgrade && acr doctor
acr run "say hello"
Full specification: ACR_MASTER_SYSTEM_PROMPT.md.
Current implementation state: docs/ARCHITECTURE.md,
the single source of truth for what's actually built, so nothing here
duplicates that status and drifts stale.
What's here
A Python CLI (acr) built around a real task engine, a hybrid-retrieval
memory store, a skill registry with routing/validation/evolution, model
and tool routing with safe-mode-aware permission checks, an agent
planner/critic/topology system, an operational dashboard with a
real-telemetry visualization, and an MCP server exposing ACR's memory,
skill, web, and GitHub search tools to any MCP client, including
project-scoped registration for both Claude Code and Codex CLI out of
the box. See docs/ARCHITECTURE.md for the full
breakdown of what's implemented, how, and why.
Quick start
Install from PyPI:
pip install acr-runtime # or: uv tool install acr-runtime
acr db upgrade # create the local SQLite schema, no repo checkout needed
acr doctor
Or from a source checkout (for development; see CONTRIBUTING.md):
uv sync # install deps + local package into .venv
cp .env.example .env # local dev data dir (repo-local ./data, gitignored)
uv run alembic upgrade head
uv run acr doctor
acr run "say hello" # create + execute a task end to end
acr dashboard serve # operational dashboard: http://127.0.0.1:8765
acr mcp serve # MCP server (stdio by default)
(prefix with uv run if working from a source checkout instead of a pip/uv tool install)
Using ACR from Claude Code or Codex CLI
This repo ships project-scoped MCP server registration for both
Claude Code and Codex CLI, so opening
it in either offers ACR's memory/skill/web/GitHub search tools and task
execution as MCP tools directly. Claude Code prompts for approval the
first time it opens the project; Codex CLI only loads project-scoped
config for a project you've marked trusted (codex trust prompt, or
trust_level = "trusted" under [projects."<path>"] in your own
~/.codex/config.toml); either way, cloning the repo can't silently
launch anything without you consenting.
Development
See CONTRIBUTING.md for the full workflow. Short version:
uv run pytest # tests
uv run ruff check . # lint
uv run ruff format . # format
uv run pyright # type check
License, security, support
MIT licensed. See SECURITY.md to report a
vulnerability privately. For bugs, questions, or feature requests, use
GitHub Issues.
If ACR is useful to you, consider supporting its development: ko-fi.com/hbkcustomsinc.
Metadata
Release files for acr-runtime 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| acr_runtime-0.2.0.tar.gz | 142.1 kB | With provenance | Details for acr_runtime-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| acr_runtime-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for acr_runtime-0.2.0-py3-none-any.whl |
Total release size: 341.8 kB
Release files / acr_runtime-0.2.0.tar.gz
| Download URL | acr_runtime-0.2.0.tar.gz |
|---|---|
| Size | 142.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d8a5ab00090718c66380b250c1ed3946bd2d44a0c6fd625fb6d529e766715f04
|
|
BLAKE2b-256 checksum How to use checksums |
b83d097c58a754215601a296dbd87edbf875230be1a48312c3f94626de9c3f72
|
| 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 1, 2026.
Transparency logRelease files / acr_runtime-0.2.0-py3-none-any.whl
| Download URL | acr_runtime-0.2.0-py3-none-any.whl |
|---|---|
| Size | 199.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
29aa93e0844634daf3311d533fbbfafbfac9118ff194c28a7897bb73e8988551
|
|
BLAKE2b-256 checksum How to use checksums |
f945e17fb071d3802debd12fd16b1ddf5ee67f51075324d57ef8e75e7aec014c
|
| 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 1, 2026.
Transparency logSecurity for acr-runtime 0.2.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for acr_runtime-0.2.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 1, 2026.
Transparency logA 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.