[BUG] Smart Mind Map no longer works on OWUI v0.10+

[Nordln]

Plugin Type

Action

Plugin Name

Action - Smart Mind Map

Plugin Name (if not in list)

No response

Description

Starting the action on chat produces the following error:
No content found to export!

Steps to Reproduce

1. Generate a model responce
2. Click MM action icon

OpenWebUI Version

10

Operating System & Container

MacOS with LimaVM running Ubuntu, then the OWUI container via containerd

Error Logs (Optional)

JS Console:

warnings.js:84 https://svelte.dev/e/derived_inert
derived_inert @ warnings.js:84
execute_derived @ deriveds.js:350
update_derived @ deriveds.js:393
get @ runtime.js:673
root @ dom-context.svelte.js:5
(anonymous) @ dom-context.svelte.js:20
(anonymous) @ link-preview.svelte.js:49
setTimeout
(anonymous) @ after-sleep.js:5
(anonymous) @ link-preview.svelte.js:48
(anonymous) @ events.js:67
without_reactive_context @ shared.js:45
target_handler @ events.js:66
Chat.svelte:1796 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'content')
    at Se (Chat.svelte:1796:37)
    at async V (Messages.svelte:427:3)


Docker log

2026-06-30 09:13:54.026 | INFO     | function_smart_mind_map:action:2456 - Action: Smart Mind Map (v1.0.1) started
2026-06-30 09:13:54.064 | INFO     | uvicorn.protocols.http.httptools_impl:send:483 - 138.232.11.38:0 - "POST /api/chat/actions/smart_mind_map HTTP/1.1" 200

Additional Information (Optional)

No response

Checklist

• I have searched for duplicate issues
• I have provided clear reproduction steps
• I have mentioned OpenWebUI version and OS/container info

[Fu-Jie]

Thanks for the detailed report — I was able to reproduce and root-cause this against the current OpenWebUI main (v0.10.x) source.

What's happening

The crash happens after the plugin returns, in the OWUI v0.10 frontend (chatActionHandler in Chat.svelte). When the action finishes, the frontend iterates every message returned in body["messages"] and looks each one up by id:

history.messages[message.id] = {
    ...history.messages[message.id],
    ...(history.messages[message.id].content !== message.content   // ← line 1796, throws here
        ? { originalContent: history.messages[message.id].content }
        : {}),
    ...message
};

The plugin's early-return paths (when there's no extractable text in the last assistant message, or the text is too short) used to append a new message without an id:

body["messages"].append({"role": "assistant", "content": "❌ ..."})

So message.id was undefined → history.messages[undefined] was undefined → accessing .content threw Cannot read properties of undefined (reading 'content'). That matches your Docker log exactly: HTTP 200 in ~38 ms with no LLM call — an early-return path was hit.

The "No content found to export!" message you saw is the plugin's error_no_content notification, i.e. the last assistant message had no extractable text content at the moment the action ran.

Fix

PR #102 updates the existing last message's content (which already carries a valid id) instead of appending a new id-less message. The frontend preserves the original content as originalContent before applying the update, so nothing is lost. Version bumped to 1.0.2.

→ #102

Could you verify?

Please reinstall the plugin from the fix/issue-101-mindmap-v10 branch (or wait until the PR is merged and pull main) and retry on OWUI v0.10+:

1. The frontend crash should be gone.
2. If you still see the "No content found to export!" notification (without a crash), that's a separate content-availability question — e.g. the model response being too short, or stored in OWUI's new structured-output (output array) format rather than plain content. If so, please share the model you used and a sample assistant reply so I can extend the content extraction.

I'll keep this issue open until you confirm. Won't close it preemptively.

[Nordln]

Thanks for the quick responce. V1.0.2 works as expected. Great stuff.

I guess the same fix would apply to the MSWord doc creation action also?

[Fu-Jie]

Update — the fix now covers a second layer of the bug I missed initially (thanks to @rbb-dev's PR #103 which fixed the same root cause for export_to_excel / export_to_docx).

What I missed in v1.0.2

v1.0.2 stopped the frontend crash, but on OWUI v0.10+ the action would still report "No content found to export!" on a perfectly valid reply. That's because OWUI v0.10+ moved assistant replies to a structured output field and leaves the flat content empty — the plugin's content extraction saw an empty content and bailed out. So the action wasn't actually usable, it just failed gracefully instead of crashing.

v1.0.3 (just pushed to PR #102)

Now recovers the assistant text from the structured output, using OWUI's own APIs (same approach as @rbb-dev's PR #103):

• convert_output_to_messages(output) rebuilds the text (reasoning excluded)
• Falls back to ChatMessages.get_message_by_id(chat_id-message_id) DB lookup when output isn't carried on the payload
• Guarded imports — on pre-v0.10 OWUI the recovery silently no-ops and the original content-only path runs unchanged (no breakage)

Could you re-verify?

Please reinstall from PR #102 (branch fix/issue-101-mindmap-v10, now v1.0.3) and retry on OWUI v0.10+:

1. No frontend crash ✅
2. The mind map should now actually generate from a normal assistant reply (not "No content found to export!")

→ #102

Still keeping this issue open until you confirm. cc @rbb-dev in case you want to coordinate the required_open_webui_version declaration — I deliberately did not add it here, because the guarded imports keep Smart Mind Map working on older OWUI too.

[rbb-dev]

OWUI 0.10.x fixes multiple security vulnerabilities that are not public yet.
I would not run anything less than 0.10.2 right now,
Check "Fixes" in the changelog.

[Nordln]

Retested mindmap v1.0.3 on OWUI v0.10.2.

I get a map render but the content is empty:

May previous test of 1.0.2 may also have produced the same output. I only registered that it output a map, not the contents of the map.

[Nordln]

Restarted the container for another reason and retested. This time, all was well:

[Fu-Jie]

Thanks for confirming @Nordln — glad it works on your end after the container restart. The earlier empty map was indeed the stale v1.0.2 cache (frontend crash fix only); the restart picked up the full fix including the structured-output content recovery.

PR #102 is now merged into main (squash commit 8b2ed0f) as Smart Mind Map v1.0.2, bundling both layers of the OWUI v0.10+ fix:

• Frontend crash on early-return paths (no more id-less message)
• Empty content recovered from the structured output field via OWUI's convert_output_to_messages + ChatMessages.get_message_by_id DB fallback
• required_open_webui_version: 0.10.2 declared; pre-v0.10 users can stay on v1.0.1

Also a shout-out to @rbb-dev — the structured-output recovery technique follows the approach from PR #103.

Closing this issue as resolved. Reopen if it resurfaces. ✅