Ai

OpenSpec v1.3.1 Improves Artifact Resolution and Telemetry Reliability

OpenSpec v1.3.1 Improves Artifact Resolution and Telemetry Reliability

OpenSpec v1.3.1 is a focused maintenance release that improves how workflow artifacts, validation, and telemetry behave in real-world environments. The update is especially relevant for teams working with symlinks, glob-based outputs, locked-down networks, and automated agents that depend on clean machine-readable CLI responses.

What Changed

The biggest fix in v1.3.1 is more reliable canonical artifact path handling. OpenSpec now resolves workflow artifact paths through native realpath, which reduces mismatches caused by symlinks and case-insensitive filesystems during apply and archive operations.

Artifact output handling also got tighter. Apply instructions using glob artifact outputs now resolve correctly, while literal outputs are explicitly enforced as file paths. In addition, directory paths containing glob-special characters are now escaped before matching, which closes a subtle but important edge case for file operations.

Validation has been improved as well. OpenSpec can now detect requirements hidden inside fenced code blocks or otherwise obscured in main specs, making validation more robust when specification files contain embedded examples or formatted sections.

For automation workflows, the CLI now produces cleaner machine-readable output. Spinner progress no longer leaks into stderr when the --json flag is used, which means agents and scripts parsing combined stdout and stderr can trust the JSON output more reliably.

Telemetry behavior has also been hardened for restricted environments. In firewalled or locked-down networks, PostHog errors are now swallowed with a one-second timeout, while retries and remote config are disabled. This prevents PostHogFetchNetworkError from surfacing unnecessarily. The project has also moved telemetry opt-out guidance earlier in the README, installation guide, and CLI reference. On top of that, telemetry config discovery now properly honors XDG_CONFIG_HOME on Linux and %APPDATA% on Windows.

Why It Matters

This release is important because it improves operational reliability rather than adding flashy surface features. Teams using OpenSpec in CI pipelines, enterprise desktops, or mixed filesystem environments should see fewer path-related failures and better consistency during artifact apply and archive steps.

The clean --json behavior is particularly useful for AI agents, automation runners, and developer tooling that depend on structured CLI output. Instead of having to defensively filter spinner noise, downstream parsers can consume responses more confidently.

The telemetry changes also make OpenSpec friendlier for regulated, offline, or firewalled environments where outbound analytics calls can generate distracting errors. Combined with stronger validation and better glob handling, v1.3.1 is a practical stability update that reduces friction for production-grade usage.

Official Source: https://github.com/Fission-AI/OpenSpec/releases/tag/v1.3.1