entroly

---

What is Entroly? (in plain English)

Entroly is a local-first context control plane for AI coding tools. It selects evidence within a token budget, preserves recoverable omissions, and records selection decisions in receipts. Three properties to evaluate on your task:

💰 Avoidable input cost	Smaller requests can reduce input cost when they reach a provider through an Entroly-controlled route. The result depends on the workload and provider cache — see the real numbers below.
🔍 Recoverable originals	Receipt-backed recovery retains source material locally. Exact recovery requires the referenced store and source bytes to remain available; it does not guarantee answer quality.
🧾 You can check its work	Every decision comes with a receipt: what was kept, what was left out, and why.

Do I have to change my code? No. On hosts with a verified prompt hook, Entroly runs before the model plans. MCP-only integrations remain callable tools that an agent may skip; API traffic is intercepted only when it is routed through the Entroly proxy. Check entroly activation status --json instead of assuming an installed integration is active.

Do I need to pay for anything to try it? No. The two commands in the Install section below run on your own machine, with no API key, and show you real numbers on your own project before you connect anything paid. (Missing native-engine support is reported without downloading packages — see the note under Install.)

Switching coding agents mid-task? entroly-work resume reconstructs unfinished work from durable repository evidence, even if the previous agent left no handoff. The receiving agent must review the inferred state and acknowledge it before claiming work through Entroly. Start with entroly-work --project . --json resume --to-agent codex; the agent continuity guide shows the complete flow and how to measure whether it actually saves rediscovery work on your tasks.

---

Contributing

Start with development setup and repository layout, then follow the architecture, style guide, and test instructions for the surface being changed. Source, delivery adapters, and benchmark evidence have different review requirements; the contributor guide explains their boundaries.

Install

Not sure which one? Pick Python. It's the complete version and what most people use. The other packages expose different runtime surfaces. | Platform | Install | What you get | |---|---|---| | 🐍 Python (pip) — recommended | pip install -U entroly | Everything: the command-line tool, the server your AI editor talks to, and the code library | | 📦 Node / npm | npm install -g entroly | Local Node/WASM CLI; the Python package has a broader CLI, SDK, and proxy surface | | 🦀 Rust (source build) | cd entroly-core && cargo build --release --bin entroly-rs --features proxy | One self-contained program, no Python or Node needed | | 🍺 Homebrew | brew install juyterman1000/entroly/entroly | The command-line tool on macOS/Linux | | 🐳 Docker | docker pull ghcr.io/juyterman1000/entroly:latest | Runs in a container, nothing installed on your machine |

Prefer a package runner instead of a global install? These commands use the same published artifacts in an isolated tool cache:

# Node or Bun / WASM runtime
npx -y entroly@latest --help
pnpm dlx entroly@latest --help
bunx --bun entroly@latest --help

# Complete Python runtime
uvx --from entroly entroly --help
pipx run --spec entroly entroly --help

The Node commands provide the local WASM CLI. The Python commands provide the complete CLI, SDK, MCP, proxy, verification, and native-engine path described above. Entroly's release workflow smoke-tests all five runners against the exact version before a release is considered complete.

Now check that it worked — free, no API key:

cd /your/repo
entroly verify-claims
entroly simulate

Both run locally. Neither calls an AI or proves answer quality, activation, or a lower provider bill. Use a task-specific --query with simulate; if it reports Relevance ranking is OFF, run entroly doctor before evaluating the selection.

Runtime package repair is off by default. If the native engine is missing, query-conditioned selection is unavailable and reduction figures are labelled unearned. Install it explicitly with python -m pip install -U entroly-core, call entroly.repair() from Python, or set ENTROLY_ENABLE_SELF_HEAL=1 to permit startup repair. This downloads through the configured package index (normally PyPI). ENTROLY_NO_SELF_HEAL=1 and ENTROLY_AIR_GAP=1 override repair consent. See Privacy and recovery-data security.

Extras (entroly[proxy], entroly[native], entroly[full]), the standalone Rust binary, and uninstall steps: Engine & install options.

Contributing from source? Follow the reproducible development setup. Local installation and the normal test suite need no API key; .env.example documents only optional workspace, offline, provider, and proxy settings.

---

Quickstart — by how you work

Start with the local check. entroly go registers an MCP server for a detected editor and starts a proxy and dashboard. Route API traffic through that proxy or use a supported host hook, then verify that the integration actually ran. The table below shows the available paths. | Your situation | Do this | What it gets you | |---|---|---| | 🟢 "I control my app's API base URL." (pip / Python user) | pip install -U entroly && entroly go | Starts the local proxy and dashboard; point your app at the displayed URL and check observed requests with entroly value --json | | "I use Node, not Python." (npm user) | npm install -g entroly && entroly init | Node/WASM CLI and local MCP path; use Python for the full proxy and SDK path | | "I want one binary, no runtime." (Rust user) | cargo build --release --bin entroly-rs --features proxy (from entroly-core/) | A single native program with no dependencies | | "I use Claude Code, Codex, Gemini CLI, or VS Code agent plugins." (plugin user) | Install the Entroly plugin/extension for that host, submit one prompt, then run entroly activation status --json | A trusted prompt hook performs bounded local selection before planning; a receipt proves the hook ran | | "I use Cursor with third-party configs enabled." | entroly activation install --host cursor --project . | Merges a reversible Claude-compatible prompt hook; native Cursor MCP remains advisory | | "I use Kiro IDE 1.x or CLI 3.x." | entroly activation install --host kiro --project . | Installs a reversible project PromptSubmit hook whose stdout is added to agent context |