Skip to content

v1.10.0 - Zed support, quieter installs

Latest

Choose a tag to compare

@clay-good clay-good released this 19 Aug 22:33
1ebddd1

What's New in v1.10.0

Zed joins the supported tools, init speaks your language, and installing OpenSpec no longer trips npm's alarm.

New

  • Zed Agent - openspec init --tools zed installs the workflow skills into .agents/skills/, where Zed's built-in Agent finds them. Skills-only, so they're invoked as /openspec-propose. Requires Zed v1.4.2 or newer.
  • Non-English artifacts - openspec init --language <language> sets the language for generated artifacts without hand-editing config.yaml. OpenSpec headings and SHALL/MUST stay in English, so your specs still validate.

Improved

  • Installing - the published package now declares no install scripts at all, so npm install -g @fission-ai/openspec no longer emits the allow-scripts warning that read like a packaging fault (and whose suggested fix, npm approve-scripts, never worked for a global install anyway). The shell-completions tip now comes from the CLI itself: once, on stderr, and only when there's a human there to read it.
  • Task plans - generated tasks now have to say how you'd know they're done, whether that's a test, a command, an observable result, or a delivered artifact. "Implement the thing" no longer passes for a plan.
  • Prompts - the multi-select picker now shows the full key help from the prompt library, so navigation, select-all and invert are discoverable instead of folklore.

Fixed

  • Feedback - openspec feedback used your entire report as the issue title and left the body with nothing but metadata. Reports now keep their text, and titles stay a readable length.
  • Archive - retiring a capability could dead-end on Spec must have at least one requirement with no guidance at all, when the spec also held content the merge couldn't account for. The abort now names exactly what's in the way.
  • Stores - the specs instruction read main specs from a path relative to your working directory. Under a store that missed the spec entirely, or, worse, quietly returned a different capability that happened to share the name.
  • Profiles - a custom profile could select archive without sync, leaving the archive workflow calling a workflow that was never installed.
  • OpenCode - /opsx-propose add-auth dropped add-auth before the workflow ever saw it.
  • Schemas with no specs artifact - changes created under one failed validation immediately, demanding a delta that schema could never produce.
  • Output hygiene - the first-run telemetry notice went to stdout, so openspec spec show auth > auth.md wrote the notice into the file ahead of the spec. It goes to stderr now.
  • openspec update - stopped advising Claude Code, Codex and other CLI tools to restart an IDE they don't have.

New Contributors

Full Changelog: v1.9.0...v1.10.0