Use this file to discover all available pages before exploring further.
Azul has two components to keep updated: the CLI daemon and the Studio companion plugin. They are versioned and distributed separately, so you can update each one independently. It’s good practice to update both at the same time to avoid compatibility gaps.
If azul --version still shows the old version after an npm update, check that the globally installed bin path is first in your PATH. Running npm root -g shows where npm installs global packages.
If you installed a local or manually built copy of the plugin instead of the Creator Store version, remove the old plugin file from Studio and replace it with the latest build from the plugin directory on GitHub.
After a manual plugin update, restart Studio to ensure the new plugin version is fully loaded before starting a sync session.