Skip to the content.

Roadmap & status

Weft is built in phase order. Each phase has explicit acceptance criteria, and a later phase’s packages are not started before the current phase’s acceptance passes.

Status: released as weft 1.1.0 on npm (@michaelfromyeg/weft-*), renamed from “loom”. Phases 0-4 plus the post-v1 work in Phase 5 are done; everything under “Beyond v1” is the honest not-yet-built boundary.

Phase 0: Prove the compile (Claude Code only), DONE

Packages: @michaelfromyeg/weft-schema, @michaelfromyeg/weft-core, @michaelfromyeg/weft-adapter-kit, @michaelfromyeg/weft-adapter-claude, @michaelfromyeg/weft-cli.

Acceptance (all met, exercised by pnpm test):

@michaelfromyeg/weft-adapter-kit was created in Phase 0 (not Phase 1 as the spec lists it) because @michaelfromyeg/weft-adapter-claude implements its HarnessAdapter interface. Only the interfaces + helpers exist so far; the HarnessDriver implementations land in Phase 1.

Brought forward from later phases (already implemented)

Vocabulary note: the canonical authoring unit is a plugin (cross-harness), and a marketplace packages many plugins. There is no separate “bundle” concept. See concepts.md.

Phase 1: Breadth + drivers + deterministic evals, DONE

Packages: the four remaining @michaelfromyeg/weft-adapter-* (codex, cursor, copilot, opencode), @michaelfromyeg/weft-eval (runner + five HarnessDrivers via execa).

Many adapter facts beyond Claude are marked // TODO(verify): in-code where upstream docs are thin (e.g. Copilot marketplace shape, Cursor remote MCP header serialization). They are isolated behind each adapter’s targetSchema per spec §2. (Codex’s plugin + marketplace format is now CONFIRMED as of the v0.121 adapter rewrite – see harness-research.md.)

Key verified facts for the drivers (see harness-research.md): Claude needs --output-format stream-json --verbose for a trace (plain json is a single result object); Codex exec --json; Cursor --output-format stream-json; Copilot has no structured trace (degrade to output); OpenCode run --format json or the SDK /event.

Phase 2: Index, federation, badges, CI, DONE

Package: @michaelfromyeg/weft-index (build + client + MCP-Registry federation + badges + publish gate).

Phase 3: Trust & subjective evals, DONE

Out of scope for v1 (noted in the spec): a hosted CI eval tier (BYO-keys local is the default) and an index UI. The deterministic gate already runs the same driver invocations a hosted runner would.

Phase 4: Lifecycle & federation extras

Beyond the original spec, two lifecycle commands round out the loop:

Phase 5: Rename, target-side lifecycle, and breadth, DONE

Renamed from loom to weft (no backwards compat) and released 1.0.0 then 1.1.0 to npm; the repo is github.com/michaelfromyeg/weft. Tag-triggered CI publishes every @michaelfromyeg/weft-* package and cuts the matching GitHub release.

Beyond v1 (planned)

Not built yet; tracked so the boundary is honest. Grouped by theme, roughly in priority order within each group. Nothing here blocks using Weft today; most items swap a production backend in behind an interface that already exists.

Trust & supply chain

The one real gap in the trust story is ownership. Everything else here is a backend swap.

Authoring experience

Shipped: weft build --check compares --out against a fresh compile (via diffPlanned over the build plan’s content hashes) and exits 1 on drift, writing nothing. It is the build-output side of the same content-hash machinery: the CI guard that keeps a committed weft build . --target claude --out . --bare marketplace from silently drifting from source.

More harnesses

The adapter-kit seam is designed for this; each is a new package, no core change.

Shipped: a generic skills-only adapter (genericSkillsAdapter) for the directory-convention harnesses that load SKILL.md from a <root>/skills/ layout (the .agents/skills/ family). Zed, Gemini CLI, Amp, and Aider are wired up as targets today; adding another is one row in the CLI registry. These get skills only; the five deep harnesses keep full plugin support.

Resolver depth

Shipped: weft install/build now resolve a remote target, not just depends. A github:/git/npm:/owner/repo ref is fetched into ~/.weft/cache (git clone or npm pack) and installed from there, and a trailing //subdir selects a plugin or marketplace nested in the source (e.g. weft install github:owner/repo//marketplace).

Discovery & operations

Distribution

Invariants held throughout

  1. Compiler, not platform; the library is the product.
  2. Single source of truth; generated files are never hand-edited.
  3. Standards as inputs, adapters as the seam; upstream churn touches one adapter.
  4. Federate, don’t wall off.
  5. Same primitives at every scale; scope + policy differ, mechanism does not.
  6. Honest coverage; untested harnesses are reported, never faked.