Skip to content

Releases

v0.12.1

Choose a tag to compare

@github-actions github-actions released this 30 Oct 11:51
Loom 0.12.1

v0.12.0

Choose a tag to compare

@github-actions github-actions released this 28 Oct 16:57
Loom 0.12.0

v0.11.0

Choose a tag to compare

@github-actions github-actions released this 26 Oct 17:48
Loom 0.11.0

v0.10.2

Choose a tag to compare

@github-actions github-actions released this 25 Oct 15:01
Loom 0.10.2

v0.10.1

Choose a tag to compare

@github-actions github-actions released this 24 Oct 04:43
Loom 0.10.1

Loom v0.10.0 — Harness² analysis, Skill inventory + validation, Pillars 1-4 landed

Choose a tag to compare

@tusharmewara tusharmewara released this 22 Oct 10:48

Loom v0.10.0

Major Features

Harness² Analysis + Skill Inventory Overhaul

  • Category analysis of Google Research's Harness² (docs/LOOM_HARNESS2_ANALYSIS.md) — different category (method, not competitor); Rust-native adoption path scoped to a 3-day slice
  • Skill inventory, validation & trigger generation (fa29056):
    • One scan pass over ~/.loom/skills/ handling both dir (SKILL.md) and flat (.md) layouts
    • 7 defect codes: missing_description (Fatal), missing_name, name_mismatch, invalid_frontmatter, empty_body, missing_script, duplicate_name
    • loom skills install/remove now accepts both layouts; refuses Fatal defects
    • trigger_lines() generates agent-facing trigger lines with cap + not_triggered tracking
    • loom doctor shows skill-validation row; loom skills list shows per-skill defects + triggers
    • loom lock --generate now produces a real lockfile (11 skills on this machine)
    • loom-skills 82 tests pass; neutral_renderer.rs (373 lines, dead, uncompilable) deleted

Pillar 1 — Harden the Core (7457c72)

  • CLI bounded backoff to daemon (8 attempts, 200ms→1s) + actionable error ("run loom daemon restart")
  • Embedded-pane dispatch now single owner (App::dispatch_embedded_pane), resolves agent from full task record, falls back to PATH binary, test asserts spawn works
  • Backlog reconciled: daemon-lifecycle tests landed, 5/6 routing debts closed, keyword weight corrected (0.35 in code)

Pillar 2 — Security & Trust (e0edb50)

  • Self-verifying audit export: recomputable chain over normalised outcome (legacy raw-result entries still verify) + Ed25519 per-machine anchor (<loom_dir>/auth/export-signing.key); three verdicts INTACT/TAMPERED/UNANCHORED, never "intact" without pinned key
  • Per-run container network posture: NetworkPolicy::NoNetwork | Restricted{allowed_hosts} | Unrestricted; Docker auto_remove restored; k8s NetworkPolicy created BEFORE Job; CNI caveat documented
  • Scoped revocable grants: derived per-run credential (master secret never leaves vault), expiry checked at USE, rotation invalidates, grants.json 0600, no new crypto deps

Pillars 3+4 — Protocol Spec & Usage Metering (d8eb9db, a31740d)

  • Public Protocol Spec v1.0.0 (docs/protocol/adapter-and-acp-protocol.md): Adapter contract + ACP dispatch server (TCP, Ed25519 challenge-response, daemon wiring, CLI surface, 236 body anchors + 146 index entries verified)
  • Usage Metering Ledger: UsageSource{Measured,Estimated,Unavailable}; exactly ONE meter owner (loom_telemetry::UsageMeter); "unavailable" printed when provider reports nothing; cost-only runs reported not measured; ACP v1 usage_update correctly labelled unstable

Phase B Contrast Experiment — NEGATIVE (3f4887e)

  • 5 planted defects, 10 runs (base vs candidate), graded by crate's own test suite
  • Result: candidate identical to base in 5/5 → signal ZERO → probe loop does NOT ship (Phases C/D/E not built)
  • Spend: $0.00 / ~41 min (1.24M input / 86k output tokens) against $10-20 cap
  • Second finding: surface hint read but not injected — Loom writes nothing to agent standing context

Other

  • All independent review records on main with RESOLVED banners: Phase A (fa29056), Pillar 1 (7457c72), Pillar 2 (e0edb50), Pillars 3+4 (d8eb9db, a31740d)
  • CI: 5-job matrix (test, container, integration, benchmarks, security)
  • cargo test --workspace green (excluding network-gated acp_live test); clippy clean; fmt clean
  • 31 crates, version 0.9.6 (next: 0.10.0)

