Changelog

Features

• Added a shared filesystem registration foundation, enabling future support for shared storage across sessions
• Introduced a Cowork session registry, laying the groundwork for collaborative session management
• MCP connections can now use local JWT verification for faster, more reliable authentication
• MCP now supports public client access for unauthenticated connections by default
• Added support for claude.ai and claude.com origins when connecting via MCP
• MCP resource metadata is now served at a standardized location following the RFC 9728 specification
• The MCP resource server client ID is now configurable, with production seeding support
• Token exchange now correctly recognizes MCP as a valid audience, allowing smoother authentication flows

Improvements

• Updated authentication library (Better Auth) to the latest version for improved stability and compatibility
• After completing OAuth consent, users are now automatically redirected to the correct destination
• MCP connections now expose WWW-Authenticate headers, improving compatibility with standard authentication clients
• Expanded internal documentation covering the MCP testing workflow for operators and contributors

Fixes

• Fixed an issue where manager plugin sync permissions were not correctly aligned
• Fixed a bug causing local plugin edit status to sync inaccurately
• Resolved an issue with the OAuth browser sign-in redirect and consent parameter handling

Features

• Owners and managers can now self-approve plugin versions without waiting for external review
• MCP connections are more secure with tighter scope controls, smarter draft handling, and organization-bound tokens

Improvements

• OAuth login and consent pages now use absolute URLs for more reliable redirects
• Published plugins are now written to standard user directories instead of session-based locations, making them easier to find and manage

Fixes

• Resolved a sync issue caused by missing plugin version data in local database migrations
• Fixed a sync reliability issue where schema changes could cause plugin version fields to be dropped or misread

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

Fixes

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

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

Fixes

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

Fixes

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

Fixes

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

Fixes

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

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

Fixes

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

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)

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

Fixes

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

Fixes

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

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

Fixes

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

Fixes

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

Improvements

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

Fixes

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

Fixes

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

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

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

• Move changelog generation into release script

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

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

Fixes

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

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.

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