Changelog

Notable changes to AIOS, newest first. Dates are ISO-8601.

Note

The Team Brain sync contract (Brain API) is versioned separately from the product release. Each entry below names the contract revision it ships.

Unreleased

v0.10.0 — 2026-08-03

The Workspace CLI is now an independently installable package with the devtools extraction completed. This release also adds the guided Team Brain Create path and makes scaffolded codebase reporting produce trustworthy coverage and health evidence.

Added

• One-click Team Brain Create — aios onboard explains the Railway deployment and cost boundary, asks before opening the stable deployment guide, and resumes through the existing origin and API-key validation path. Onboarding never persists an unverified Brain origin or key.
• Devtools preflight — operators can verify all five delegated commands and see whether each resolves from the exact npm dependency or an adjacent checkout.
• Brain-reporting scaffold workflow — new workspaces report real codebase-health and coverage evidence after protected-main pushes.
• aios-deck — a reusable deck-building skill with brand theming and rendered visual QA.

Changed

• ship, build, roadmap-run, spec, and consolidate-findings now execute from exactly pinned @aiosbrain/aios-devtools@0.2.0; their former Workspace implementations were removed.
• Scan workflows now use immutable Actions and scanner revisions, exact hash-locked dependencies, disabled install scripts, and step-scoped Brain credentials.

Fixed

• Failed suites still produce a coverage artifact, absent GUI coverage is no longer reported as zero, SR18 scope fences handle nested and sibling headings correctly, and malformed daily due dates are rejected.

Migration and rollback

• Install the release with npm install -g @aiosbrain/aios@0.10.0.
• Adjacent devtools contributors can export AIOS_DEVTOOLS_DIR; the preflight identifies that source explicitly. Everyone else uses the exact packaged dependency.
• Roll back to @aiosbrain/aios@0.9.1 to restore the last tarball containing the in-tree devtools implementations.

The Team Brain member-facing contract is unchanged at v1.15.

v0.9.0 — 2026-08-01

The multi-repo split release. The one-repo Workspace layout is cut along declared, tested seams into a published foundation package, a standalone GUI repo, and a devtools repo — while the core toolkit in aios-workspace stays authoritative for every cut surface until the deferred deletion PRs land.

Repo topology

• @aiosbrain/foundation 0.1.0 published to npm (public) — the shared hub modules (runtimes, workspace-parse, brain-config, linear-client, brain-client, git-files, constitution) extracted into the packages/foundation/ npm workspace. The old scripts/ paths remain as one-line re-export shims, so nothing consuming them breaks.
• GUI + desktop shell cut to aiosbrain/aios-workspace-gui — filtered history from the Workspace repo. The in-tree gui/ + src-tauri/ remain present and authoritative in 0.9.0; their deletion from the core repo is a deferred post-demo change (tracked as AIO-612).
• Devtools command set cut to aiosbrain/aios-devtools — bootstrapped via aios repo-bootstrap with pinned-toolkit CI. The in-tree scripts/ implementations remain authoritative until the removal lands.

What’s new in the toolkit

• aios codebase-health — a composed codebase-health scorer + rubric + CLI with an advisory CI baseline delta. Brain API revision 1.15 adds an optional, scalar-only codebase_health object on POST /api/v1/codebases; attaching it to the scan-on-merge payload is opt-in and default-off.
• aios repo-bootstrap — governance stamp installer for split repos, used to bootstrap the cut repositories.
• aios delivery status — cross-repo PR/worktree/branch reconciliation over a durable split-delivery manifest.
• GUI seam commands — catalog, gen-catalog, and connector are now first-class registry commands: the GUI server shells the aios CLI instead of reaching into toolkit scripts.

Migration (0.8.0 → 0.9.0)

