SHELFCRITTER AI Digest

DEVELOPER-TOOL

OpenSpec

developer-tooltopic-notefission-ai

Overview

OpenSpec is a project developed by Fission AI, tracked as one of three monitored repositories in the AI Digest. The project has maintained version stability with v1.2.0 since early March 2026, indicating either feature completion or a maintenance-focused period.

Timeline

  • 2026-05-03-AI-Digest — No new release; v1.3.1 from April 21 remains latest, now twelve days old. Sub-1.5-week cadence is normal; quiet patch continues.

  • 2026-05-02-AI-Digest — No new release; v1.3.1 from April 21 remains latest, now eleven days old. Sub-1.5-week cadence is the running baseline; release gap is unremarkable.

  • 2026-03-08-AI-Digest - OpenSpec v1.2.0 tracking begins

  • 2026-03-12-AI-Digest - Version remains at v1.2.0 (no updates since initial tracking)

  • 2026-03-17-AI-Digest - Version stability maintained

  • 2026-03-22-AI-Digest - No updates reported

  • 2026-03-27-AI-Digest - No updates reported

  • 2026-03-31-AI-Digest - No updates reported

  • 2026-04-06-AI-Digest — v1.2.0 remains latest; no new release since February.

  • 2026-04-07-AI-Digest — No new release; v1.2.0 current with profiles system and Pi/Kiro IDE support

  • 2026-04-07-AI-Digest — No new release; v1.2.0 from February remains latest with support for 21 AI tools.

  • 2026-04-08-AI-Digest — No new release; v1.2.0 still current. Issue activity continues through early April but no new tagged releases.

  • 2026-04-22-AI-Digest — v1.3.1 (April 21, 2026) lands with path and telemetry fixes: canonical artifact path resolution through realpath, glob artifact output corrections, cleaner --json output (preventing spinner progress from contaminating stderr when agents parse combined output), and telemetry reliability in firewalled networks. v1.3.1 is the second April release after v1.3.0’s April 11 feature drop (Junie/Lingma/ForgeCode/IBM Bob tool integrations) — confirming OpenSpec is running a point-release pattern where minor fixes land within two weeks of feature drops, rather than the “monthly cadence” assumption tracked through early April.

  • 2026-04-30-AI-Digest — No new release; v1.3.1 (April 21) remains latest as nine days have elapsed since the last release.

  • 2026-05-29-AI-Digest — Still unchanged on v1.3.1 (2026-04-21, now ~38 days old) — no new release this week. The cadence read has now firmly crossed from “normal envelope” into cooling: at ~38 days the gap is past the historical v1.2→v1.3 spacing, so the next tag is overdue rather than merely awaited.

  • 2026-06-02-AI-Digest — v1.4.0 “Kimi CLI, Mistral Vibe” ships 2026-06-01 ~21:27 UTC — the cadence-break recovery that prior digests had been flagging lands ~41 days after v1.3.1, closing the “firmly stale” gap. Two new agent integrations are skills-only: Kimi CLI (skills under .kimi/skills/) and Mistral Vibe (skills under .vibe/skills/). Sync skills are enabled by default in new installs — a behaviour change worth knowing before the next bootstrap. Requirement headers now parse case-insensitively (real footgun), and oh-my-zsh completion is fixed. The skills-only agent-integration pattern is now four integrations in two releases — the through-line.

  • 2026-06-04-AI-Digest — v1.4.1 “Update Fix” ships 2026-06-03 — a single-issue patch on the v1.4.0 release from June 1. Projects carrying their own workspace.yaml can run openspec update again — the v1.4.0 path broke this for Dagster-style workspace configs. Small patch, but it unblocks a real user-visible regression that hit anyone trying to update inside an existing monorepo workspace.

  • 2026-06-05-AI-Digest — Unchanged today; v1.4.1 “Update Fix” (2026-06-03) remains latest, the single-issue patch on v1.4.0 covered in 2026-06-04-AI-Digest. No new release in the last 24 hours.

  • 2026-06-06-AI-Digest — No new release. v1.4.1 “Update Fix” (2026-06-03), the workspace.yaml regression fix covered in 2026-06-05-AI-Digest, remains the current tag. Within the 7-day window but nothing new to add — cadence-watch only.

  • 2026-06-07-AI-Digest — No new release. v1.4.1 (2026-06-03) — the single-issue “Update Fix” patch that restored openspec update for projects carrying their own workspace.yaml (e.g. Dagster) — remains the latest. Quiet four days; nothing new to report against 2026-06-04-AI-Digest‘s coverage.

  • 2026-06-15-AI-Digest — No new release. OpenSpec v1.4.1 (2026-06-03) is now twelve days out. The Kimi CLI / Mistral Vibe skills-only support from v1.4.0 (2026-06-01) and the openspec update + workspace.yaml fix in v1.4.1 are unchanged. Already-reported across 2026-06-04-AI-Digest forward.

  • 2026-06-17-AI-Digest — No new release this week. v1.4.1 (June 3, “Update Fix”) remains the head — restored openspec update for projects with their own workspace.yaml and unblocked tools like Dagster. 14 days stale, and stable on its own terms.

  • 2026-06-29-AI-Digest — v1.5.0 “Stores Beta” shipped June 28 — first new OpenSpec tag since v1.4.1 on June 3, ending the 25-day silence flagged across 2026-06-26-AI-Digest, 2026-06-27-AI-Digest, and yesterday’s “drought now in its fifth week” line. The headline change is a new Stores surface, billed in the release notes as “a simpler way to organize specs and changes, replacing the workspace and initiative model” — the same workspace concept whose workspace.yaml regression triggered the v1.4.1 patch in early June. Worth carrying the release author’s own framing verbatim: Stores is “still rough — expect breaking changes while it stabilizes,” and the tag is gated on the very-early-beta flag rather than a stable cut. The narrow read: the cadence-break is real and the silence is over, but v1.5.0’s surface is explicitly a beta intended to replace the workspace and initiative model, not the polished v1.5.0 the 25-day gap was setting up. Two further changelog items: configuration values wrapped in JSON containers now parse correctly (silent corruption fix), and carriage returns in generated command descriptions are now escaped instead of written literally (CRLF authoring footgun). Three new contributors first-merged on this tag.

  • 2026-06-30-AI-Digest — v1.5.0 “Stores Beta” (June 28) remains the latest tag — no new release in the 48 hours since yesterday’s headline coverage. Carry the existing framing from 2026-06-29-AI-Digest: a beta-flagged surface replacing the workspace and initiative model, three first-time contributors merged on the tag, and the release author’s own “still rough” framing intact. already-reported: 2026-06-29-AI-Digest

  • 2026-07-05-AI-Digest — v1.5.0 “Stores Beta” (2026-06-28) remains the latest tag — no new release this week. Day seven since release with no v1.5.1 patch against the beta — the patch-cadence gap the corpus has been flagging since 2026-07-01-AI-Digest is now a full week wide. The “expect breaking changes” caveat that shipped with Stores Beta remains the only guidance for anyone integrating; if this stretches through next week the corpus will start reading it as a hold rather than a normal pause. already-reported: 2026-06-29-AI-Digest

  • 2026-07-10-AI-Digest — v1.6.0-beta.1 (2026-07-08) shipped — new minor bump, retiring the read the 2026-07-09-AI-Digest carried that the v1.5.1 gap looked like a hold on the Stores Beta. Fission-AI skipped the patch and shipped a beta minor instead, and the substance is a spec-traversal correctness fix rather than a Stores retreat: resolution convergence is now consistent across validate, view, and archive operations — the load-bearing line for anyone chaining OpenSpec into a build system. Stores also gets empty-store registration support, and the third-party adapter surface widens with Trae and Oh My Pi (OMP) additions. The line most likely to matter for Claude Code users: auto-approval for the OpenSpec CLI in generated skills, which drops the last confirmation step for OpenSpec-inside-Claude-Code workflows. Narrow read: the beta tag is itself the signal — Fission-AI wants field feedback on the resolution-convergence fix before promoting it to v1.6.0 stable. Structural read the corpus carries: the “hold” framing yesterday’s digest carried should be reframed as a maintainer-driven pause to bundle correctness plus adapter surface into one minor rather than shipping a Stores patch — not the same story.

  1. v1.6.0-beta.1 Ships Spec-Traversal Correctness + Adapter Surface (July 8, 2026): First new tag after 10 days on v1.5.0 — Fission-AI skipped a v1.5.1 patch on the Stores beta and shipped a v1.6.0-beta.1 minor instead. Substance: spec-traversal correctness fix (resolution convergence consistent across validate, view, archive), empty-store registration support, Trae + Oh My Pi (OMP) third-party adapters, and auto-approval for the OpenSpec CLI in generated skills — the line most likely to matter for Claude Code users. Beta tag is itself the signal: Fission-AI wants field feedback on the resolution-convergence fix before promoting to stable. The 2026-07-09-AI-Digest “hold on Stores Beta” framing reframes as a maintainer-driven pause to bundle correctness plus adapter surface into one minor — not a Stores retreat.
  • 2026-07-14-AI-Digest — v1.6.0 “OPSX Update, Tool Support” (2026-07-10) remains latest — day four post-promotion, no v1.6.1 patch. Consistent with the “beta held under field-testing” read the corpus has been carrying from prior digests. Prior tag in the window remains v1.6.0-beta.1 (2026-07-08). already-reported: 2026-07-11-AI-Digest
  • 2026-07-15-AI-Digest — v1.6.0 “OPSX Update, Tool Support” (2026-07-10) remains latest — day five post-promotion, no v1.6.1 patch. Consistent with the “beta held under field-testing” read the corpus has been carrying from prior digests. already-reported: 2026-07-14-AI-Digest
  • 2026-07-17-AI-Digest — v1.6.0 remains latest (2026-07-10), same as 2026-07-16-AI-Digest — day seven on the stable tag with no v1.6.1 hotfix. Digest framing: the beta-held-under-field-testing pattern flagged in 2026-07-12-AI-Digest continues cleanly. already-reported: 2026-07-11-AI-Digest
  • 2026-07-11-AI-Digest — v1.6.0 stable (2026-07-10) shipped, promoting yesterday’s v1.6.0-beta.1 with no beta.2 in between. The substance is the beta unchanged: /opsx:update ships as the revise-plan-without-implementing verb, Oh My Pi (OMP) and TRAE adapters widen the third-party surface (TRAE lands on top of yesterday’s Trae adapter — two distinct integrations, not a typo), archive safety and store-registration fixes carry over, and the resolution-convergence correctness fix across validate / view / archive is now the stable production line. Narrow read: Fission-AI took two days to promote beta.1 → stable with zero interim patch — the tightest beta cycle the corpus has logged for OpenSpec, and the confidence signal that the resolution-convergence fix held under beta field-testing. Structural read worth carrying: yesterday’s reframing of the v1.5.1 “hold” as a deliberate bundle rather than a Stores retreat now reads correctly against the promotion pace — Fission-AI held the patch, shipped a beta minor with the correctness fix bundled with the adapter widening, and promoted in forty-eight hours. That’s a coherent release-management posture, not a stall.
  1. v1.6.0 Stable Promoted from beta.1 in ~48 Hours (July 10, 2026): Fission-AI skipped beta.2 entirely and shipped stable — the tightest beta cycle the corpus has logged for OpenSpec. Substance carries forward from beta.1: /opsx:update revise-plan-without-implementing verb, OMP + TRAE adapters (distinct third-party integrations), archive-safety and store-registration fixes, resolution-convergence correctness across validate / view / archive now on the stable line. The “Stores Beta hold” framing retires: Fission-AI held the patch, shipped a beta minor with correctness + adapter widening bundled, and promoted in forty-eight hours — coherent release-management posture, not a stall. Confidence signal that the resolution-convergence fix held under beta field-testing.

