Recipe Management

Overview

Karini AI provides a comprehensive recipe versioning feature that allows users to save a recipe with its current configuration, publish it as a stable version, and then test it before deployment to Copilot. This ensures that each version acts as a reliable snapshot of the recipe, enabling users to experiment confidently while maintaining control over production deployments. If needed, users can roll back to any previously published version, ensuring stability and continuity.

Agent Recipe Lifecycle

The Agent recipe adheres to a structured lifecycle designed to provide stability, controlled flexibility, and continuous improvement. This lifecycle enables recipes to evolve iteratively while safeguarding production environments from untested changes. By progressing through the Publish, Draft, Deploy, and Rollback stages, users can reliably build, refine, and operationalize Agent recipes with full version control and assured consistency.

Publish

Publishing creates a stable version of the Agent recipe by capturing its current configuration. This version serves as a fixed reference point, allowing users to validate behavior and performance before making it available for wider use. Publishing also ensures that the recipe is safeguarded against unintended edits.

When a recipe is published, a confirmation dialog appears with an auto-generated version name, and users can optionally add tags to organize and identify versions.

After publishing, the interface updates to display the recipe status as Published along with the assigned version number (e.g., V16-Published).

By clicking the Ver. button, users can see the complete version history of the recipe, including version number, tags, publication date, and publisher details.

Draft

Whenever changes are made to a published recipe, it transitions back into draft mode. In this stage, users can modify workflows, logic, or settings without impacting the live version. Drafts are flexible and iterative, allowing experimentation until the recipe is ready to be published again.

Once a published recipe is modified, its status automatically changes to Draft (e.g., V3 – Draft), allowing further edits before re-publishing.

Deploy

Once a recipe has been published and thoroughly tested, it can be deployed to Copilot. Deployment activates the recipe in real-world environments, making it operational for live interactions. By deploying only published versions, teams maintain reliability and version control while ensuring continuous improvement.

Users can initiate deployment by selecting Actions → Deploy from the interface.. A confirmation dialog appears showing the version number, ensuring the correct version is deployed to Copilot.

After confirmation, the recipe displays the deployed version, indicating the active release in Copilot.

Rollback

Users can roll back to a previously published version of a recipe by selecting the Ver. button, which displays all associated versions. After choosing the desired version, it becomes the active version, restoring the recipe to a stable configuration. This ensures that any issues in newer versions can be quickly resolved by rolling back to a reliable, tested version.

Refer to the video for rollback functionality.

Rolled-back versions can be deployed upon selection, restoring the recipe to a previous stable state.

For a step-by-step demonstration of this process, please refer to the video.

The Recipe Table provides an overview of the current and deployed versions of each recipe, including key details such as:

• Current Version: The active version of the recipe.

• Deployed Version: The version that has been deployed to the system.

• Deployed By: The user responsible for the deployment.

• Deployed Date: The date and time when the recipe was deployed.