c676303 enh: automatically remove incorrect backticks before code_interpreter tags
74b971b refac: clean up solution for correcting code_interpreter backticks
📊 Changes
1 file changed (+18 additions, -0 deletions)
View changed files
📝backend/open_webui/utils/middleware.py (+18 -0)
📄 Description
Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:
Target branch: Please verify that the pull request targets the dev branch.
Description: Provide a concise description of the changes made in this pull request.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Have you written and run sufficient tests for validating the changes?
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?
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
When Code Interpreter is activated, sometimes the LLM prefixes its call to <code_interpreter> with an opening code block (triple back ticks). This is not how it is supposed to work, as it will cause breakage in the visual markdown rendering of the Code Interpreter block. When the LLM makes this kind of mistake, we can automatically correct it by removing any OPENING code blocks. Note that we know it is an OPENING block by counting the sets of back ticks.
Added
None
Changed
None
Deprecated
None
Removed
None
Fixed
Improve reliability of Code Interpreter visual format rendering by removing invalid opening back ticks before each Code Interpreter block
Security
None
Breaking Changes
None
Additional Information
None
Screenshots or Videos
Before:
After:
🔄 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/9463
**Author:** [@roryeckel](https://github.com/roryeckel)
**Created:** 2/6/2025
**Status:** ✅ Merged
**Merged:** 2/6/2025
**Merged by:** [@tjbck](https://github.com/tjbck)
**Base:** `dev` ← **Head:** `cleanup-code-interpreter-markdown`
---
### 📝 Commits (2)
- [`c676303`](https://github.com/open-webui/open-webui/commit/c676303a55b9c78800efbd7fd70c84b4ccc356ed) enh: automatically remove incorrect backticks before code_interpreter tags
- [`74b971b`](https://github.com/open-webui/open-webui/commit/74b971b88861b26c9be76cd11c068de4336187b0) refac: clean up solution for correcting code_interpreter backticks
### 📊 Changes
**1 file changed** (+18 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `backend/open_webui/utils/middleware.py` (+18 -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) and describe your changes before submitting a pull request.
**Before submitting, make sure you've checked the following:**
- [x] **Target branch:** Please verify that the pull request targets the `dev` branch.
- [x] **Description:** Provide a concise description of the changes made in this pull request.
- [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.
- [ ] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources?
- [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation?
- [ ] **Testing:** Have you written and run sufficient tests for validating the changes?
- [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] **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
- When Code Interpreter is activated, sometimes the LLM prefixes its call to <code_interpreter> with an opening code block (triple back ticks). This is not how it is supposed to work, as it will cause breakage in the visual markdown rendering of the Code Interpreter block. When the LLM makes this kind of mistake, we can automatically correct it by removing any OPENING code blocks. Note that we know it is an OPENING block by counting the sets of back ticks.
### Added
- None
### Changed
- None
### Deprecated
- None
### Removed
- None
### Fixed
- Improve reliability of Code Interpreter visual format rendering by removing invalid opening back ticks before each Code Interpreter block
### Security
- None
### Breaking Changes
- None
---
### Additional Information
- None
### Screenshots or Videos
**Before:**
**After:**
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/open-webui/open-webui/pull/9463
Author: @roryeckel
Created: 2/6/2025
Status: ✅ Merged
Merged: 2/6/2025
Merged by: @tjbck
Base:
dev← Head:cleanup-code-interpreter-markdown📝 Commits (2)
c676303enh: automatically remove incorrect backticks before code_interpreter tags74b971brefac: clean up solution for correcting code_interpreter backticks📊 Changes
1 file changed (+18 additions, -0 deletions)
View changed files
📝
backend/open_webui/utils/middleware.py(+18 -0)📄 Description
Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:
devbranch.Changelog Entry
Description
Added
Changed
Deprecated
Removed
Fixed
Security
Breaking Changes
Additional Information
Screenshots or Videos
Before:
After:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.