Version Status

  • Current version - v1.5.0 “Stores Beta” (June 28, 2026)
  • Previous versions - v1.4.1 (June 3, 2026), v1.4.0 (June 1, 2026), v1.3.1 (April 21, 2026), v1.3.0 (April 11, 2026), v1.2.0 (February 2026)
  • Status - Beta cut after 25-day silence — Stores surface flagged “still rough” by the release notes themselves

Key Developments

  1. v1.5.0 “Stores Beta” Ends the 25-Day Silence (June 28, 2026): First new tag since v1.4.1 on June 3, ending the 25-day gap the corpus had been tracking as a “drought.” Headline change is the new Stores surface — “a simpler way to organize specs and changes, replacing the workspace and initiative model” — flagged by the release author as “still rough — expect breaking changes while it stabilizes.” Two corruption-class fixes ride along: JSON-wrapped configuration values now parse correctly, and CRLF carriage returns in generated command descriptions are now escaped. Three new contributors first-merged on this tag. The disciplined corpus read: cadence-break is real and silence is over, but the v1.5.0 surface is explicitly a beta intended to replace workspace-and-initiative, not the polished v1.5.0 the gap was setting up — for a small OSS side-project, 25 days is past the comfortable cadence envelope but well inside the small-OSS base rate for between-feature gaps.

