Skip to content

Logic-Loom v0.1.0-alpha.4

Fourth alpha — one place to choose your LLM. A unified provider layer drives Learn, zotero-summarizer, and node generation from a single setting, and the packaged app now finds the agent CLIs installed on your machine.

Builds on v0.1.0-alpha.3 with the unified host-LLM provider system (a Settings chooser plus a shared routing layer behind all three consumers), provider-aware node generation, and a fix so the packaged desktop app can resolve locally-installed agent CLIs (claude, codex, nlm).

Platform availability

Multi-platform, built by the GitHub Actions release.yml workflow on real macOS, Linux, and Windows runners.

  • macOS Apple Silicon — .dmg
  • Linux x86_64 — .deb and .AppImage
  • Windows x86_64 — .msi and NSIS .exe installer

Per-platform SHA-256 manifests ship alongside the binaries as SHA256SUMS files.

What's new since v0.1.0-alpha.3

Unified LLM provider system

A single LLM provider setting (AKMS ▸ Settings) now drives every LLM-backed feature. Pick one global provider — the LiteLLM API route (Anthropic / OpenAI / Google keys), an agent CLI (claude-cli, codex-cli, nlm), or a custom CLI you define — with optional per-consumer overrides for zsum and node generation.

Under the hood, a new host_llm/ layer is the single source of truth: it discovers which providers are actually usable on this machine, resolves the active choice at each adapter boundary (Learn, zsum, node-gen), and exposes GET /api/llm/providers plus a reload endpoint so a provider change takes effect without restarting the app. Every consumer degrades gracefully to a safe default when a provider is unavailable, and the app never mutates your committed config or the global process environment.

Provider-aware node generation

Node generation now dispatches through your chosen provider's own runtime rather than assuming a single backend — the codex path launches in a codex runtime carrying the skill, the NotebookLM path goes through akms_nodes_gen.nlm_batch, and a missing CLI binary degrades to an actionable 400 (with a claude fallback) instead of a 500.

Packaged-app agent-CLI discovery

Fixes a macOS issue where the packaged .app, launched from Finder, inherited only a minimal PATH and therefore reported every CLI provider as "not found" even when claude / codex / nlm were installed. The sidecar now prepends the common install locations (~/.local/bin, /opt/homebrew/bin, /usr/local/bin) to its PATH, so locally-installed agent CLIs resolve for every user with no per-machine configuration.

MechDSL verification runtime

The MechDSL verify path can now provision its Taichi runtime on demand from inside the app, unblocking on-device verification without shipping the heavy runtime in the base bundle. The emit/transpile paths remain Taichi-free and available out of the box, as before.

Under the hood

  • AKMS is now vendored via a formalized in-place content-copy mechanism (scripts/sync_akms_vendor.sh) rather than a git subtree, keeping the flat path-deps stable across upstream refreshes.
  • Repo-integration and tracker wiring salvaged and refreshed.

Verifying downloads

shasum -a 256 -c SHA256SUMS.txt