Skip to content

v1.8.0 - More agents, sturdier archives

Latest

Choose a tag to compare

@clay-good clay-good released this 05 Aug 21:10
d578896

What's New in v1.8.0

Thirty-four merged PRs from fifteen contributors. More agents pull up a chair, archive learns to use its words, and validate starts catching problems while you can still fix them cheaply.

New

  • Three more agent targets - The vendor-neutral agents (writes skills to the shared .agents/skills/ that AGENTS.md-aware assistants read), MiniMax Code, and Atlassian's Rovo Dev CLI. openspec init --tools agents and you're set.
  • GitHub Copilot cloud agent, opt-in - openspec init can generate Copilot coding-agent files for you. It asks first and defaults to No, so nothing lands in .github/ unless you say yes.
  • Retire a capability on archive - A change that declares retire_capabilities: true can remove a capability's last requirement and cleanly delete its spec, instead of hitting a wall at archive time.

Improved

  • Archive that talks back - Run openspec archive with no terminal (an agent, a CI job) and it now names the exact flag it needs and hands you a paste-ready rerun, instead of dying on a cryptic prompt error.
  • validate catches scenario loss early - A MODIFIED requirement that would drop a scenario now fails at authoring time, naming the scenarios to copy back, instead of ambushing you at archive.
  • Sub-tasks finally count - Nested checkboxes in tasks.md count toward progress, so "✓ Complete" actually means complete.
  • Telemetry honors your config - telemetry.enabled: false turns off anonymous telemetry and update checks. Env and CI opt-outs still win.
  • Sharper agent workflows - Propose stays focused on planning and hands off cleanly to apply, explore scaffolds a real change before writing to it, and nested specs/<area>/<capability>/ paths are preserved end to end.

Fixed

  • Stops eating its own commands - init and update no longer delete the CoStrict and Junie command files they just generated.
  • Non-English specs validate - SHALL/MUST is treated as guidance in normal mode, so requirements in other languages pass. Strict mode still enforces it.
  • Your notes stay put - Archive warns before a merge would drop a note tucked under a requirement, and generated files stay inside their boundaries without breaking linked monorepos.

New Contributors

Full Changelog: v1.7.0...v1.8.0