Archbee CLI Troubleshooting

troubleshooting the archbee cli this guide covers the most common problems users encounter when working with the archbee cli use these troubleshooting steps before opening a support ticket most issues can be resolved by validating your setup, checking authentication, or reviewing the cli command options cli does not start problem running archbee fails or does nothing recommended steps run archbee version to verify the cli is installed reinstall the cli globally using npm if the command is missing restart your terminal session and try the command again install command npm install g @archbee/cli hot reload is not working problem changes are not updating in the local preview recommended steps restart the local development server using archbee dev verify your project contains a supported config file check that your documentation folder is not ignored or excluded broken links are not being detected run archbee broken links make sure your internal links use valid relative paths openapi sync problems problem sync openapi fails during import common causes invalid openapi schema unsupported references incorrect file path missing authentication recommended first step validate the openapi file before syncing authentication errors 401 unauthorized usually caused by invalid api key expired token wrong space id 403 forbidden usually caused by missing permissions or a read only team api key publishing problems problem publish space fails solution verify you have write permissions the space id is correct the api key belongs to the correct organization recommended debugging workflow run archbee validate to verify project structure run archbee broken links to scan internal links use archbee \<command> help to review command usage and arguments additional resources main docs https //archbee com/docs https //archbee com/docs npm package https //www npmjs com/package/@archbee/cli https //www npmjs com/package/@archbee/cli cli help archbee help