Artifacts

  • Tarball: loom-0.10.0.tar.gz
  • sha256: 05907f187ceca1047807cee369587418e527a0fefebf6b022177b0d759681075

Loom 0.9.6

Choose a tag to compare

@tusharmewara tusharmewara released this 20 Oct 07:39

Added

  • feat(acp): loom acp registry [--available] [--json] lists all 42 agents in the public ACP registry, marking locally registered ones with *
  • feat(acp): ACP agents can now be launched with an env map (registry env blocks are honored, e.g. FAST_AGENT_MODEL for fast-agent)

Fixed

  • fix(tui): the Kanban and Orchestrator tabs no longer trap tab navigation — both tab-specific key handlers ran before the global handler and swallowed Tab/Shift-Tab/←/→, so the Orchestrator tab could not be left at all and the Kanban tab could not be switched away from. Kanban now uses h/l for columns and j/k for rows; the Orchestrator uses ↑/↓ for field focus and ←/→ for tool selection
  • fix(acp): loom acp run <agent> now resolves the agent's real launch command — explicit path → local config/agents.toml entry → public ACP registry → PATH binary — instead of spawning a bare binary with no arguments. Agents were previously started outside ACP mode (e.g. opencode without its acp flag) and timed out on initialize
  • fix(acp): loom add-acp-agent now picks a usable distribution deterministically (npx > uvx > binary, resolved for the current platform) instead of an arbitrary first key of the registry distribution map, so agents like kilo and sigit keep their package runner and their acp mode flag
  • fix(acp): uvx agents are resolvable — the daemon's agent launcher previously understood only npm and pip runners
  • fix(acp): a JSON-RPC error returned by the agent during session/prompt is now reported as ACP session/prompt failed: <error> instead of being masked as ACP session/prompt timed out

Changed

  • fix(homebrew): bottle releases are published under a vX.Y.Z-bottles tag in the tap repo. The tap's plain vX.Y.Z tag namespace is permanently reserved by GitHub once a tag has been used by an immutable release and can never be recreated, which broke the 0.9.5 publish
  • chore: cargo fmt --all across the workspace — 8 files that had drifted out of rustfmt compliance (loom-routing outcomes.rs/scorer.rs, loom-cli commands/routing.rs, loom-tui app.rs/ui/tabs/kanban.rs, loom-workflow task_manager.rs, two loom-integration-tests)

Loom 0.9.5

Choose a tag to compare

@tusharmewara tusharmewara released this 19 Oct 16:16

Changelog

All notable changes to the Loom project will be documented in this file.

The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.

[0.9.5] - 2026-10-19

