Publish to Vibe

mistral apps publish adds a deployed app alias to the Vibe catalog. mistral apps unpublish removes its catalog entry without stopping the app.

First deploy the app, then run these commands from its project directory:

mistral login
mistral apps publish

mistral login
mistral apps publish

The command reads the deployment binding saved in mistral.json. It doesn't build or redeploy the app. By default, it publishes the production alias. To publish another alias, pass --alias.

The entry inherits the app's title, description, and visibility. You must have permission to modify the source app. Users can only open apps that their account and organization allow.

Open Vibe Work with the account and organization that have access to the app, then find its published entry in the app catalog. If the app isn't available to the intended users, check its title and visibility in Studio.

The app's deployed URL works whether or not the app is published. To decide between an app and a plugin, see Apps overview.

mistral apps unpublish

mistral apps unpublish

Unpublishing removes the catalog entry for the selected alias, not its deployment. You can publish the app again later. You can safely repeat either command for the same alias. If a draft or archived entry blocks publication, the CLI reports the conflict and prints the unpublish command that removes it.

Both commands accept --json and return a nonzero exit code on failure. For flags, see the CLI reference.