V2026.6.0 Announcement

AIWG 2026.6.0 — OpenHuman, declarative Flows, and corpus-level research

Released 2026-06-12

AIWG 2026.6.0 — a multi-platform AI deployment framework: a central hub linked to distinct provider nodes, a knowledge-graph cluster, and an orchestration pipeline

The June release covers a wide surface area, introducing a new deployment provider, a declarative orchestration layer, and a research framework capable of analyzing an entire corpus rather than just storing papers. Alongside routine cross-provider hardening, the discovery layer now handles natural user queries more reliably. Note that highly complex requests still demand precise terminology.

Install or upgrade:

npm install -g aiwg          # fresh install (stable)
aiwg refresh                 # update an existing install + redeploy

OpenHuman is AIWG's 11th provider

OpenHuman (tinyhumansai) is an open-source personal-AI runtime. It pairs a Rust core with a Tauri desktop shell, and can drive `claude_code` and `factory` as inference backends. As of 2026.6.0, AIWG supports it as a first-class deployment target:

aiwg use sdlc --provider openhuman

The deploy is a hybrid that matches OpenHuman's own conventions:

  • Kernel skills install globally to `~/.openhuman/skills/<name>/SKILL.md` — the ungated user-scope root OpenHuman scans unconditionally, and the exact path OpenHuman's own "Install from URL" writes to. The full standard set stays discover-reachable under `~/.openhuman/.aiwg/skills/`.
  • Personas stay workspace-scoped at `.agents/agents/` for the external coding hosts OpenHuman drives.
  • Commands and rules aggregate into an `AGENTS.md` discover-first bridge.

This is verified live, not theoretical: deploy AIWG and OpenHuman's agent harness scans the `SKILL.md` bundles at startup and event-bus-wires the triggered ones (`aiwg steward`, `capability discovery`, `aiwg pr`, `ops runbook`, …). Your AIWG skills are loaded and usable by OpenHuman's agents the moment you deploy.

One honest caveat: OpenHuman's BETA "Skills Explorer → Installed" tab reads `~/.openhuman/workflows/`, not `skills/`, so deployed skills don't render in that particular panel yet — an upstream OpenHuman limitation that affects its own catalog installs too, not an AIWG deploy issue. The skills work regardless; the panel will catch up.

See the OpenHuman quickstart.

Releases and orchestration run on declarative Flows

AIWG's orchestration is now declarative. `flow-release` and `flow-architecture-evolution` are YAML Flows (`flow.aiwg.io/v1`) rather than prose runbooks:

  • Discoverable directly — `aiwg discover "cut a release"` surfaces the Flow; YAML Flow docs are a first-class discoverable type.
  • Config-driven gates — the release gate sequence lives in `.aiwg/release.config`, so the same skill body works for a CalVer + npm project (like AIWG) and a SemVer + container-only one. Only the config differs.
  • Intra-step multi-agent panels — Flows can fan out a step across an agent panel and synthesize the results, via a documented executor fan-out contract.

Cross-stack Missions

A Mission is a single conductor fanning heterogeneous workers across stacks — a Claude session dispatching Codex subagents, for instance — over the `runtime:<name>` executor convention. `/aiwg-mission` ships AIWG-owned on Codex with no plugin dependency, so the orchestration surface is the same wherever you run it.

The research corpus learned to think

The research framework picked up the tooling that turns a pile of PDFs into a navigable, auditable knowledge base:

  • Semantic + lexical search — `aiwg index query --semantic` (embeddings: `similar`, `dedup-report`) and `--fulltext` (BM25 body search).
  • Citation intelligence — `aiwg corpus extract-crossrefs` and `citation-backfill` densify the citation graph; profile-graph edges link sources by embedding similarity.
  • Integrity + quality — `aiwg corpus integrity-scan` (submission-risk), `sidecar-lint`/`repair` for metadata, per-type induction depth audits with frontmatter backfill.
  • Vision — provider-neutral scanned-page extraction pulls structured content out of image-only PDFs.
  • Extensibility — an open source-type registry with by-source-type views.

Discovery matches how you ask

The discover layer got materially better at natural language:

  • Full questions ("help me choose the right AIWG framework or skill") normalize to keyword phrases and match.
  • Single-content-token queries no longer dead-end.
  • `discover` is now the exclusive agentic-capability surface, auto-builds the framework index from `$AIWG_ROOT` so deployed commands are findable from any project, and induces discover-first on new directives, not just when an agent is about to decline.

Cross-provider hardening

  • Cursor — rules emit as native `.mdc` (not `.md`), and cleanup preserves operator-authored `.mdc`.
  • OpenClaw — Steward identity injected into `SOUL.md`; commands correctly aggregated; discover-first bridge + scope defaults.
  • Warp — `WARP.md` regenerated as a lean discover-first managed bridge (down from a 17.5k-line aggregate).
  • OpenCode — loads `AIWG.md` directive classification via `instructions[]` and wires deployed rules into `opencode.json`.
  • Codex — AIWG-owned `/aiwg-mission`, `AIWG.md` via `instructions[]`, `address-issues`/`issue-audit` as commands.

Housekeeping you'll notice

User-facing CLI output — the `aiwg use` version stamp, the `aiwg diagnose` bug-report link, the entrypoint packaging-bug message — now reads `github.com/jmagly/aiwg`, sourced from `package.json` rather than the internal build origin. And the agentic-sandbox project now publishes its docs as a tenant at docs.aiwg.io/agentic-sandbox, cross-linked from the serve and daemon guides.

npm install -g aiwg