Added

  • docs: architecture diagrams — static SVG (docs/diagrams/architecture-export.svg) and interactive HTML (docs/diagrams/architecture.html), embedded in the README intro
  • docs: competitive analysis refresh — Orca (stablyai) tool-by-tool entry, Orca column in the feature matrix, shipped-status annotations across the P0/P1/P2 roadmap items (worktrees, containers, PR integration, remote SSH, Kanban/Graph/Cost tabs, ACP registry, cross-session recall all marked shipped)
  • docs: man pages rewritten for 0.9.x — manpages/loom.1 covers all 36 subcommands (incl. cfg-gated tui), the 12 adapters, the 15 TUI tabs, corrected hook event types (PreToolUse/PostToolUse/SessionStart/PostPhase) and honest environment-variable docs (LOOM_AGENTS_DIR, not the never-honored LOOM_DIR); manpages/loomd.1 documents the gRPC server, TLS env vars, ZeroMQ event socket, and the WSL2/Unix-socket constraint
  • docs: docs/ is no longer gitignored — analysis docs and diagrams are tracked; only the archify JSON intermediates (docs/diagrams/*.json) stay ignored

Changed

  • docs: README rewritten with source-verified facts (12 adapters, 15 tabs, 31 crates, CHANGELOG-driven version history, working links) replacing the 0.3.x-era drift
  • feat(tui): tab bar shows per-tab shortcut labels (1–9, 0, !, @, #) and scrolls to keep the active tab visible on narrow terminals
  • feat(tui): Kanban tab renders workflow phases (Plan → Implement → Verify → Finish) as columns with per-task selection; the custom scrollbar widget was removed in favor of native scrolling

Fixed

  • fix(workflow): git worktree add now retries with --orphan (git ≥ 2.42) for repositories without any commit, and worktree isolation is best-effort — a non-git project directory or missing git no longer blocks task creation (the task runs in the project directory instead)

[0.9.4] - 2026-10-18

Added

  • feat(routing): persisted decision + outcome telemetry (crates/loom-routing/src/outcomes.rs) — SQLite store at ~/.loom/telemetry/routing.db records one row per task-bound decision (signals JSON, numeric, level, tier, model, token estimates) and closes it with an outcome: completed when the task reaches Finish, overridden when a manual tier override rejects the heuristic's pick; new loom routing outcomes [--limit N] reports recent decisions and outcome counts, giving the decision-model flip condition its evidence surface
  • feat(core): [security] require_signature config flag (default off) — when enabled, unsigned hooks are skipped and unsigned plugins are rejected at install; documents the trust model explicitly (loom dir contents are user-owned local state)
  • feat(config): config/security.toml overlay joins the merge chain alongside routing.toml/mcp.toml/hooks.toml/acp.toml
  • feat(core): derive_level(numeric, thresholds) and derive_tier(level) — one exported source of truth for complexity level and model tier derivation
  • docs: track ROADMAP.md (previously untracked, referenced by the routing debt record)

Changed

  • refactor(routing): the level/tier derivation duplicated across scorer.rs, router.rs, task_manager.rs (×2) and the CLI now routes through derive_level/derive_tier; configurable complexity_thresholds govern level as well as tier, making the Supplement's "these thresholds are configurable" claim true
  • refactor: dedupe cross-crate helpers into loom-core, split workflow machinery, dependency hygiene
  • chore: workspace cargo fmt and clippy 1.99 drift lints (result_large_err, useless_format, borrow in println)
  • chore: __pycache__/ gitignored; release-bottle script untracked (artifact dirs are gitignored)

Fixed

  • fix(routing): extract_signals counted bytes, not chars, inflating the length signal ~3× for UTF-8 CJK prompts and biasing CJK tasks toward higher tiers
  • fix(core): ComplexityThresholds derived Default was {0.0, 0.0} rather than the serde defaults (0.35/0.7), so any routing config without a [complexity_thresholds] section treated every score as High → Flagship
  • fix(routing): the level-vs-tier contradiction (config low_max = 0.3 + numeric = 0.32 yielded level = Low but tier = Mid) is resolved by the unified derivation
  • fix(cli): init's routing.toml template claimed threshold defaults 0.33/0.66; corrected to the shipped 0.35/0.7
  • fix(routing-hook): the Python hook imported third-party toml (ImportError on any machine without pip install toml); now uses stdlib tomllib (Python ≥ 3.11), with the no-op-on-error contract unchanged
  • ci: install protoc for the integration and test-matrix jobs; fail cargo steps properly (set -o pipefail); --all-features builds no longer break on duplicate cfg-gated imports

Security

  • fix(core): plugin downloads were HTTPS-only for remote config but accepted plain http:// for plugins — install_from_url and update() now reject non-HTTPS URLs before any network I/O, closing an on-path tool-TOML swap
  • feat(security): require_signature trusts nothing unsigned when enabled — hooks skip and plugin installs fail rather than running unverified code

Tests

  • test(routing): characterization suite pinning hook and scorer behavior before the refactor — 7 routing_hook.py contract tests (plain asserts, tempfile rules files, never ~/.loom), user-override precedence, and the adversarial keyword ceiling (keyword weight 0.35 clamps at max 0.35 contribution, so keywords alone cannot force Flagship on the static path)
  • test(routing): boundary and contradiction coverage for derive_level/derive_tier, including the strict-< edges at low_max/high_min (previously only the 0.5 midpoint was tested)
  • test(core): HTTPS rejection on install and update, unsigned-plugin policy follows the flag, half-signed manifests rejected, security config parse and default
  • test(routing): outcome-telemetry store and full workflow flow (create → advance ×3 → override → Finish = 4 rows: 3 completed, 1 overridden)

[0.9.3] - 2026-10-09

Fixed

  • fix(loom-ipc): sync IPC handlers now run on a bare scoped thread instead of inside the async connection task — handlers that drive tokio runtimes internally (Handle::block_on / Runtime::block_on) panicked with "Cannot start a runtime from within a runtime", breaking loom acp status/show/stop, loom hooks list, and tool availability checks (the CLI surfaced this as EOF while parsing a value at line 1 column 0); a panicking handler now returns an error response instead of dropping the connection

Changed

  • chore: workspace clippy cleanup — cargo clippy --workspace --all-targets reports 0 warnings (was ~110): dead code removed (loomd capture.rs never-wired tracked-spawn chain, gRPC shutdown channel, loom-remote default_key_paths, ForgeManager.loom_dir field), lint fixes (matches!, sort_by_key + Reverse, while let, needless pass-by-value, complex type aliases), #[allow(dead_code)] on deserialized-but-unread serde response fields, ///! → //! doc-comment headers, integration tests no longer drop save_manifest Results
  • chore(loomd, loom-tui): container runtime features (docker/podman/kubernetes) forwarded via [features] instead of forced on every dependent build

[0.9.2] - 2026-10-06

Added

  • feat(loom-auth): audit trail integrity verification — SHA-256 hash-chained audit log (prev_hash/entry_hash on AuditEntry) with verify_integrity() tamper detection; chain survives restarts and log rotation; legacy unchained entries are tolerated

Loom v0.9.4

Choose a tag to compare

@tusharmewara tusharmewara released this 18 Oct 16:44

Routing debt closed. This release pays down the seven items from the internal routing debt record, plus the security hardening they surfaced.

Added

  • feat(routing): persisted decision + outcome telemetry (crates/loom-routing/src/outcomes.rs) — SQLite store at ~/.loom/telemetry/routing.db records one row per task-bound decision (signals JSON, numeric, level, tier, model, token estimates) and closes it with an outcome: completed when the task reaches Finish, overridden when a manual tier override rejects the heuristic's pick; new loom routing outcomes [--limit N] reports recent decisions and outcome counts, giving the decision-model flip condition its evidence surface
  • feat(core): [security] require_signature config flag (default off) — when enabled, unsigned hooks are skipped and unsigned plugins are rejected at install; documents the trust model explicitly (loom dir contents are user-owned local state)
  • feat(config): config/security.toml overlay joins the merge chain alongside routing.toml/mcp.toml/hooks.toml/acp.toml
  • feat(core): derive_level(numeric, thresholds) and derive_tier(level) — one exported source of truth for complexity level and model tier derivation
  • docs: track ROADMAP.md (previously untracked, referenced by the routing debt record)

Changed

  • refactor(routing): the level/tier derivation duplicated across scorer.rs, router.rs, task_manager.rs (×2) and the CLI now routes through derive_level/derive_tier; configurable complexity_thresholds govern level as well as tier, making the Supplement's "these thresholds are configurable" claim true
  • refactor: dedupe cross-crate helpers into loom-core, split workflow machinery, dependency hygiene
  • chore: workspace cargo fmt and clippy 1.99 drift lints (result_large_err, useless_format, borrow in println)
  • chore: __pycache__/ gitignored; release-bottle script untracked (artifact dirs are gitignored)

Fixed

  • fix(routing): extract_signals counted bytes, not chars, inflating the length signal ~3× for UTF-8 CJK prompts and biasing CJK tasks toward higher tiers
  • fix(core): ComplexityThresholds derived Default was {0.0, 0.0} rather than the serde defaults (0.35/0.7), so any routing config without a [complexity_thresholds] section treated every score as High → Flagship
  • fix(routing): the level-vs-tier contradiction (config low_max = 0.3 + numeric = 0.32 yielded level = Low but tier = Mid) is resolved by the unified derivation
  • fix(cli): init's routing.toml template claimed threshold defaults 0.33/0.66; corrected to the shipped 0.35/0.7
  • fix(routing-hook): the Python hook imported third-party toml (ImportError on any machine without pip install toml); now uses stdlib tomllib (Python ≥ 3.11), with the no-op-on-error contract unchanged
  • ci: install protoc for the integration and test-matrix jobs; fail cargo steps properly (set -o pipefail); --all-features builds no longer break on duplicate cfg-gated imports

Security

  • fix(core): plugin downloads were HTTPS-only for remote config but accepted plain http:// for plugins — install_from_url and update() now reject non-HTTPS URLs before any network I/O, closing an on-path tool-TOML swap
  • feat(security): require_signature trusts nothing unsigned when enabled — hooks skip and plugin installs fail rather than running unverified code

Tests

  • test(routing): characterization suite pinning hook and scorer behavior before the refactor — 7 routing_hook.py contract tests (plain asserts, tempfile rules files, never ~/.loom), user-override precedence, and the adversarial keyword ceiling (keyword weight 0.35 clamps at max 0.35 contribution, so keywords alone cannot force Flagship on the static path)
  • test(routing): boundary and contradiction coverage for derive_level/derive_tier, including the strict-< edges at low_max/high_min (previously only the 0.5 midpoint was tested)
  • test(core): HTTPS rejection on install and update, unsigned-plugin policy follows the flag, half-signed manifests rejected, security config parse and default
  • test(routing): outcome-telemetry store and full workflow flow (create → advance ×3 → override → Finish = 4 rows: 3 completed, 1 overridden)

Install: brew install tusharmewara/loom/loom (bottles attach below once the release workflow finishes).

v0.9.3

Choose a tag to compare

@github-actions github-actions released this 10 Oct 02:47
v0.9.3