[GH-ISSUE #22672] feat: Support :::writing blocks for OpenAI Chat models #35313

New Issue

GiteaMirror · 2026-04-25T09:32:54-05:00

GiteaMirror commented

2026-04-25 09:32:54 -05:00

Originally created by @ufozone on GitHub (Mar 14, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22672

Check Existing Issues

I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

Newer OpenAI chat models (e.g. gpt-5.3-chat-latest) can return standalone writing artifacts wrapped in a :::writing block:

:::writing
Text
:::

These blocks are intended to clearly separate content that can be reused outside the chat (e.g. letters, posts, documentation, stories).

Currently, Open WebUI does not recognize or format these blocks. They are displayed as plain text including the :::writing markers, which reduces readability and makes the content look like unformatted output instead of a structured text block.

Desired Solution you'd like

Open WebUI should add native support for the :::writing block format.

When a response contains:

:::writing
...
:::

the UI should detect and render it as a formatted writing block, similar to how code blocks or other structured elements are handled.

Possible behavior:

Remove the :::writing markers from the visible output.
Render the content inside a visually distinct container (e.g. styled panel, quote block, or document-style layout).
Optionally provide a quick “copy text” action for the entire block.

This would improve readability and ensure compatibility with newer OpenAI chat model output formats.

Alternatives Considered

No response

Additional Context

Originally created by @ufozone on GitHub (Mar 14, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22672 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description Newer OpenAI chat models (e.g. `gpt-5.3-chat-latest`) can return standalone writing artifacts wrapped in a `:::writing` block: ``` :::writing Text ::: ``` These blocks are intended to clearly separate content that can be reused outside the chat (e.g. letters, posts, documentation, stories). Currently, Open WebUI does not recognize or format these blocks. They are displayed as plain text including the `:::writing` markers, which reduces readability and makes the content look like unformatted output instead of a structured text block. ### Desired Solution you'd like Open WebUI should add native support for the `:::writing` block format. When a response contains: ``` :::writing ... ::: ``` the UI should detect and render it as a formatted writing block, similar to how code blocks or other structured elements are handled. Possible behavior: - Remove the `:::writing` markers from the visible output. - Render the content inside a visually distinct container (e.g. styled panel, quote block, or document-style layout). - Optionally provide a quick “copy text” action for the entire block. This would improve readability and ensure compatibility with newer OpenAI chat model output formats. ### Alternatives Considered _No response_ ### Additional Context <img width="991" height="586" alt="Image" src="https://github.com/user-attachments/assets/ed516b83-3ceb-4a3d-98e5-05633ab05e99" />

GiteaMirror closed this issue

2026-04-25 09:32:55 -05:00

GiteaMirror commented

2026-04-25 09:32:57 -05:00

@tjbck commented on GitHub (Mar 21, 2026):

Addressed in dev.

@tjbck commented on GitHub (Mar 21, 2026): Addressed in dev.

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#35313