sx 2.0 release notes / what's new

sx 2.0 release notes / what's new

sx 2.0 transforms the open-source AI asset package manager into a native desktop application for Mac, Windows, and Linux, shifting its distribution model to support non-technical users. While the original version focused on Git-based workflows for developers, 2.0 enables teams in marketing, legal, and sales to share AI skills, MCP configurations, and commands without requiring a terminal or Git knowledge.

Shared-Folder Distribution Model

Sx 2.0 replaces the command-line requirement for skill sharing with a shared-folder approach. Users can point the application to a folder in Dropbox, Google Drive, OneDrive, or iCloud, and drag-and-drop markdown files to publish skills.

This model leverages existing corporate file-syncing services to handle replication and versioning, removing the need for a separate server or account system. When a user clicks "Sync" in the app, sx performs an sx install in the background, translating assets into the specific formats required by various AI clients, including Claude Code, Cursor, Copilot, Codex, Gemini, and Cline.

Vault Format v2

To support the shared-folder workflow, sx 2.0 introduces Vault Format v2. Assets are now stored as plain, readable markdown files directly on disk at assets/<name>/. Version history is maintained in .sx/versions/.

This change allows the vault to be compatible with other tools like Obsidian or grep, and allows AI clients like Claude Code to point directly to the vault without needing to unpack files. Developers continue to have full access to the CLI and Git-based vaults, as the app and CLI read the same vault formats.

Pluggable Extension System

Sx 2.0 introduces an extension system to prevent core product bloat. Extensions are ES modules with a manifest, requiring no build step. They can add dashboard widgets, editor commands, and new views.

Key extensions included in the marketplace include:

  • Collection Doctor: Analyzes collections for thin descriptions, stale assets, or oversized skills that consume too much context.
  • Adoption Widgets: Tracks which skills are being used by team members to measure utility.
  • Adoption Rota: Provides adaptive review due dates for assets based on usage levels.
  • Collection Export: Compiles collections into plugins for Claude Code, Codex, or Gemini.

Extensions are permission-gated with restricted access to the filesystem, Node, and network. They are treated as sx assets themselves, meaning they can be versioned, pinned, and audited through the same pipeline as skills.

Community Discussion and Counterpoints

While the move to shared folders is designed for accessibility, some community members have raised concerns regarding version control and reliability.

"I can't think of anything worse than sharing skills via Dropbox. The version management and AIBoM problems that generates is extremely painful."

Critics argue that Git repositories or internal IT push systems are superior for versioning and tracking which LLM version is paired with a specific skill. Others suggest that skills should live directly within a project's repository folder to ensure project-specific alignment.

Conversely, some users have reported success with similar manual symlink-based Dropbox approaches, noting that it simplifies the process for non-technical users who struggle with the same self-containment and replication issues sx 2.0 aims to solve.

Sources