• Existing workspace owners: run aios update once, and set AIOS_TOOLKIT_DIR in your workspace .envrc to your toolkit checkout. No re-scaffold is needed.
• Standalone GUI installs (from aios-workspace-gui) must locate the toolkit explicitly — set AIOS_TOOLKIT_DIR or pass --toolkit-dir. The built-in relative fallback only resolves in the in-tree monorepo layout.
• In-tree GUI still works: because the deletion is deferred, npm run gui from the Workspace repo is unchanged this release.
• Desktop (Tauri) is adjacent-checkout mode only and not demo-ready; self-contained bundling is tracked in the GUI repo (AIO-581).

This release ships member-facing Brain API contract v1.15 (additive within major v1).

v0.8.0 — 2026-07-28

What’s new

• Onboarding V2 — one inspect-first onboarding contract across the Workspace, Team Brain, and public website, with three explicit paths: Personal, Join, and Create.
• Safe upgrades — aios update --preview shows the planned update and safety checks before any mutation, followed by an explicit human approval.
• Reliable Team Brain connection — the API key is authoritative, team_id is optional, the exact Brain origin requires approval, and GET /api/v1/me validates the connection before setup is marked complete.

Changed

• Team Brain keeps workstation setup discoverable without blocking Pulse, including for members joining an already-active team.
• The Create path is guide-only, and onboarding never pushes workspace content.
• Public quickstart, contributor, troubleshooting, landing animation, and agent prompt now describe the same shipped flow.

Fixed

• Cross-repository contract fixtures and docs-drift checks now prevent the public onboarding instructions from silently diverging from the Workspace implementation.
• Team Brain durably records a successful /api/v1/me connection while ordinary API authentication remains available if non-critical usage telemetry fails.

This release ships member-facing Brain API contract v1.14.

v0.7.0 — 2026-07-04

Cognitive Ergonomics shadow band (workspace + Team Brain)

• Workspace CLI — aios analyze --push now includes an optional ce_band scalar (0–4 or null) on each daily POST /api/v1/metrics payload. Scored client-side relative to your own baseline; the four raw attention signals still never leave the machine.
• Team Brain — Individual Maturity dashboard shows CE beside AM: a CE column on the people table, a CE stat card on member deep-dive, and a dashed amber CE timeline (gaps when no reading). Every CE element is badged shadow · uncalibrated; CE does not enter radar, spine distribution, or team-axis rollups.
• Display rename — “Agentic Engineering Maturity (AEM)” → Agentic Maturity (AM) in product UI and docs (wire metric id aem-individual unchanged).

Sync contract stays v1 — ce_band is an additive v1.3 field on the existing metrics endpoint. See Brain API and the workspace repo’s docs/brain-api.md.

Website

• Landing — deck synthesis — Principles and Honesty sections on the editorial landing page; collective brain architecture diagram in How It Works; Problem lead paragraph bridging deck narrative.
• Docs — anatomy reference — The 8 organ systems Starlight page adapted from Team Brain ARCHITECTURE.md, with shipped/partial/planned status.
• Product deck — standalone slideshow at /deck/ (keyboard + touch navigation), linked from the site footer.

v0.6.0 — 2026-07-03

The aios ship pipeline (workspace toolkit)

One gated command per issue, one walker per roadmap. The proven plan → adversarial review → build → bot review → consolidated fix loop → gated merge workflow is now first-class tooling in the workspace repo:

• aios ship <ISSUE> — runs the whole loop for a single tracker issue: recon → plan (adversarial PLAN_READY gate) → isolated worktree build → PR → bot + GPT reviews → consolidated fix rounds → merge gate → cleanup, with operator gates on by default (--auto / --auto-merge to run unattended) and a local-only audit trail per issue.
• aios roadmap-run — the serial walker: picks the top unblocked issue from a label/epic/project, ships it, fast-forwards main, moves to the next; defined escalation conditions and a morning digest.
• aios pr — push the build branch + open the PR with the issue key in the title (idempotent); push/PR is the tool’s job, never the build agent’s.
• aios consolidate-findings — dedupes CI + review-bot + model-review findings into one severity-ranked must-fix list (a merged finding inherits the max source severity, never downgraded) that feeds fix rounds automatically.
• Per-step model config — .aios/loop-models.yaml maps every pipeline step to a model + effort, with a fail-closed diversity guard: the builder and its reviewer must be different model families.
• Hardening — the build agent runs with a scoped worktree fence and a cleaned environment; review calls auto-retry on timeout with size-scaled limits; the bot wait gate is fail-closed by default (--any to opt out).

