Changelog

The latest updates and improvements to Playbook.

v0.42.0

Playbook Studio v0.42.0

Features

  • Added a diagnostics page in Studio to support testing in enterprise environments
  • Cowork plugins now publish using an updated manifest format and include a new connectivity probe for more reliable integrations
  • Cowork MCP skill editing is now supported via OAuth 2.1 authentication

Fixes

  • Updated a core networking dependency to address two security vulnerabilities
v0.42.1

Playbook Studio v0.42.1

Fixes

  • Resolved an issue that was preventing the app from being properly built and distributed on macOS
v0.38.0

Playbook Studio v0.38.0

Features

  • The desktop app is now code-signed on macOS, enabling seamless automatic updates

Fixes

  • Resolved an issue that could cause database sync to fail due to a missing internal migration
v0.39.0

Playbook Studio v0.39.0

Fixes

  • Resolved an issue that could cause the macOS code signing step to fail during the build process
v0.40.0

Playbook Studio v0.40.0

Fixes

  • Resolved an issue that could cause the macOS code signing process to fail during builds
v0.40.1

Playbook Studio v0.40.1

Fixes

  • Resolved an issue with the v0.40.1 release of Playbook Studio to ensure a smooth and stable experience.
v0.41.0

Playbook Studio v0.41.0

Fixes

  • Resolved an issue with internal build conditions that could affect reliability of automated processes behind the scenes
v0.37.0

Playbook Studio v0.37.0

Features

  • The editor now checks whether it has permission to write to your home directory, helping catch setup issues earlier

Improvements

  • Skills documentation has been updated to recommend the skill creator tool as the best starting point for building new skills

Fixes

  • Resolved an issue that was causing problems with data sync and remote connections
  • Fixed a formatting error in the documentation that prevented certain pages from loading correctly
v0.37.1

Playbook Studio v0.37.1

Fixes

  • Resolved an issue where database sync could fail due to a missing internal migration step
v0.36.0

Playbook Studio v0.36.0

Improvements

  • Enhanced the editor with better data flow, plugin visibility controls, and dashboard authorship tracking
  • Reduced notification noise by hiding the “sync tokens refreshed” toast message
  • Upgraded core dependencies across the board for improved performance, stability, and security (including Electron, Vite, Astro, and internal database libraries)
v0.26.0

Playbook Studio v0.26.0

Features

  • Implemented auto-updating builds for Windows

Fixes

  • Resolved an issue causing pages to fail to load correctly on the documentation site
  • Restored missing documentation for teams and team plugins
v0.27.0

Playbook Studio v0.27.0

Fixes

  • Resolved an issue causing a 500 error on the documentation site
  • Restored missing documentation for teams and team plugins
v0.28.0

Playbook Studio v0.28.0

Fixes

  • Resolved an issue with the build and signing process to improve release reliability and security
v0.29.0

Playbook Studio v0.29.0

Improvements

  • Updated internal build and signing processes to improve reliability and compatibility
  • Migrated automation workflows to a new infrastructure platform for better performance and maintainability

Fixes

  • Resolved issues with the Azure Trusted Signing configuration to improve stability
  • Fixed a problem with how signing tools were located and configured during the build process
v0.30.0

Playbook Studio v0.30.0

Fixes

  • Resolved an issue with the installation process for code signing tools on Windows
v0.31.0

Playbook Studio v0.31.0

Fixes

  • Resolved an issue with the app signing process to improve reliability during updates and installations.
v0.32.0

Playbook Studio v0.32.0

Improvements

  • Added internal logging to help diagnose code signing issues during the build process
v0.33.0

Playbook Studio v0.33.0

Fixes

  • Updated internal build tooling to improve compatibility with modern code signing processes
v0.34.0

Playbook Studio v0.34.0

Fixes

  • Resolved an issue where incorrect formatting caused problems with certain file path handling internally
v0.35.0

Playbook Studio v0.35.0

Features

  • Added a “Check for Updates” option in the menu, so you can manually check for the latest version at any time
  • Reduced the automatic update check interval so you’ll be notified about new versions more promptly
v0.35.1

Playbook Studio v0.35.1

Features

  • Added an option to run the release process automatically without requiring manual confirmations
  • The app now prompts you to restart after an update has been downloaded
v0.20.0

Playbook Studio v0.20.0

  • Move changelog generation into release script
v0.21.0

Playbook Studio v0.21.0

Features

  • Team-scoped plugins are now available in the web app, making it easier to manage and share plugins across your team

Fixes

  • Fixed an issue where document frontmatter was being incorrectly removed and rewritten in the editor, preserving your content’s metadata as intended
v0.22.0

Playbook Studio v0.22.0

Features

  • Teams can now manage plugins and organize dashboards into groups
  • Added public-facing documentation with interactive embedded actions directly in the product

Improvements

  • Documentation is now reliably deployed and loads correctly in all environments

Fixes

  • Fixed an issue preventing the documentation panel from loading properly inside Studio
v0.23.0

Playbook Studio v0.23.0

Fixes

  • Resolved an issue that caused unnecessary skill installation steps to run in automated workflows, improving reliability and performance in those environments.
v0.24.0

Playbook Studio v0.24.0

Features

  • Introduced Playbook Studio v0.24.0

Note: The raw release notes provided don’t include enough detail to generate meaningful changelog entries beyond the version release itself. If you share the full notes — including what was added, changed, or fixed — I can rewrite them into a complete, customer-friendly changelog.

v0.25.0

Playbook Studio v0.25.0

Fixes

  • Resolved an issue with macOS installation packaging that could cause problems when files were already in the correct location
  • Fixed a bug where certain database test settings were not properly carried over during release processes