[PR #21565] [CLOSED] fix: respect content edits and deleted blocks in output #113452

New Issue

GiteaMirror · 2026-05-18T13:50:07-05:00

GiteaMirror commented

2026-05-18 13:50:07 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/21565
Author: @Algorithm5838
Created: 2/18/2026
Status: ❌ Closed

Base: dev ← Head: fix/drop-output-for-removed-tool-calls

📝 Commits (1)

e4447f5 fix: respect content edits and deleted blocks in output

📊 Changes

2 files changed (+108 additions, -5 deletions)

View changed files

📝 backend/open_webui/utils/middleware.py (+42 -5)
📝 backend/open_webui/utils/misc.py (+66 -0)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.

This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.

Before submitting, make sure you've checked the following:

Target branch: Verify that the pull request targets the dev branch. PRs targeting main will be immediately closed.
Description: Provide a concise description of the changes made in this pull request down below.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: Add docs in Open WebUI Docs Repository. Document user-facing behavior, environment variables, public APIs/interfaces, or deployment steps.
Dependencies: Are there any new or upgraded dependencies? If so, explain why, update the changelog/docs, and include any compatibility notes. Actually run the code/function that uses updated library to ensure it doesn't crash.
Testing: Perform manual tests to verify the implemented fix/feature works as intended AND does not break any other functionality. Include reproducible steps to demonstrate the issue before the fix. Test edge cases (URL encoding, HTML entities, types). Take this as an opportunity to make screenshots of the feature/fix and include them in the PR description.
Agentic AI Code: Confirm this Pull Request is not written by any AI Agent or has at least gone through additional human review AND manual testing. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR.
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Design & Architecture: Prefer smart defaults over adding new settings; use local state for ephemeral UI logic. Open a Discussion for major architectural or UX changes.
Git Hygiene: Keep PRs atomic (one logical change). Clean up commits and rebase on dev to ensure no unrelated commits (e.g. from main) are included. Push updates to the existing PR branch instead of closing and reopening.
Title Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
- BREAKING CHANGE: Significant changes that may affect compatibility
- build: Changes that affect the build system or external dependencies
- ci: Changes to our continuous integration processes or workflows
- chore: Refactor, cleanup, or other non-functional code changes
- docs: Documentation update or addition
- feat: Introduces a new feature or enhancement to the codebase
- fix: Bug fix or error correction
- i18n: Internationalization or localization changes
- perf: Performance improvement
- refactor: Code restructuring for better maintainability, readability, or scalability
- style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- test: Adding missing tests or correcting existing tests
- WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

Deleting a <details> block from a message doesn't actually remove it from model context. The output field keeps the items regardless of what happens to content. This applies to tool calls, reasoning, and code interpreter blocks.

Shows up with things like a fetch tool that pulls large pages (50k+ tokens) where you'd delete the block to free up context, but the tokens stay. Or a custom thinking tool where a filter removes the tool block after the model finishes responding. This used to work before the output refactor.

Editing assistant message text also has no effect. The model still sees the old text because process_messages_with_output was pulling everything from output items, ignoring content entirely.

The fix: process_messages_with_output now uses content (stripped of <details> blocks) for text and only uses output for structured items. If an output item's ID is gone from content, it gets skipped. serialize_output now emits id= on reasoning and code_interpreter <details> tags (tool_calls already had it). Output stays in DB untouched, it just doesn't get sent to the model.

Added

filter_output_by_content() in misc.py

Changed

serialize_output emits id= on reasoning and code_interpreter <details> tags
process_messages_with_output filters output items by matching against content, and uses content (minus <details> blocks) as assistant text

Deprecated

[List any deprecated functionality or features that have been removed]

Removed

[List any removed features, files, or functionalities]

Fixed

Deleting any <details> block (tool call, reasoning, code interpreter) now removes it from model context
Editing assistant message text is respected

Security

[List any new or updated security-related changes, including vulnerability fixes]

Breaking Changes

BREAKING CHANGE: [List any breaking changes affecting compatibility or functionality]

Additional Information

[Insert any additional context, notes, or explanations for the changes]
- [Reference any related issues, commits, or other relevant information]

Screenshots or Videos

[Attach any relevant screenshots or videos demonstrating the changes]

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

Note

Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/21565 **Author:** [@Algorithm5838](https://github.com/Algorithm5838) **Created:** 2/18/2026 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `fix/drop-output-for-removed-tool-calls` --- ### 📝 Commits (1) - [`e4447f5`](https://github.com/open-webui/open-webui/commit/e4447f5262c0bda0857ee93cafe09a9483455498) fix: respect content edits and deleted blocks in output ### 📊 Changes **2 files changed** (+108 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/utils/middleware.py` (+42 -5) 📝 `backend/open_webui/utils/misc.py` (+66 -0) </details> ### 📄 Description  # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request. This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR. **Before submitting, make sure you've checked the following:** - [x] **Target branch:** Verify that the pull request targets the `dev` branch. **PRs targeting `main` will be immediately closed.** - [x] **Description:** Provide a concise description of the changes made in this pull request down below. - [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [x] **Documentation:** Add docs in [Open WebUI Docs Repository](https://github.com/open-webui/docs). Document user-facing behavior, environment variables, public APIs/interfaces, or deployment steps. - [x] **Dependencies:** Are there any new or upgraded dependencies? If so, explain why, update the changelog/docs, and include any compatibility notes. Actually run the code/function that uses updated library to ensure it doesn't crash. - [x] **Testing:** Perform manual tests to **verify the implemented fix/feature works as intended AND does not break any other functionality**. Include reproducible steps to demonstrate the issue before the fix. Test edge cases (URL encoding, HTML entities, types). Take this as an opportunity to **make screenshots of the feature/fix and include them in the PR description**. - [x] **Agentic AI Code:** Confirm this Pull Request is **not written by any AI Agent** or has at least **gone through additional human review AND manual testing**. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR. - [x] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [x] **Design & Architecture:** Prefer smart defaults over adding new settings; use local state for ephemeral UI logic. Open a Discussion for major architectural or UX changes. - [x] **Git Hygiene:** Keep PRs atomic (one logical change). Clean up commits and rebase on `dev` to ensure no unrelated commits (e.g. from `main`) are included. Push updates to the existing PR branch instead of closing and reopening. - [x] **Title Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description Deleting a `<details>` block from a message doesn't actually remove it from model context. The `output` field keeps the items regardless of what happens to content. This applies to tool calls, reasoning, and code interpreter blocks. Shows up with things like a fetch tool that pulls large pages (50k+ tokens) where you'd delete the block to free up context, but the tokens stay. Or a custom thinking tool where a filter removes the tool block after the model finishes responding. This used to work before the output refactor. Editing assistant message text also has no effect. The model still sees the old text because `process_messages_with_output` was pulling everything from output items, ignoring content entirely. The fix: `process_messages_with_output` now uses content (stripped of `<details>` blocks) for text and only uses output for structured items. If an output item's ID is gone from content, it gets skipped. `serialize_output` now emits `id=` on reasoning and code_interpreter `<details>` tags (tool_calls already had it). Output stays in DB untouched, it just doesn't get sent to the model. ### Added - `filter_output_by_content()` in `misc.py` ### Changed - `serialize_output` emits `id=` on `reasoning` and `code_interpreter` `<details>` tags - `process_messages_with_output` filters output items by matching against content, and uses `content` (minus `<details>` blocks) as assistant text ### Deprecated - [List any deprecated functionality or features that have been removed] ### Removed - [List any removed features, files, or functionalities] ### Fixed - Deleting any `<details>` block (tool call, reasoning, code interpreter) now removes it from model context - Editing assistant message text is respected ### Security - [List any new or updated security-related changes, including vulnerability fixes] ### Breaking Changes - **BREAKING CHANGE**: [List any breaking changes affecting compatibility or functionality] --- ### Additional Information - [Insert any additional context, notes, or explanations for the changes] - [Reference any related issues, commits, or other relevant information] ### Screenshots or Videos - [Attach any relevant screenshots or videos demonstrating the changes] ### Contributor License Agreement  By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. > [!NOTE] > Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-05-18 13:50:07 -05:00

GiteaMirror closed this issue

2026-05-18 13:50:09 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#113452