Skip to content

Releases

Loom v0.2.0

Choose a tag to compare

@github-actions github-actions released this 06 Jul 20:57
c71802a

manifestVersion: 1
releaseTag: v0.2.0
tarballName: loom-0.2.0.tar.gz
sha256: 88819cb70109088d317c0b5f373892e99a47df79d7f5738ae9df0b8e626deba6
sizeBytes: 1207887
producedAt: 2026-07-06T20:57:19.672Z

v0.0.1 — initial public alpha

Choose a tag to compare

@launchstack-dev launchstack-dev released this 15 Jun 02:40

Loom v0.0.1 — initial public alpha.

Loom is a discipline layer on top of Claude Code. Give it a one-line idea — "add user auth with RBAC and team management" — and it drives a multi-agent pipeline from scope decisions, through wave-based execution, to passing tests and reviewed code. Tool-call-level hooks keep agents on-task, in-scope, and within budget.

What's in v0.0.1

Core pipeline — stable and exercised on real work:

  • Pre-flight scope contract. Prompt Refiner + Scope Interrogator turn a loose prompt into a locked decision manifest before any code is written
  • Dual-track planning + scenarios. Plan-builder + criteria-planner run in parallel from the same roadmap; interpretation-reviewer surfaces conflicts before convergence starts
  • Four-tier convergence engine. Unit → integration → e2e → qa-review, mapped to wave / feature / milestone / phase. One iteration pattern (execute → check → triage → remediate), applied across three modes (criteria, target, document)
  • Hook-enforced execution. Thirteen Claude Code hooks block at the tool-call level: file ownership, contract locks after Wave 0, 100k context cap per spawn, wiki integrity, deploy guard, typecheck-on-write
  • Change-proposal lifecycle. /loom-change init → review → approve → run → archive mutates per-domain contract-* wiki pages atomically with drift validation
  • Wiki maintenance. Persistent project knowledge in .loom/wiki/ with automatic state-capture at every pipeline boundary

Install

Stable pin (recommended):

curl -fsSL https://raw.githubusercontent.com/launchstack-dev/loom-ai/v0.0.1/install.sh | bash

Or, for users who want to inspect first or use a local checkout, see the Install section of the README.

Status — what's stable vs. still settling

The core pipeline is shipped and exercised on real work. The distribution layer is alpha:

Area v0.0.1 v0.1.0 (in flight)
Convergence engine + scenarios ✅ —
Change-proposal lifecycle ✅ —
Hook-enforced discipline ✅ —
Wiki maintenance ✅ —
Install curl-only + cosign-signed tarballs, Homebrew formula, version-pinned installer with atomic rollback
Cross-platform macOS + Ubuntu + Windows

Schemas can evolve with migrations — /loom-upgrade handles per-project migration when new versions ship. See planning/plans/PLAN-oss-launch.md for what lands in v0.1.0.

Known limitations

  • Windows not supported. Tested on macOS (Apple Silicon + Intel) and Ubuntu 22.04+
  • Curl install has no auto-update. Re-run the install script or use /loom-library sync to refresh
  • Alpha schema compatibility. Plans + roadmaps written under v0.0.x may need /loom-upgrade migration when v0.1.0 lands

Start here

Contributing

See CONTRIBUTING.md. PRs against main; issue templates in .github/ISSUE_TEMPLATE/; branch protection requires PRs (no direct push). The PR template prompts for what changed, how it was tested, and any related plan or issue.

License

Apache 2.0.