Release 10.9

Release Date: October 4th, 2024

---

New Feature	Improvement	Bug Fix	Enterprise Only

Clarifai Product Roadmap

Status	Change	Details
	Introduced new public roadmap	We've published a public roadmap to give you a view of our upcoming plans and to gather your valuable feedback. You can explore the features we're considering, vote for the ones you want most, or submit new ideas For a sneak peek at what's coming, such as Compute Orchestration, check out our public roadmap here.

Control Center

Status	Change	Details
	Introduced Clarifai’s Control Center	It is an all-in-one interface that provides centralized visibility into your utilization of our platform during a selected period. Learn more about it here.

New Published Models

Status	Change	Details
	Published new models	Published OpenAI o1-preview, a reasoning-focused AI model designed for complex problem-solving in math, coding, and science. Published OpenAI o1-mini, a reasoning-focused LLM designed for complex problem-solving in math, coding, and science. Published Llama-3.2-11B-Vision-Instruct, a multimodal LLM by Meta designed for visual reasoning, image captioning, and VQA tasks, supporting text and image inputs with 11B parameters. Published Llama-3.2-3B-Instruct, a multilingual, instruction-tuned LLM optimized for dialogue and text generation tasks.

Python SDK​

Status	Change	Details
Private Preview	Introduced enhanced model upload capabilities	Introduced a new method for model uploads to our platform. This integration includes: A new, more efficient model upload process utilizing Clarifai's runners. Migration of relevant files from runners-python to appropriate locations within the clarifai-python repository. Learn more about it here.
	Enhanced model upload capabilities with HuggingFace integration and concept handling	We've expanded our model upload functionality to improve integration with HuggingFace and enhance concept handling: Introduced a HuggingFaceLoader utility for seamless checkpoint downloads and concept fetching from HuggingFace for classification and detection models. Implemented new methods in model_upload for efficient checkpoint downloads and concept handling. Updated the model upload process to use the new HuggingFaceLoader for HuggingFace-related models. Changed the command-line interface to use --model_path instead of -folder for improved clarity.

Platform

Status	Change	Details
	Added "Collaborations" as a top-level link	We’ve introduced "Collaborations" as a top-level link, similar to "My Apps" and "Community," making it easier for users to access apps they’ve been invited to collaborate on.
	Made some visual enhancements	We fixed CSS artifacting issues in the app creation input fields, improving the visual experience. We fixed an issue where the password field in the sign-up modal was not displaying correctly. We improved tables across the platform, including updating header names to use Capital Case and resolving table height issues for a more consistent and polished appearance. We fixed a visual issue where the input field border in the "Create an App from a template" modal was displayed incorrectly. We fixed an issue where the icon for an app's cover image was displayed incorrectly in the app's sidebar. We fixed an issue where the "Template" tag, which identifies template apps on the "My Apps" listing page, was not displaying correctly. We fixed an issue where the validation text, which is shown when a user provides incorrect input values in the sign-up form, overlapped and obstructed other fields in the form.
	Fixed an issue with saving users' contact information	Previously, a bug during account creation caused contact information to be captured incorrectly. Even attempts to update the information on the account settings page would fail. We fixed it.
	Fixed issues with the user-guided tour	We fixed some issues with the application guided tour flow for onboarding new users. Primarily, the guided tour is now only shown to logged-in users who have never used our platform before. Also, Org Users are not shown the guided tour because they already went through this process via their personal accounts.
	Fixed an issue with listing invited members to an organization	Previously, Org Contributors were able to view the pending members tab. Since inviting members is an Admin-only function, we now restrict Org Contributors, Org Users, and Team Contributors from accessing the pending invitations list.
	Fixed an issue with inviting users to an organization	Previously, users could not accept invitations to join an organization if the invitation was sent to an email with a different case (upper or lower) than the one associated with their account. We’ve now made email addresses case-insensitive when sending organization invitations.
	Fixed an issue with pricing display	We fixed an issue where the pricing information for base workflows was missing. The pricing information is now displayed in the upper-right section of a workflow page.
	Fixed an issue with user registration	Previously, some users were able to create an account without consenting to the terms of service. Now, the "Create account" button remains disabled until the user consents by checking the terms of the service box.

Workflows

Status	Change	Details
	Introduced workflow versioning	You can now create workflow versions that track the changes of models, operators, agents, prompts, and their configurations within the pipeline nodes.
	Fixed RAG Prompter modification issues in public workflows	Previously, modifying a RAG Prompter model in a public workflow would unexpectedly create a new private model and version, causing save failures due to the incompatibility of private models in public workflows. This also led to workflow execution errors. We've resolved this by ensuring that modifications to existing nodes reuse the original model, either creating a new version or updating the existing one as appropriate. This fix maintains workflow integrity, prevents unintended privatization, and eliminates related execution errors.
	Fixed compatibility issue between Image Cropper and Multimodal-to-Text models in Workflows	Previously, when using an Image Cropper with a Multimodal-to-Text model in a workflow, the cropped image regions were not being properly processed. This was due to the Multimodal-to-Text model being incorrectly configured with a single 'Any' input type, causing the workflow runner to skip the cropped regions. We've addressed this by updating the model's input configuration to correctly specify [image, text] input fields. This fix ensures that all cropped image regions are now properly processed by the Multimodal-to-Text model, improving the accuracy and functionality of workflows using these components.
	Fixed an issue with the Concept thresholder	We fixed an issue where the concept thresholder was displaying concept ID while selecting concepts instead of concept names. Now, this issue is fixed, and it shows concept names correctly.
	Fixed an issue with the RAG-prompter metadata field update	Previously, when updating metadata, the old metadata was merged with the new metadata instead of being overwritten. We fixed the issue, now metadata gets correctly overwritten instead of being merged.
	Fixed issues with max_results and min_score sliders and metadata input in the workflow builder page	Previously, the max_results slider allowed decimal inputs and had an inconsistent maximum value, while the min_score slider's range was incorrect. Additionally, the metadata field was rejecting valid JSON input. We fixed these issues as follows: Max Results: The slider now only accepts whole numbers and correctly allows values up to 128, instead of being limited to 100. Min Score: We've adjusted the range to be between 0 and 1, with a step size of 0.01, ensuring more precise and appropriate score selection. Metadata: The system now properly accepts and processes valid JSON input in the metadata field, allowing users to input structured data as intended.

Models

Status	Change	Details
	Fixed an issue with the model builder page	Previously, when users attempted to expand the Output Settings section while viewing model version details, a client-side exception would occur, showing the error: "Application error: a client-side exception has occurred (see the browser console for more information)." This would crash the page. Now, the issue has been resolved, and users can seamlessly expand the Output Settings section.