open-webui v0.8.3 版本更新介绍
发布日期: 2026-02-17
版本号: v0.8.3
本次更新包含以下新增功能和修复:
新增功能方面:用户现在可以从模型选择下拉菜单直接编辑模型设置,无需跳转到单独的页面。图像编辑API增加了对背景透明度控制的支持。优化了模型列表的加载性能,减少了不必要的数据库查询。改进了工具调用结果的显示格式,使其在不同屏幕尺寸下布局更合理。同时增强了应用的整体性能、稳定性和安全性,并更新了葡萄牙语(巴西)、简体中文和繁体中文的翻译。
修复问题方面:修复了在提示词中使用用户邮箱变量时显示“未知”的问题。修正了上传图像未能正确发送至支持视觉的模型,以及文件附件在无用户文本时无法正常工作的问题。改进了当模型引用已删除函数时的错误处理,避免整个模型列表加载失败。增强了应用启动时的模型预取和函数模块加载失败的容错能力,防止程序崩溃。最后修复了PostgreSQL数据库中分组查询的语法错误。
更新内容 (中文)
[0.8.3] - 2026-02-17
新增功能
- ✏️ 模型编辑快捷方式。 用户现在可以直接从模型选择器下拉菜单编辑模型,无需导航至单独的管理或工作区页面,即可更快捷地修改模型设置。Commit
- 🎨 图像编辑 API 背景支持。 图像编辑 API 现已支持 OpenAI gpt-image-1 模型的
background参数,允许在 UI 中启用该功能时控制背景透明度(“transparent”、“opaque”、“auto”)。#21459 - ⚡ 更快的模型过滤。 模型访问控制过滤不再执行冗余的数据库查询来重新获取内存中已有的模型信息,从而减少了非管理员用户加载模型列表时的延迟。Commit
- 🔧 工具调用显示改进。 工具调用结果现在以更清晰的键值格式显示参数,而非原始 JSON。响应式布局在窄屏幕上仅显示工具名称,在宽屏幕上显示完整标签,防止文本换行至多行。Commit
- 🔄 通用改进。 实施了多项改进以增强应用程序的性能、稳定性和安全性。
- 🌐 增强并扩展了葡萄牙语(巴西)、简体中文和繁体中文的翻译。
修复内容
- 📧 USER_EMAIL 变量修复。
{{USER_EMAIL}}模板变量现在正确返回用户的电子邮件地址,而非提示中的 “Unknown”。#21479,#21465 - 🖼️ 图像和文件附件处理修复。 上传的图像现在可以正确发送给支持视觉的模型,并且即使未输入用户文本,文件附件也能正常工作。这修复了后端未正确处理文件附件的两个问题:图像未转换为 API 请求所需的格式,以及当用户仅发送文件而未附带文本时,文件上下文被丢弃。Commit,#21477,#21457
- 🛡️ 缺失函数错误处理。 引用已删除函数的模型不再导致整个
/api/models端点崩溃;取而代之的是,缺失的函数会被跳过并记录日志,允许其余模型成功加载。#21476,#21464 - 🚀 启动模型预获取错误处理。 如果在应用启动期间模型预获取失败,应用程序现在会记录警告并继续运行,而不是完全崩溃。Commit
- ⚙️ 函数模块加载错误处理。 在启动或模型处理期间加载失败的函数模块现在会被捕获并记录日志,防止模型引用具有加载错误的函数时崩溃。Commit
- 🗄️ PostgreSQL 分组查询修复。 使用 PostgreSQL 时,
/api/v1/groups/端点不再因 GROUP BY 错误而失败;成员计数现在使用关联子查询计算,以获得更好的数据库兼容性。#21458,#21467
更新内容 (原始)
[0.8.3] - 2026-02-17
Added
- ✏️ Model edit shortcut. Users can now edit models directly from the model selector dropdown menu, making it faster to modify model settings without navigating to separate admin or workspace pages. Commit
- 🎨 Image edit API background support. The image edit API now supports the background parameter for OpenAI’s gpt-image-1 model, enabling background transparency control (“transparent”, “opaque”, “auto”) when the feature is exposed in the UI. #21459
- ⚡ Faster model filtering. Model access control filtering no longer makes a redundant database query to re-fetch model info that is already available in memory, reducing latency when loading model lists for non-admin users. Commit
- 🔧 Tool call display improvements. Tool call results now display arguments in a cleaner key-value format instead of raw JSON, with a responsive layout that shows only the tool name on narrow screens and the full label on wider screens, preventing text wrapping to multiple lines. Commit
- 🔄 General improvements. Various improvements were implemented across the application to enhance performance, stability, and security.
- 🌐 Translations for Portuguese (Brazil), Simplified Chinese, and Traditional Chinese were enhanced and expanded.
Fixed
- 📧 USER_EMAIL variable fix. The {{USER_EMAIL}} template variable now correctly returns the user’s email address instead of “Unknown” in prompts. #21479, #21465
- 🖼️ Image and file attachment handling fixes. Uploaded images are now correctly sent to vision-enabled models, and file attachments now work even when no user text is entered alongside a system prompt. This fixes two issues where the backend was not properly processing file attachments: images weren’t converted to the expected format for API requests, and file context was dropped when the user sent only a file without accompanying text. Commit, #21477, #21457
- 🛡️ Missing function error handling. Models that reference deleted functions no longer cause the entire /api/models endpoint to crash; instead, the missing functions are skipped and logged, allowing the rest of the models to load successfully. #21476, #21464
- 🚀 Startup model pre-fetch error handling. If model pre-fetching fails during app startup, the application now logs a warning and continues instead of crashing entirely. Commit
- ⚙️ Function module loading error handling. Function modules that fail to load during startup or model processing are now caught and logged, preventing crashes when models reference functions with loading errors. Commit
- 🗄️ PostgreSQL group query fix. The ‘/api/v1/groups/’ endpoint no longer fails with a GROUP BY error when using PostgreSQL; member counts are now calculated using correlated subqueries for better database compatibility. #21458, #21467