issue: no 0.5 -> 0.6 update documentation for tools and functions #102

New Issue

2026-02-15T17:15:01-05:00

yindo commented

2026-02-15 17:15:01 -05:00

Originally created by @aimendenche-nw on GitHub (Oct 1, 2025).

Check Existing Issues

I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

0.6.32

Ollama Version (if applicable)

No response

Operating System

ubuntu

Browser (if applicable)

No response

Confirmation

I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

There should be an official migration guide for 0.5 → 0.6 in the documentation.

This guide should list:

All breaking changes between 0.5 and 0.6.

Deprecated imports, functions, and modules.

New replacements or updated usage examples.

Steps required to update custom tools, plugins, and extensions.

Actual Behavior

Currently, the official documentation includes a Migration Guide: 0.4 → 0.5, but there is no migration guide for 0.5 → 0.6.
When upgrading to version 0.6.x, many tools, functions, and imports no longer work due to breaking changes in the API and plugin structure. Without documentation, it is unclear what needs to be modified to make custom tools and extensions compatible.

Steps to Reproduce

Have a working OpenWebUI 0.5.x instance with custom tools, plugins, or extensions.

Upgrade to OpenWebUI 0.6.x (latest 0.6.32 tested).

Try importing or running the same custom tools or functions.

Observe that many imports fail (e.g., libraries, plugin hooks, functions no longer recognized).

Look for migration guidance in the docs → only 0.4 → 0.5 guide exist

Logs & Screenshots

Additional Information

No response

Originally created by @aimendenche-nw on GitHub (Oct 1, 2025). ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version 0.6.32 ### Ollama Version (if applicable) _No response_ ### Operating System ubuntu ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior There should be an official migration guide for 0.5 → 0.6 in the documentation. This guide should list: All breaking changes between 0.5 and 0.6. Deprecated imports, functions, and modules. New replacements or updated usage examples. Steps required to update custom tools, plugins, and extensions. ### Actual Behavior Currently, the official documentation includes a Migration Guide: 0.4 → 0.5, but there is no migration guide for 0.5 → 0.6. When upgrading to version 0.6.x, many tools, functions, and imports no longer work due to breaking changes in the API and plugin structure. Without documentation, it is unclear what needs to be modified to make custom tools and extensions compatible. ### Steps to Reproduce Have a working OpenWebUI 0.5.x instance with custom tools, plugins, or extensions. Upgrade to OpenWebUI 0.6.x (latest 0.6.32 tested). Try importing or running the same custom tools or functions. Observe that many imports fail (e.g., libraries, plugin hooks, functions no longer recognized). Look for migration guidance in the docs → only 0.4 → 0.5 guide exist ### Logs & Screenshots <img width="1832" height="660" alt="Image" src="https://github.com/user-attachments/assets/c38d1e9b-4bfa-4464-a799-b831772579d0" /> ### Additional Information _No response_

yindo added the documentation enhancement labels 2026-02-15 17:15:01 -05:00

yindo commented

2026-02-15 17:15:01 -05:00