Skip to content

Releases: Fission-AI/OpenSpec

v1.3.1 - Path & Telemetry Fixes

21 Apr 16:18
3c7a05c

Choose a tag to compare

What's New in v1.3.1

A batch of path resolution and telemetry reliability fixes for workflow artifacts, validation, and locked-down networks.

Fixed

  • Canonical artifact paths - Workflow artifact paths now resolve through the native realpath, so symlinks and case-insensitive filesystems no longer cause mismatches during apply and archive.
  • Glob artifact outputs - Apply instructions with glob artifact outputs resolve correctly. Literal outputs are enforced as file paths.
  • Hidden spec requirements - Validation now detects requirements nested inside fenced code blocks or otherwise hidden in main specs.
  • Clean --json output - Spinner progress no longer leaks into stderr when --json is passed, so agents parsing combined stdout/stderr get clean JSON.
  • Silent telemetry in firewalled networks - PostHog errors are swallowed with a 1s timeout and retries/remote config disabled, so PostHogFetchNetworkError no longer appears in locked-down environments. Telemetry opt-out is documented earlier in the README, install guide, and CLI reference.
  • Telemetry config on XDG and Windows - Honors XDG_CONFIG_HOME on Linux and %APPDATA% on Windows when locating the telemetry config file.
  • Glob-special characters in paths - Directory paths containing glob metacharacters are now escaped before matching.

New Contributors

Full Changelog: v1.3.0...v1.3.1

v1.3.0 - New Tool Integrations

11 Apr 15:47
9b5007d

Choose a tag to compare

What's New in v1.3.0

New tool integrations plus targeted fixes for OpenCode, Copilot, and pi.dev.

New

  • Junie support - Generate tool and command files for JetBrains Junie.
  • Lingma IDE support - Configuration support for Lingma IDE.
  • ForgeCode support - Tool support for ForgeCode.
  • IBM Bob support - Tool support for IBM Bob coding assistant.

Fixed

  • OpenCode directory - OpenCode adapter now uses .opencode/commands/ (plural) to match OpenCode's official convention.
  • openspec status with no changes - Exits gracefully instead of throwing when no changes exist.
  • Copilot auto-detection - No longer triggers from a bare .github/ directory with no Copilot config.
  • pi.dev command generation - Command reference transforms and template argument passing now work correctly.
  • Shell completions opt-in - Completion install is now opt-in, avoiding PowerShell encoding corruption.

New Contributors

Full Changelog: v1.2.0...v1.3.0

v1.2.0 - Profiles, Pi & Kiro Support

23 Feb 23:43
6a3a126

Choose a tag to compare

What's New in v1.2.0

Control what gets installed with profiles, create complete change proposals in one step, and use OpenSpec with two new coding agents.

New

  • Profiles — Choose between core (4 essential workflows) and custom (pick any subset) to control which skills get installed. Manage with openspec config profile.
  • Propose workflow — Create a complete change proposal with design, specs, and tasks from a single request — no need to run new then ff separately.
  • Pi support — Pi (pi.dev) coding agent is now a supported tool with prompt and skill generation.
  • Kiro support — AWS Kiro IDE is now a supported tool with prompt and skill generation.
  • AI tool auto-detectionopenspec init scans your project for existing tool directories (.claude/, .cursor/, etc.) and pre-selects detected tools.

Improved

  • Sync prunes deselected workflowsopenspec update now removes command files and skill directories for workflows you've deselected, keeping your project clean.
  • Config drift warningopenspec config list warns when global config is out of sync with the current project.

Fixed

  • Onboard preflight no longer gives a false "not initialized" error on freshly initialized projects
  • Archive workflow no longer stops mid-way when syncing — it properly resumes after sync completes
  • Added Windows PowerShell alternatives for onboard shell commands

New Contributors

Full Changelog: v1.1.1...v1.2.0

v1.1.1 - OpenCode Command Fix

30 Jan 22:56
36fbc89

Choose a tag to compare

What's New in v1.1.1

A quick patch to fix OpenCode command references.

Fixed

  • OpenCode command references - Generated files now use the correct /opsx- hyphen format instead of /opsx: colon format, so commands work properly in OpenCode

New Contributors

Full Changelog: v1.1.0...v1.1.1

v1.1.0 - Cross-Platform Fixes, Nix Improvements

30 Jan 10:28
3768694

Choose a tag to compare

What's New in v1.1.0

A stability release focused on fixing cross-platform path issues and improving the Nix build experience.

Fixed

  • Codex global paths - Codex adapter now resolves global paths correctly, fixing workflow file generation when run outside the project directory
  • Archive on networked/external drives - Archive falls back to copy+remove when rename fails with EPERM or EXDEV errors
  • Windsurf workflow path - Updated Windsurf adapter to use the correct workflows directory instead of the legacy commands path
  • Slash command hints - Workflow completion messages now display helpful slash command hints for next steps

Improved

  • Nix flake - Version now read dynamically from package.json; source filtering excludes node_modules for faster builds
  • Nix CI - Updated to latest nix-installer and magic-nix-cache actions

New Contributors

v1.0.2

