We hope you’ve been enjoying your Summer and have found an opportunity to adventure out and explore with family and friends.

Here’s the latest from the Venice team covering the last few weeks of our development. Stay tuned in the coming weeks for a number of major new releases from our team.

Today’s cover art can be found on the Venice Social feed.

Models

• Upgraded Venice Large to Qwen 235B A22B 2507, the latest version of this premier model published by the team at Qwen. Venice now routes thinking and non thinking requests programmatically between the two optimized models. You can learn more about this update here.

• Increased context size on Venice Small (Qwen 3 4B) to 40k tokens to fully expose model’s available context.

App

• Launched “Auto Mode” as the default for new Venice users. Auto mode will route prompts to the best model to answer the user’s questions, removing the need for users to swap between image and text generation. You can learn more about this update here.

• Migrated model settings from the top right corner of the chat window into a drop down selector in the chat input. You can learn more about this update here.

• Added a new “Settings” menu to the left nav bar to unify all Venice settings into a single place.

• Added “thumbs up” / “thumbs down” rankings to results to allow Venice to better gauge model quality based on user feedback.

• Permit users to auto-generate tags when posting a new social feed image.

• Added a UI element to show when a user has custom system prompts enabled.

• Added support to lock image settings to a specific model.

• Improved Venice’s models knowledge of its own features and capabilities to permit the model to guide users on how to use Venice more effectively.

• Added the concept of current user time to the models to permit more relevant responses when dealing with time pertinent requests. 

• Combined the “Edit Image” and “Enhance Image” modals into a single user interface for simpler image edits.

• Added UI states to report when the local browser database is inaccessible due to resource constraints imposed by the user’s browser.

• Permit any image in the chat history to be regenerated — previously only the last image in the conversation list would permit regeneration.

• Updated the social feed notification drawer to mark all notifications as read when the drawer is viewed.

• Updated content violation interface on image generation to give more information on what happened and provide a mechanism to regenerate certain prompts on our default model.

• Improved bulk chat deletion UX to avoid accidental clicks during flow.

• Permit the deletion of image variants when generating more than 1 image at a time.

• Show an improved error message when users are trying to save a social feed username that’s already in use.

• Fixed a bug where users were unable to preview the original source image when image mode was enabled.

• Fixed a bug that was stripping EXIF data from WebP images when they were downloaded.

• Fixed a bug where when users created a new conversation, the type would be reset back to text. Instead we now carry over whatever the last conversation type they were previously using, or if in auto mode, that is selected.

Characters

• Updated the default character sorting order to require reviews on the latest characters displayed in the list.

• Added the ability for Character chats to support file uploads.

• Fixed a layering issue in the Character modal where the footer could overlap content or interactive elements. The stacking order has been adjusted so the footer no longer obscures underlying UI, improving visibility and clickability.

API

• Added an API Key Info route to return information about a specific API key. API docs have been updated.

• Added an API Docs page describing the Venice model suite.

• Create custom validations for API models to avoid infinite repetition from certain settings on certain models.

• Retired the Fluently image model from the API based on usage patterns.

• Fix API bug that was artificially limiting the max payload size of requests, preventing the full context from being utilized.