Development Pattern

OpenSpec demonstrates a different development pattern compared to Beads:

  • Stability-focused - No rapid iteration or minor version bumps
  • Feature-complete - Suggests v1.2.0 meets project goals
  • Maintenance mode - Possible transition to maintenance after completion

Project Context

OpenSpec is maintained by Fission AI and serves as one of three primary repositories monitored for developments in the AI/developer tools ecosystem alongside Beads and other tracked projects.

Repository Status

OpenSpec remains available as an open-source project with development tracking through the AI Digest monitoring system.

Timeline (continued)

  • 2026-07-29-AI-Digest — v1.7.0 “New tools, smarter updates” landed 2026-07-29, ending a 19-day gap since v1.6.0 (2026-07-10). Four moves worth naming: (1) Auto-update via npm poll — CLI now checks the registry and offers upgrade in place, removing the “am I on latest?” friction that had been a recurring paper-cut in the v1.6.x line. (2) Five new tool integrations — ZCode, Hermes Agent, CodeArts Agent, Kimi Code, and Codex (skills-only mode); generated content now matches each tool’s command-naming convention rather than a single OpenSpec default. The Codex skills-only carve-out is the notable one — first-class acknowledgement that Codex’s slash-command surface differs enough from Claude Code / Cursor that a full integration doesn’t map. (3) skip_specs: true flag + machine-wide default store — openspec config set defaultStore <id> lets a machine pick a store without per-repo config; skip_specs: true lets pure refactors bypass validation/archive. Both read as OpenSpec’s team responding to user reports, not roadmap-driven feature adds. (4) First-class nested specs/<area>/<capability>/spec.md layout — the biggest structural change; prior nesting was tolerated but not idiomatic, this makes it the recommended shape for larger codebases. Plus footprint reduction, shell-completion fixes (fish, PowerShell, Oh My Zsh), Windows input responsiveness, and UTF-8 BOM handling. Pattern to name: v1.7.0 is the “quality-of-life follow-through” release after the v1.6.x line’s structural additions — auto-update, better nesting ergonomics, per-tool naming, and skip-flags for pure refactors are all workflow smoothings, not new abstractions. Consistent with the earlier read that OpenSpec is deliberately keeping its surface area small.