27 Jan 03:34
f6b415c

Choose a tag to compare

Patch Changes

  • #596 e91568d Thanks @TabishB! - ### Bug Fixes

    • Clarified spec naming convention — Specs should be named after capabilities (specs/<capability>/spec.md), not changes
    • Fixed task checkbox format guidance — Tasks now clearly require - [ ] checkbox format for apply phase tracking

v1.0.1

26 Jan 10:52
d155126

Choose a tag to compare

Patch Changes

  • #587 943e0d4 Thanks @TabishB! - ### Bug Fixes

    • Fixed incorrect archive path in onboarding documentation — the template now shows the correct path openspec/changes/archive/YYYY-MM-DD-<name>/ instead of the incorrect openspec/archive/YYYY-MM-DD--<name>/

v1.0.0 - The OPSX Release

26 Jan 00:10
0e6f42c

Choose a tag to compare

What's New in v1.0.0

OpenSpec 1.0 marks the transition from experimental to stable. The workflow has been rebuilt around an action-based system where AI understands your project's state—what artifacts exist, what's ready to create, and what each action unlocks.


⚠️ Migrating from Pre-1.0

Breaking changes:

  • Old commands removed — /openspec:proposal, /openspec:apply, /openspec:archive no longer exist
  • Config files removed — Tool-specific files (CLAUDE.md, .cursorrules, AGENTS.md, project.md) are no longer generated

To upgrade: Run openspec init. Your existing work is safe—active changes, archived changes, and main specs are all preserved. Only obsolete config files are cleaned up (with confirmation).

Migration guide


New

  • Action-based workflow — Replaced the rigid proposal → apply → archive sequence with flexible actions. Edit any artifact anytime. The artifact graph tracks state automatically.
Command What it does
/opsx:explore Think through ideas before committing to a change
/opsx:new Start a new change
/opsx:continue Create one artifact at a time (step-through)
/opsx:ff Create all planning artifacts at once (fast-forward)
/opsx:apply Implement tasks
/opsx:verify Validate implementation matches artifacts
/opsx:sync Sync delta specs to main specs
/opsx:archive Archive completed change
/opsx:bulk-archive Archive multiple changes with conflict detection
/opsx:onboard Guided 15-minute walkthrough of complete workflow
  • Dynamic instructions — AI instructions are now assembled from three layers: context (your tech stack), rules (artifact-specific constraints), and templates (output structure). AI queries the CLI for real-time state instead of receiving static prompts.

  • Semantic spec syncing — Delta specs use markers like ## ADDED Requirements and ## MODIFIED Requirements. Archive parses these at the requirement level, not brittle header matching.

  • Agent Skills — Single .claude/skills/ directory replaces 8+ scattered config files. YAML-fronted markdown files that work across Claude Code, Cursor, and Windsurf.

  • Onboarding skill/opsx:onboard walks new users through their first complete change with codebase-aware task suggestions. 11 phases, ~15 minutes.

  • Interactive setupopenspec init shows animated welcome screen and searchable multi-select for tools. Pre-selects already-configured tools for easy refresh.

  • 21 AI tools supported — Claude Code, Cursor, Windsurf, Continue, Gemini CLI, GitHub Copilot, Amazon Q, Cline, RooCode, Kilo Code, Auggie, CodeBuddy, Qoder, Qwen, CoStrict, Crush, Factory, OpenCode, Antigravity, iFlow, and Codex.

  • Custom schemas — Define custom artifact workflows in openspec/schemas/ without touching package code.

Fixed

  • Claude Code YAML parsing failure when command names contained colons
  • Task file parsing to handle trailing whitespace on checkbox lines
  • JSON instruction output now separates context/rules from template (AI was copying constraint blocks into artifact files)

Documentation

New guides: Getting Started · CLI Reference · Commands · Concepts · Customization

v0.23.0 - Bulk Archive, Simplified Setup

21 Jan 01:22
3b16b13

Choose a tag to compare

What's New in v0.23.0

This release streamlines both active development and post-implementation workflows.

New

  • Bulk archive - Archive multiple completed changes at once with /opsx:bulk-archive. Validates specs, detects conflicts, and shows a single confirmation before archiving.

Improved

  • Config setup - Creating a new OpenSpec config now uses sensible defaults with helpful comments instead of asking questions. Get started faster.

v0.22.0 - Project Configuration

20 Jan 08:01
7d1237f

Choose a tag to compare

What's New in v0.22.0

OpenSpec now supports per-project configuration, letting you customize behavior and define schemas for project-specific workflows. (Still very experimental, feedback appreciated!)

More docs available here (search for schema and/or config): https://github.com/Fission-AI/OpenSpec/blob/main/docs/experimental-workflow.md

New

  • Project configuration - Configure OpenSpec per-project with openspec/config.yaml to inject custom rules, specify context files, and control schema resolution
  • Project-local schemas - Define custom artifact schemas in openspec/schemas/ for project-specific workflows
  • Schema management - Inspect and manage artifact schemas with new openspec schema commands (list, show, export, validate)

Fixed

  • Config loading now handles null rules field without errors