N8N chat input not working

Questions
1

Hey I need help. After updating N8N today, my chat input is no longer working. It has shrunk in width with the submit button right below it. Any body else facing the same issue?

2

Can you confirm the exact version number (n8n --version) or in the configuration UI?

You can also do the following:
1- Suggest reloading with Ctrl+F5 or clearing the cache.
2- Check for errors in the browser console (F12 → Console).

3

screenshot
screenshot1614×903 22.6 KB

Thanks for your quick response to my issue. I’ve attache an image to show the issue with my chat input width. (See bottom) Also this is the error I get in my browser console…content script loaded
webcomponents-ce.js:33 Uncaught Error: A custom element with name ‘mce-autosize-textarea’ has already been defined.
at Aa (webcomponents-ce.js:33:363)
at m.define (webcomponents-ce.js:33:133)
at overlay_bundle.js:147:5559
at D (overlay_bundle.js:44:680)
at overlay_bundle.js:159:4

4

Thanks for sharing the screenshot and the console error, @athompson.

It looks like a conflict where the mce-autosize-textarea component is being defined multiple times, which breaks the chat input layout.

Here are some things you can try:
1- Open n8n in incognito mode or temporarily disable extensions (such as Grammarly or form plugins).
2- If you’re using any customizations on the frontend, make sure you don’t define that component more than once.
3- If you’re using n8n Cloud or standard Docker, it may be a bug in the latest version. In that case, you can open an issue, or we can help you report it.

Could you confirm which exact version of n8n you’re using and whether it’s n8n Cloud or self-hosted?

5

Thank you for the prompt response.

  • I am running n8n self-hosted (not n8n Cloud), version 1.98.2 (latest stable as of June 2025)123.
  • I’ve already tried incognito mode and disabling all browser extensions, but the error persists.
  • I have also uninstalled all community plugins and disabled all workflows, but the error still appears.
  • There are no custom frontend modifications or custom scripts in my setup.
  • I’m running n8n in Docker using the official image, with a clean n8n-data volume.

Given all this, it seems likely this is a bug in the latest version or a conflict in the core n8n codebase.
Please advise if there is a workaround, or if I should open an issue on GitHub for further investigation.

Thank you!

6

Quick Question. How long would it take to fix this issue?