Sync contract unchanged: the Brain API stays v1 — no protocol change in this release. Full details in the workspace repo’s CHANGELOG.md at tag v0.6.0.

v0.5.0 — 2026-06-19

Agentic Engineering Maturity (AEM)

• Individual maturity — aios analyze builds an AEM report from your local agent-session logs (Claude/Codex/Cursor) and, with --push, sends a daily aggregate to the brain. Only ratios and counts cross the boundary — raw session content never leaves your machine; the brain recomputes the canonical Spine/axes so team rollups have one authority.
• Codebase agent-readiness — aios assess-codebase scores a repo’s agent-readiness (L0–L5) against the shared rubric; --push records the scan in the brain. A scanner-side Python scorer applies the same rubric on the ingestion path.

Team Brain

• New endpoints (additive — the sync contract stays v1): POST /api/v1/codebases (codebase scan ingest) and POST /api/v1/metrics (AEM individual daily aggregate). Both are team-tier only — an external-tier key gets 403 forbidden_tier, and the metrics endpoint persists aggregates only (never raw session text).

Tooling

• aios relay — an automated Opus ↔ Cursor plan/review loop: Opus plans, Cursor executes, Opus reviews, repeating for N rounds (default 3).

v0.4.0 — 2026-06-17

Onboarding & memory

• Onboarding from a link now drafts into two-axis durable memory (.claude/memory/USER.md + WORKSPACE.md) — confirm before write.
• Suggested integrations — after a link-draft, the agent matches detected tools to connectable integrations and offers to connect them (advisory; never auto-connects).
• Update memory on request (“remember that …”, “update my tooling”) and an opt-out background memory reviewer that conservatively saves durable facts with undo.

Skills

• Marketplace tier — install first-party Anthropic skills from claude-plugins-official via fetch-on-install with byte-diff authenticity (alongside the official and community tiers).

Runtimes & security

• BYOA: OpenClaw on the ACP adapter (hardened stdout) + recorded-transcript CI gates.
• Encrypted .env — connector secrets are encrypted at rest via dotenvx.

The Team Brain sync contract is unchanged (still v1).

v0.3.0 — 2026-06-17 — The cockpit overhaul

The local cockpit (npm run gui) becomes a real workspace cockpit. No change to the spine, validators, guard, harnesses, or the Team Brain sync contract.

Cockpit chat

• Model picker — choose Sonnet 4.6 (default) or Opus 4.8 and switch mid-session with no reconnect; the choice persists to aios.yaml.
• Resumable chats — a sidebar of saved conversations; reopen one to resume the same session, or start a new one.
• Context (est.) meter — an approximate read of how much of the model’s window the last turn used.
• Markdown rendering — assistant replies render as GitHub-flavored markdown.
• Personality presets — AIOS, Analyst, Coach, Operator. A style layer only; it never overrides your rules, CLAUDE.md, or skills.

Skills library

• One-click install of official Anthropic skills, vendored from anthropics/skills, hash-locked, all Apache-2.0: skill-creator, mcp-builder, web-artifacts-builder, claude-api, frontend-design.
• Document skills (Word, Excel, PowerPoint, PDF) are Anthropic-hosted pointers — Enable in Claude — not copied into your repo.
• Community installs, scanned — install skills beyond the official library behind a static safety scan and a consent gate. The scanner flags bundled code (including extensionless shebang scripts), network calls, secret reads, external URLs, and prompt-injection; a high-risk skill requires a typed confirm. Scanning is advisory — official skills stay one-click.

Onboarding

• Draft your profile from a link — paste a URL and the agent reads it with Firecrawl, then drafts .claude/CLAUDE.md for you to confirm before it’s written.