[PR #20909] [CLOSED] feat(functions): Add "Neural Log" Visualizer for Reasoning Models (DeepSeek R1) #48872

Closed
opened 2026-04-30 01:04:16 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/20909
Author: @sjhddh
Created: 1/23/2026
Status: Closed

Base: devHead: feat/deepseek-r1-neural-log-dev


📝 Commits (1)

  • f6cda04 feat(functions): Add DeepSeek R1 Neural-Log Visualizer

📊 Changes

1 file changed (+116 additions, -0 deletions)

View changed files

examples/filters/r1_neural_log.py (+116 -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. Not targeting the dev branch will lead to immediate closure of the PR.
  • 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: If necessary, update relevant documentation Open WebUI Docs like environment variables, the tutorials, or other documentation sources.
  • Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
  • Testing: Perform manual tests to verify the implemented fix/feature works as intended AND does not break any other functionality. Take this as an opportunity to make screenshots of the feature/fix and include it 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?
  • Title Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
    • feat: Introduces a new feature or enhancement to the codebase

Changelog Entry

Description

This PR introduces a new Function/Filter (examples/filters/r1_neural_log.py) designed to enhance the Developer Experience (DX) when working with reasoning models like DeepSeek R1.

Problem:
Reasoning models output their internal thought process within <think> tags. Currently, this is displayed as raw text or hidden, making it difficult to distinguish between the "reasoning trace" and the final answer.

Solution:
The Neural Log Visualizer intercepts these tags and transforms the content into a stylized "System Log" or "Cyberpunk Terminal" block. This visual separation allows users to inspect the logic chain without it cluttering the final response.

Added

  • examples/filters/r1_neural_log.py: A new filter that visualizes <think> tags as a styled terminal log.
  • Features:
    • Automatic Interception: Detects <think> tags (even if unclosed during streaming).
    • Theming: Includes "Cyberpunk", "Matrix", and "Minimalist" themes configurable via Valves.
    • Log Simulation: Adds pseudo-timestamps and status prefixes (e.g., [NEURAL]) to each line of reasoning.

Additional Information

This filter is implemented as a standalone Python file in the examples/filters directory and does not modify core system files. It is intended to be used via the Functions interface.

Screenshots or Videos

(Description of the visual effect)
The output replaces the raw <think>...</think> content with a Markdown code block (language: log or bash).
The block contains a "Boot Sequence" header (e.g., > INITIALIZING NEURAL PATHWAYS...) followed by the reasoning text, where each line is prefixed with a timestamp and a status tag (e.g., [00:00:01.450] [NEURAL] ...).

Testing Confirmation

You have personally tested ALL changes in this PR
I have manually tested this filter by:

  1. Adding the r1_neural_log.py code to the Functions interface in a local Open WebUI instance.
  2. Enabling the filter globally.
  3. Chatting with a model that outputs <think> tags (simulated and actual DeepSeek R1 output).
  4. Verifying that the <think> content is correctly intercepted and formatted into the code block.
  5. Verifying that the final response (outside the tags) remains untouched.
  6. Toggling the filter off via Valves to ensure it passes through content unchanged.

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/20909 **Author:** [@sjhddh](https://github.com/sjhddh) **Created:** 1/23/2026 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `feat/deepseek-r1-neural-log-dev` --- ### 📝 Commits (1) - [`f6cda04`](https://github.com/open-webui/open-webui/commit/f6cda04a0db2bf7bc264773599f48770fd248423) feat(functions): Add DeepSeek R1 Neural-Log Visualizer ### 📊 Changes **1 file changed** (+116 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `examples/filters/r1_neural_log.py` (+116 -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. **Not targeting the `dev` branch will lead to immediate closure of the PR.** - [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. - [ ] **Documentation:** If necessary, update relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs) like environment variables, the tutorials, or other documentation sources. - [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [x] **Testing:** Perform manual tests to **verify the implemented fix/feature works as intended AND does not break any other functionality**. Take this as an opportunity to **make screenshots of the feature/fix and include it 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] **Title Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **feat**: Introduces a new feature or enhancement to the codebase # Changelog Entry ### Description This PR introduces a new Function/Filter (`examples/filters/r1_neural_log.py`) designed to enhance the Developer Experience (DX) when working with reasoning models like DeepSeek R1. **Problem:** Reasoning models output their internal thought process within `<think>` tags. Currently, this is displayed as raw text or hidden, making it difficult to distinguish between the "reasoning trace" and the final answer. **Solution:** The **Neural Log Visualizer** intercepts these tags and transforms the content into a stylized "System Log" or "Cyberpunk Terminal" block. This visual separation allows users to inspect the logic chain without it cluttering the final response. ### Added - `examples/filters/r1_neural_log.py`: A new filter that visualizes `<think>` tags as a styled terminal log. - Features: - **Automatic Interception:** Detects `<think>` tags (even if unclosed during streaming). - **Theming:** Includes "Cyberpunk", "Matrix", and "Minimalist" themes configurable via Valves. - **Log Simulation:** Adds pseudo-timestamps and status prefixes (e.g., `[NEURAL]`) to each line of reasoning. --- ### Additional Information This filter is implemented as a standalone Python file in the `examples/filters` directory and does not modify core system files. It is intended to be used via the Functions interface. ### Screenshots or Videos *(Description of the visual effect)* The output replaces the raw `<think>...</think>` content with a Markdown code block (language: `log` or `bash`). The block contains a "Boot Sequence" header (e.g., `> INITIALIZING NEURAL PATHWAYS...`) followed by the reasoning text, where each line is prefixed with a timestamp and a status tag (e.g., `[00:00:01.450] [NEURAL] ...`). ### Testing Confirmation ✅ **You have personally tested ALL changes in this PR** I have manually tested this filter by: 1. Adding the `r1_neural_log.py` code to the Functions interface in a local Open WebUI instance. 2. Enabling the filter globally. 3. Chatting with a model that outputs `<think>` tags (simulated and actual DeepSeek R1 output). 4. Verifying that the `<think>` content is correctly intercepted and formatted into the code block. 5. Verifying that the final response (outside the tags) remains untouched. 6. Toggling the filter off via Valves to ensure it passes through content unchanged. ### 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-04-30 01:04:17 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#48872