Key Developments (continued)

  1. v1.7.0 “New Tools, Smarter Updates” Ends 19-Day Gap With Quality-of-Life Follow-Through (July 29, 2026): First OpenSpec tag since v1.6.0 (Jul 10), ending a 19-day gap. Auto-update via npm poll removes “am I on latest?” friction. Five new tool integrations — ZCode, Hermes Agent, CodeArts Agent, Kimi Code, Codex (skills-only) — with generated content matching each tool’s command-naming convention rather than a single OpenSpec default; the Codex skills-only carve-out is the notable one. skip_specs: true + machine-wide defaultStore are user-report-driven friction removals rather than roadmap features. First-class nested specs/<area>/<capability>/spec.md layout is the biggest structural change — makes prior tolerated nesting the recommended shape for larger codebases. Plus shell-completion, Windows input, and UTF-8 BOM fixes. Pattern to name: “quality-of-life follow-through” release after the v1.6.x line’s structural additions — workflow smoothings, not new abstractions. Reads on the same day OpenAI‘s Codex Security repo lit the HN front page (425 pts) as the same “coding-agent surface area is finally getting formalised” beat from two different angles.

  • 2026-08-02-AI-Digest — No new tag since v1.7.0 “New tools, smarter updates” (2026-07-29 01:31 UTC) — 4 days, the 90-PR, 19-contributor release covered in full on Wednesday: npm-registry auto-update, skip_specs: true refactor flag, machine-wide openspec config set defaultStore, five new tool integrations (ZCode, Hermes Agent, CodeArts Agent, Kimi Code, Codex skills-only), first-class nested specs/<area>/<capability>/spec.md, fish/PowerShell/Zsh completions, ~160-package footprint reduction. already-reported: 2026-07-30-AI-Digest. Cadence framing: 4 days post-v1.7.0 sits well inside the standard post-feature-drop soak envelope; the digest logs the concurrent toolchain-wide silence today (Claude Code day 8 on v2.1.220, Beads day 7 on v1.1.2) as the simultaneity being the signal, not the individual repo cadences.

  • 2026-08-06-AI-Digest — v1.8.0 “More agents, sturdier archives” shipped 2026-08-05 — the release landed after yesterday’s digest closed, so today is first coverage. Load-bearing: (1) Four new agent targets — vendor-neutral generic agents, MiniMax Code, Atlassian Rovo Dev CLI, and GitHub Copilot cloud agent (opt-in). Extends the tool-integration surface v1.7.0’s ZCode / Hermes Agent / CodeArts Agent / Kimi Code / Codex-skills-only pass pushed forward, dropping in the second-tier coding agents that shipped through July. (2) “Archive that talks back” — improved error messaging for non-terminal environments; validation now catches scenario loss early during authoring rather than at archive time. Continues the archive-safety thread from v1.6.0. (3) Sub-tasks count toward progress tracking, closing a completion-accounting gap that recurred in issues after the v1.5.0 Stores beta. (4) Telemetry now respects user configuration settings — first explicit user-consent-honoring change in the v1.x line. Cadence framing: v1.8.0 lands 7 days after v1.7.0, well inside the sub-1.5-week post-feature-drop envelope; the four-new-agent-target ship is the operationally larger of the two, and the vendor-neutral generic-agent target is worth naming separately as the escape valve for tools OpenSpec hasn’t shipped a first-class integration for yet.

  1. v1.8.0 “More Agents, Sturdier Archives” — Four New Agent Targets (MiniMax Code, Atlassian Rovo Dev CLI, Vendor-Neutral Generic, GitHub Copilot Cloud Agent) + User-Consented Telemetry (August 5, 2026): First OpenSpec tag since v1.7.0 (Jul 29), ending a 7-day gap. Four new agent integrations — vendor-neutral generic agents (the escape valve for tools without first-class support), MiniMax Code, Atlassian Rovo Dev CLI, and GitHub Copilot cloud agent (opt-in). Extends the v1.7.0 ZCode / Hermes / CodeArts / Kimi Code / Codex-skills-only integration pass with the second-tier coding agents that shipped through July. “Archive that talks back” improves error messaging for non-terminal environments and moves scenario-loss validation from archive-time to authoring-time — continues the archive-safety thread from v1.6.0. Sub-tasks count toward progress tracking closes a completion-accounting gap that recurred in issues after the v1.5.0 Stores beta. Telemetry now respects user configuration settings is the first explicit user-consent-honoring change in the v1.x line. Pattern to name: v1.8.0 continues the tool-integration + operational-hygiene cadence Fission-AI has been running through v1.6.x / v1.7.0 — no new abstractions, but a widened tool surface and a clean archive-safety + telemetry-consent pair. Covered in 2026-08-06-AI-Digest.
  • 2026-08-27-AI-Digest — v1.11.0 “Spec Diffs & Batch Status” ships 2026-08-26 (release notes) — first feature release since v1.10.0 on 2026-08-19; a week is well inside normal OSS variance and this doesn’t call for a “re-engagement” narrative. Load-bearing items: --diff on the change/spec view for precise per-requirement diffs; --all for checking every active change in one pass; Explore mode now requires confirmation before writing files (guards against openspec explore scaffolding into a live repo); fish shell completions improved; archive path fixed to preserve requirement ordering during renames (previously reshuffled on archive). Narrow read the digest carries: the --diff / --all pair is the substantive lift; the rest is polish — practitioners running specs across a multi-change branch finally have batch-status visibility without shelling out to jq. Cadence framing: v1.11.0 lands 7 days after v1.10.0, well inside the sub-1.5-week post-feature-drop envelope; extends the v1.8.0 / v1.10.0 widened-tool-surface arc with the first visibility-tooling ship on the change/spec pipeline itself.
  1. v1.11.0 “Spec Diffs & Batch Status” — --diff for Per-Requirement Diffs + --all for Batch Change-Check + Explore-Mode Confirmation-Gate + Archive Ordering Fix (August 26, 2026): First OpenSpec tag since v1.10.0 (Aug 19), ending a 7-day gap that reads as normal OSS variance rather than a re-engagement narrative. --diff on the change/spec view brings per-requirement diff visibility to the CLI; --all for checking every active change in one pass closes the last batch-status visibility gap in the workspace flow. Explore mode requires confirmation before writing files — guards against openspec explore scaffolding into a live repo (safety-hardening on the same axis as the v1.6.0 archive-safety thread). Fish completions improved, and the archive path fix preserves requirement ordering during renames (a regression that had been reshuffling requirements on archive). Pattern to name: the --diff / --all pair is the substantive lift, the rest is polish — visibility tooling on the change/spec pipeline itself finally lands, and multi-change branch practitioners can retire the jq-shell workaround. Covered in 2026-08-27-AI-Digest.

  • 2026-09-04-AI-Digest — OpenSpec v1.12.0 — “Findings Reports, SourceCraft” (2026-09-03) — already-reported: 2026-09-03-AI-Digest, covered in depth as yesterday’s load-bearing OpenSpec beat. No new cut in the last 24 hours. The validate --report findings view and the SourceCraft VS Code integration are the two pieces of the release still worth carrying forward as the durable read: multi-agent-frontend support is the thesis, not any single IDE.

  • 2026-09-03-AI-Digest — v1.12.0 “Findings Reports, SourceCraft” — published Sep 3 (today). Two moves that matter together. First, openspec validate --report findings narrows the validation view to errors and warnings only, maturing the visibility-tooling arc that --diff / --all opened in v1.11.0. Second and more structurally interesting, SourceCraft Code Assistant support ships — a new agent surface for OpenSpec-driven project skills and commands, joining the existing Claude Code / Cursor / Copilot integrations. Also adds code-grounded planning (the agent now inspects relevant code, tests, and docs before drafting a change) and reliability polish for init on Git-tracked repos. Structural read the corpus carries: SourceCraft is a new agent front-end for the same OpenSpec substrate; multi-agent-frontend support is the durable OpenSpec thesis, not any single IDE integration. Log against MOC - Developer Tools and MOC - Agentic Coding.

  1. v1.12.0 “Findings Reports, SourceCraft” — openspec validate --report findings + SourceCraft Code Assistant Integration + Code-Grounded Planning (September 3, 2026): OpenSpec’s Sep 3 cut bundles a visibility-tooling narrowing (--report findings shows only errors and warnings, extending the --diff / --all arc from v1.11.0) with a new agent front-end integration (SourceCraft Code Assistant joins Claude Code / Cursor / Copilot). Code-grounded planning is the third named change — the agent now inspects code, tests, and docs before drafting a change. Load-bearing structural framing to carry: SourceCraft is a new agent front-end for the same OpenSpec substrate; the durable thesis is multi-agent-frontend support, not any single IDE integration. Extends the v1.7.0 / v1.8.0 widened-tool-surface arc onto a first-class agent front-end that isn’t an established IDE product. Covered in 2026-09-03-AI-Digest.
  • 2026-09-10-AI-Digest — v1.13.0 “Apply warnings, safer archives” (2026-09-09) — supersedes v1.12.0 after six days. Three substantive changes: openspec apply now flags a change with no delta specs and suggests either writing specs or declaring skip_specs: true, closing the “silently-applied change without spec deltas” hole that had been the load-bearing gap in the findings-report line. Archive no longer quietly edits fenced code blocks that contain blank lines — the archive step was mid-editing user content in the name of formatting normalisation, and now leaves fenced code alone. Removals/renames written with alternate bullet syntax now actually take effect, and multiple delta sections in one change all apply instead of only the first — both silent-drop bugs that would have looked like a spec-authoring mistake rather than a tooling one. Reframe worth carrying: the release closes three silent-mutation and silent-drop bugs, not polish release. Log against MOC - Developer Tools and MOC - Agentic Coding.
  1. v1.13.0 “Apply Warnings, Safer Archives” Closes Three Silent-Mutation / Silent-Drop Bugs (September 9, 2026): OpenSpec’s Sep 9 cut supersedes v1.12.0 after six days. Three substantive changes worth naming separately: (1) openspec apply now flags a change with no delta specs and suggests either writing specs or declaring skip_specs: true — closes the “silently-applied change without spec deltas” hole in the findings-report line the v1.12.0 validate --report findings visibility arc had left open; (2) archive no longer edits fenced code blocks with blank lines during formatting normalisation — the archive step was silently rewriting user content and now leaves fenced code alone; (3) removals/renames written with alternate bullet syntax now actually take effect, and multiple delta sections in one change all apply rather than only the first — both silent-drop bugs that would have read as spec-authoring mistakes rather than tooling bugs. Load-bearing framing to carry: the release closes three silent-mutation and silent-drop bugs, not a polish release. Pattern to name: v1.13.0 extends the visibility-and-safety arc that ran through v1.11.0 (--diff / --all visibility) and v1.12.0 (--report findings filter) — where prior visibility-tooling releases exposed problems, this release fixes the mutation-side problems the visibility passes surfaced. Covered in 2026-09-10-AI-Digest.

  • 2026-09-11-AI-Digest — No new release since v1.13.0 (2026-09-09) — already-reported: 2026-09-10-AI-Digest. Stable line remains v1.13.0; the “Apply warnings, safer archives” release still holds. Watch clause carries: whether the archive-safety and delta-application fixes hold once the wider install base exercises the corner cases they closed.

  • 2026-09-17-AI-Digest — v1.13.1 “Hardened CLI, safer archives” (2026-09-17, 01:11 UTC) — the security-hardening pass on freshly-cloned repos that the community had been asking for. Repo config files can no longer inject directives into agent instructions; malicious files can’t hang openspec update / openspec archive; .npmrc files can’t redirect update checks. Directly addresses the practitioner-facing “can I trust openspec init in an unreviewed repo” question, a real gap after the v1.13.0 cut (2026-09-10-AI-Digest). Workflow ergonomics also move: openspec status now prints a Next: line with the exact resume command; generated skills match natural phrasings like "openspec propose" / "do an openspec apply"; workflows verify openspec init has run before writing. Archive validation catches case-sensitive name conflicts and unpaired rename sections; task counters recognize +, 1., 1) list markers; openspec store remove guards against nested-store deletion; editor commands with args (e.g., code --wait) work; DO_NOT_TRACK=true disables telemetry; the Nix flake now ships bash/zsh/fish completions. Pattern to name: v1.13.1 closes the trust-boundary holes on top of v1.13.0’s silent-mutation/silent-drop fixes — the visibility-and-safety arc extends into an untrusted-repo-input threat model.

  • 2026-09-24-AI-Digest — v1.13.2 (2026-09-23) — correctness + Windows-hygiene point release, one week after the v1.13.1 security-hardening line. verify reporting fix — no longer counts skipped checks as passing; handles requirement changes correctly on the CI-facing surface, closing a regression that would have quietly passed builds missing coverage. Windows archive reliability — archive on Windows no longer leaves .openspec-archive.lock behind or rolls back mid-run; line endings preserved when rewriting spec files; archive task warnings use schema-aware progress tracking. Task/workflow guidance — task guidance folds tests and documentation updates into each task group; scenario-loss messages name what blocks contribute; approval prompts only ask when context is critically unclear; clearer setup hints for Codex CLI, IDE, and Desktop app users. Artifact + tool plumbing — brace-expansion patterns in artifact outputs resolve correctly; update can fill missing files under partially written glob artifacts; Kilo Code commands generate in the right directories; Codex update exits with proper status codes; non-English Purpose fields validate. Same-day compound with Claude Code v2.1.281 — both projects shipped hardening-track releases on the same UTC date, closing footguns rather than shipping features. Log against MOC - Developer Tools and MOC - Agentic Coding.

  1. v1.13.2 — Verify Reporting Fix + Windows Archive Reliability + Task/Workflow Guidance Tightening (September 23, 2026): OpenSpec’s Sep 23 cut closes correctness and Windows-hygiene gaps a week after the v1.13.1 security-hardening line. verify no longer counts skipped checks as passing and handles requirement changes on the CI-facing surface — closes a regression that could have quietly passed builds missing coverage. Windows archive reliability — no orphaned .openspec-archive.lock files, no mid-run rollback, preserved line endings on spec-file rewrites, schema-aware progress on archive-task warnings. Task/workflow guidance — tests and docs folded into each task group; scenario-loss messages name what blocks contribute; approval prompts only when context is critically unclear. Artifact + tool plumbing — brace-expansion patterns resolve, update fills partially-written glob artifacts, Kilo Code commands generate in correct directories, Codex update exits with correct status codes, non-English Purpose fields validate. Load-bearing compound framing to carry: both Claude Code v2.1.281 and OpenSpec v1.13.2 shipped hardening-track releases on the same UTC date — both projects now spending release cadence on reliability of the automated loop, not new capabilities on top of it. Covered in 2026-09-24-AI-Digest.
  • 2026-10-01-AI-Digest — v1.14.0 (2026-09-30) breaks the 7-day quiet period since v1.13.2 (2026-09-23) with a minor-version bump rather than a patch — the quiet week ended with a feature cut, not a hotfix. (1) Ten new coding-tool integrations in a single release: Amp, AtomCode, Code Studio, DeepSeek Harness, EasyCode, GigaCode, Grok Build, GSD, Veai, and Warp — the integration list is wider than any single prior OpenSpec release. (2) openspec list --archived surfaces archived changes; a new workflow-status view exposes schema + artifact completion states inline. (3) New openspec version command with structured output; Nix flake exposes OpenSpec via overlays.default. (4) Fixes: store-backed apply operations, apply task updates with precise file locations, archive reliability after failed syncs, zsh completion restoration. Pattern worth noting: the Fission-AI team used the quiet week to ship integration breadth, not core workflow changes. If the goal is tool-coverage parity across the agentic-coding stack, this is the shape it takes. Log against MOC - Developer Tools and MOC - Agentic Coding.
  1. v1.14.0 “Ten New Coding-Tool Integrations” (Amp, AtomCode, Code Studio, DeepSeek Harness, EasyCode, GigaCode, Grok Build, GSD, Veai, Warp) + --archived List + Workflow-Status View + openspec version Command + Nix Flake (September 30, 2026): First OpenSpec tag since v1.13.2 (Sep 23), ending a 7-day gap with a minor-version bump rather than a patch — the quiet week ended with a feature cut, not a hotfix. Ten new coding-tool integrations in a single release — the integration list is wider than any single prior OpenSpec release, and includes DeepSeek Harness (ecosystem acknowledgement of the MIT-licensed Claude Code rival). openspec list --archived surfaces archived changes; new workflow-status view exposes schema + artifact completion states inline; new openspec version command with structured output; Nix flake exposes OpenSpec via overlays.default. Fixes: store-backed apply operations, apply task updates with precise file locations, archive reliability after failed syncs, zsh completion restoration. Load-bearing framing to carry: Fission-AI used the quiet week to ship integration breadth, not core workflow changes — if the goal is tool-coverage parity across the agentic-coding stack, this is the shape it takes. Covered in 2026-10-01-AI-Digest.
  • 2026-10-06-AI-Digest — v1.14.1 (2026-10-06) “Faster startup, cleaner view” — the first cut after the v1.14.0 ten-integration feature expansion is cold-start / UX polish, not a regression patch. CLI now loads 24 modules instead of 485 on startup — a ~20× reduction in cold-start module count. Archived changes removed from the default dashboard view (still accessible via openspec list --archived). Incremental spec-file generation now shows progress during writes; archive-cleanup error reporting improved. Load-bearing framing to carry: this resolves the v1.14.0 patch-watch flagged in 2026-10-05-AI-Digest as cold-start / UX polish, not a regression patch for the ten-integration surface — the ten-new-integration surface shipped in v1.14.0 is holding. Log against MOC - Developer Tools and MOC - Agentic Coding.
  1. v1.14.1 “Faster Startup, Cleaner View” — 24 Modules Loaded vs 485 (~20× Cold-Start Reduction) + Archived Changes Off Default Dashboard + Incremental Spec-File Progress + Archive-Cleanup Error Reporting (October 6, 2026): v1.14.1 (2026-10-06) is the first cut after v1.14.0’s ten-integration feature expansion and is cold-start / UX polish, not a regression patch for the ten-integration surface — a ~20× reduction in startup module count (485 → 24), archived changes removed from the default dashboard (still available via openspec list --archived), progress during incremental spec-file writes, and improved archive-cleanup error reporting. Load-bearing framing to carry: the v1.14.0 ten-new-integration surface is holding — the patch-watch flagged in 2026-10-05-AI-Digest resolves on the UX-polish axis rather than requiring a hotfix on any of the ten integrations. Covered in 2026-10-06-AI-Digest.
  • 2026-10-15-AI-Digest — v1.14.2 shipped today, 2026-10-15 — Fission-AI’s first cut since v1.14.1 on 2026-10-06 (already-reported: 2026-10-14-AI-Digest for the “no new release this week” status that stood in yesterday’s digest). Features: top-level x- keys in .openspec.yaml are now ignored by OpenSpec, so tracker IDs / owner fields don’t fail validate --strict. Improvements: faster Tab completion; warnings when delta specs contain content archive won’t carry into the main spec; verify checks removed requirements against their original text. Fixes: archive accepts symlinked openspec/ directories; explore no longer suggests default-schema files a custom schema doesn’t define; update handles partly-written glob artifacts; deeply-nested brace patterns are rejected with a clear error. Breaking: none listed. Load-bearing softener: the x- escape hatch is a small-but-real concession that OpenSpec’s .openspec.yaml is becoming a shared surface across tooling (trackers, PM systems) rather than a Fission-AI-only artifact. Log against MOC - Developer Tools and MOC - Agentic Coding.
  1. v1.14.2 Ends the “No Release This Week” Streak With Top-Level x- Key Tolerance + Faster Tab Completion + Delta-Spec Warnings + Archive Symlink Support (October 15, 2026): v1.14.2 (2026-10-15) is Fission-AI’s first cut since v1.14.1 on 2026-10-06 — ending the “no new release this week” status that stood in yesterday’s digest. Top-level x- keys in .openspec.yaml are now ignored so tracker IDs / owner fields don’t fail validate --strict — the small-but-real concession that OpenSpec’s config is becoming a shared surface across tooling (trackers, PM systems) rather than a Fission-AI-only artifact. Faster Tab completion, warnings when delta specs contain content archive won’t carry into the main spec, verify checks removed requirements against their original text. Archive accepts symlinked openspec/ directories (new); explore no longer suggests default-schema files a custom schema doesn’t define; update handles partly-written glob artifacts; deeply-nested brace patterns rejected with a clear error. No breaking changes listed. Covered in 2026-10-15-AI-Digest.

  • 2026-10-16-AI-Digest — v1.14.2 (2026-10-15, “Extension metadata, faster completion”) — no new release since yesterday’s digest. Features recap: top-level x- keys in .openspec.yaml ignored (strict-validate escape hatch for trackers/PM systems), faster Tab completion, validate/archive warn on delta content that won’t carry into main spec, verify reads removed-requirement original text. already-reported: 2026-10-15-AI-Digest (cross-ref only; no fresh beat). Log against MOC - Developer Tools and MOC - Agentic Coding.

  • 2026-10-17-AI-Digest — v1.14.3 — “Linked specs, safer globs” — shipped today (2026-10-17) by openspec-release-bot, two days after v1.14.2. Headline items: symlinked specs — a capability’s spec.md may now be a symlink, provided it resolves inside the project (enables sandbox-safe cross-project sharing without the “spec is a copy, drift begins” tax); supply-chain cleanup — the unpatched braces dependency is removed, clearing GHSA-vfj7-8cjw-p6xm so npm audit no longer flags OpenSpec through that chain; hang fix + DoS guardrail — validate --all no longer hangs in pre-commit hooks, and brace patterns that expand past 1,024 paths are rejected outright. Reframe worth carrying: the agentic-coding infra is quietly moving toward safer defaults one knob at a time — the 1,024-path glob expansion cap and the GHSA-vfj7-8cjw-p6xm supply-chain cleanup are the fresh signals, with symlinked specs as the cross-project-sharing surface, not a feature-breadth cut like v1.14.0. Pairs same-day with Claude Code v2.1.302’s default-perm-mode fix for third-party providers as this cycle’s compound “safer defaults” beat across both projects. Log against MOC - Developer Tools, MOC - Agentic Coding, and MOC - Agent Security.

  • 2026-10-23-AI-Digest — No new release this week. v1.14.3 (2026-10-17) remains the head — six-day quiet, extending yesterday’s “five-day quiet” by one. already-reported: 2026-10-22-AI-Digest. The safer-defaults framing from the v1.14.3 cut (1,024-path glob cap, GHSA-vfj7-8cjw-p6xm supply-chain cleanup, symlinked specs) is unchanged; nothing new on the tag side today. Log against MOC - Developer Tools and MOC - Agentic Coding.

  • 2026-10-24-AI-Digest — OpenSpec shipped v1.15.0 (2026-10-24), breaking the seven-day quiet after v1.14.3 (2026-10-17). The minor-version bump (1.14 → 1.15) carries the distribution-posture shift behind it. (1) Install without Node.js. Standalone binaries for macOS, Linux (glibc + musl), and Windows on x64 and arm64. First time OpenSpec can ship into a sandbox that doesn’t have Node already — matters for CI runners, build containers, and the growing set of agent harnesses that treat Node as an opt-in dependency. (2) openspec update --dry-run previews file adds/changes/deletes without writing; --json gives machine-readable output. Several --json commands start faster. (3) Fixes: openspec new change reports the schema it actually uses; /opsx:verify matches REMOVED requirements by exact name; openspec feedback form matches the bug form. What’s new in posture: the no-Node install path is the first real move toward “OpenSpec as a system binary” rather than “OpenSpec as an npm package” — a minor bump is the standard way to flag that; expect a handful of CI / container recipes to shift over the next month. Log against MOC - Developer Tools and MOC - Agentic Coding.