2062 Commits

• refac
  Timothy Jaeryang Baek · 2026-11-15 16:56:45 +09:00
  31ef2064da
• fix: terminal files fail to load on a Tether reconnect instead of being retried (#34396)

  When the computer connected through Tether reconnected while the terminal's files panel was loading its working folder, a folder listing or a file, the load failed with "Tether connection interrupted". Reads like these are meant to be retried once Tether is back. They never were, because each of them went out with an empty upload attached, and an upload cannot be sent a second time. Requests with nothing to upload now go without one, so these reads are retried on the new connection. Uploads work as before.
  
  Fixes #34394

  Classic298 · 2026-11-14 06:40:44 +09:00
  7a73f1960f
• refac
  Timothy Jaeryang Baek · 2026-11-14 01:15:47 +09:00
  694dc9796c
• refac
  Timothy Jaeryang Baek · 2026-11-14 00:45:43 +09:00
  6378f94a65
• refac
  Timothy Jaeryang Baek · 2026-11-13 23:50:28 +09:00
  f1d735d807
• refac
  Timothy Jaeryang Baek · 2026-11-13 22:40:53 +09:00
  06491f0132
• refac
  Timothy Jaeryang Baek · 2026-11-13 17:36:00 +09:00
  4720ff19e7
• refac
  Timothy Jaeryang Baek · 2026-11-12 22:17:23 +09:00
  c67d774d71
• fix: Browser tab in Chrome mode keeps reconnecting when its chat is open in two windows (#34133)

  * fix: Browser tab in Chrome mode keeps reconnecting when its chat is open in two windows
  
  With the same chat open in two windows, the terminal hands the Chrome tab to the newer window, but the older window only saw a lost connection. It reconnected and took the tab back, so both windows kept flipping to "Reconnecting…" and the "Browser opened in another viewer." message never showed. The terminal's reason for ending the tab's connection now reaches the page, as it already does for the shell. The window that lost the tab shows that message and stops, and the other window keeps the page.
  
  Fixes #34095
  
  * fix: Browser tab in Chrome mode keeps reconnecting when its chat is open in two windows
  
  Narrows the change to passing the terminal's close reason on to the page. The relay's existing handling of a broken connection stays as it was.

  Classic298 · 2026-11-12 22:00:12 +09:00
  408e89d7e8
• refac
  Timothy Jaeryang Baek · 2026-11-12 21:28:52 +09:00
  edecad351b
• refac
  Timothy Jaeryang Baek · 2026-11-12 13:39:35 +09:00
  2547992b8a
• feat: permission to limit sub-agents to specific users and groups (#34040)

  Sub-agents could only be switched on or off for the whole instance, so once they were on every user could spawn them and an admin had no way to keep the extra model usage to a pilot group. The user permissions now have a Sub-agents switch under Features, both in the default permissions and in each group, next to Memories and working the same way. Users without the permission no longer get the sub-agent tool in their chats, nor the timer tool that is part of the same feature. Admins are not restricted by it, and with sub-agents off in Admin Settings nobody gets them, admins included. The permission is on by default, so existing instances behave as before until an admin turns it off; the default can also be set with the USER_PERMISSIONS_FEATURES_SUBAGENTS environment variable.
  
  Closes #34038

  Classic298 · 2026-11-11 10:11:30 +09:00
  2c8fa823f3
• refac
  Timothy Jaeryang Baek · 2026-11-10 23:38:17 +09:00
  c647f3f42e
• refac
  Timothy Jaeryang Baek · 2026-11-10 23:02:00 +09:00
  2975bf8e42
• refac
  Timothy Jaeryang Baek · 2026-11-10 22:56:33 +09:00
  f4cf2ca0c7
• refac
  Timothy Jaeryang Baek · 2026-11-10 21:18:18 +09:00
  6f2fc7bc7a
• refac
  Timothy Jaeryang Baek · 2026-11-10 13:05:45 +09:00
  98f94057bb
• refac
  Timothy Jaeryang Baek · 2026-11-10 12:13:49 +09:00
  354c652fc9
• refac
  Timothy Jaeryang Baek · 2026-11-09 16:04:13 +09:00
  553b18a34d
• refac
  Timothy Jaeryang Baek · 2026-11-09 15:55:13 +09:00
  62849662d9
• refac
  Timothy Jaeryang Baek · 2026-11-09 15:54:43 +09:00
  54593dadd5
• refac
  Timothy Jaeryang Baek · 2026-11-09 15:35:53 +09:00
  537e223ede
• refac
  Timothy Jaeryang Baek · 2026-11-08 21:57:07 +09:00
  21fc016141
• Merge pull request #33929 from Classic298/fix-chat-view-disconnect-log

  fix: error traceback in the log when a chat's layout save is dropped

  Classic298 · 2026-11-08 21:14:48 +09:00
  494e2790af
• refac
  Timothy Jaeryang Baek · 2026-11-08 19:06:43 +09:00
  9b9bea514d
• refac

  Co-Authored-By: Classic298 <27028174+Classic298@users.noreply.github.com>

  Timothy Jaeryang Baek · 2026-11-08 19:00:46 +09:00
  c1a9306397
• refac
  Timothy Jaeryang Baek · 2026-11-08 18:37:29 +09:00
  e8c0ad85e5
• refac
  Timothy Jaeryang Baek · 2026-11-08 15:27:19 +09:00
  2416b1fc0b
• refac
  Timothy Jaeryang Baek · 2026-11-08 12:56:55 +09:00
  2a0e0100bf
• feat: optional size limit for chat history tool results (#33695)

  * feat: optional size limit for chat history tool results
  
  Reading a long earlier chat through the Chat History tools could return far more text than a model's context window holds, so the next request failed. Admins can now set VIEW_CHAT_MAX_CHARS to cap what is returned. The newest messages are kept, older ones are dropped, and the result says it was cut and how many messages came back. Unset keeps the full chat as before.
  
  Fixes #33608
  
  * feat: set the chat read limit from the admin settings
  
  The limit on how much of an earlier chat a model can read could only be set with an environment variable. It is now a Chat Read Limit field in Admin Settings under General, next to the skill limits. The environment variable still works as the starting value, and the setting saved in the panel takes precedence.
  
  * fix: chat read limit failing on chats with empty or non-text messages
  
  With a chat read limit set, reading an imported chat that held empty or non-text message content ended in an error instead of the chat. Such content is now counted and cut as plain text.

  Classic298 · 2026-11-08 12:10:18 +09:00
  749dc4dbae
• refac
  Timothy Jaeryang Baek · 2026-11-08 12:08:18 +09:00
  07029af63d
• fix: saving a chat's view answers signed-out and pending accounts with "Invalid chat view" (#33885)

  Saving a chat's view (the per-chat display state the app stores) looked at the request before it checked who was sending it. A signed-out client or a pending account sending broken data got "Invalid chat view" instead of being refused, unlike everywhere else that needs a signed-in user, and the server read up to 1 MB of data for callers it would turn away anyway. The caller is now checked first, so they get the usual 401 Unauthorized. Signed-in users see no change.
  
  Fixes #33883

  Classic298 · 2026-11-08 10:47:00 +09:00
  00360d7020
• fix: OpenAI image generation with no model set asks GPT image models for base64 output (#33875)

  With the OpenAI image engine and the Model field left empty, requests go out for gpt-image-2 but still ask for base64 output, a parameter OpenAI does not support for GPT image models. Typing gpt-image-2 into the Model field already left it out. Whether that parameter is sent now depends on the model the request actually uses, so the empty default and the named model send the same request, and an image edit request that names its own model is handled the same way.
  
  Fixes #33874

  Classic298 · 2026-11-08 10:43:04 +09:00
  d2a8374f3a
• refac
  Timothy Jaeryang Baek · 2026-11-08 01:44:08 +09:00
  003299641e
• fix: autocompletion no longer fails while typing in a chat with a terminal model (#33857)
  G30 · 2026-11-07 23:07:57 +09:00
  e1aa2e30f7
• fix: terminal connection closed before login no longer logs an error (#33863)

  When the file panel or terminal view closes its live connection right after opening it, the server logged a full error traceback for a client that was already gone. Such a connection is now dropped quietly. Real authentication failures still close with the same error as before.
  
  Fixes #33850

  Classic298 · 2026-11-07 23:07:19 +09:00
  ac45fc0fcc
• refac: limit size of version history diffs (#33865)

  Diffing two versions of a skill, tool, function or prompt now refuses inputs above 5000 lines per version. All four history diff views share the same check.

  Classic298 · 2026-11-07 23:06:56 +09:00
  77959080e3
• refac
  Timothy Jaeryang Baek · 2026-11-07 21:32:04 +09:00
  c31cdb4e86
• refac
  Timothy Jaeryang Baek · 2026-11-07 20:31:42 +09:00
  d4e8493cc5
• refac
  Timothy Jaeryang Baek · 2026-11-07 19:50:51 +09:00
  7d4dda2704
• refac
  Timothy Jaeryang Baek · 2026-11-07 13:13:27 +09:00
  99dd6a356b
• feat: client IP placeholders for connection custom headers (#33833)

  Connection custom headers had no way to tell the upstream provider which client a request came from. Adding {{USER_IP}} and {{X_FORWARDED_FOR}} fills in the client address Open WebUI resolves for the request, for example {"X-Real-IP": "{{USER_IP}}"}. Both are empty when there is no client request, such as automations and background jobs. Headers that don't use them are unaffected.
  
  Fixes #33819

  Classic298 · 2026-11-07 11:38:59 +09:00
  d39cb17b97
• refac
  Timothy Jaeryang Baek · 2026-11-06 14:37:15 +09:00
  6da3e7a5d6
• refac
  Timothy Jaeryang Baek · 2026-11-06 13:40:53 +09:00
  18f7633afa
• refac
  Timothy Jaeryang Baek · 2026-11-06 13:23:52 +09:00
  6f4c7f8935
• refac
  Timothy Jaeryang Baek · 2026-11-06 12:40:49 +09:00
  0f3bd0a7ea
• refac
  Timothy Jaeryang Baek · 2026-11-06 11:12:04 +09:00
  bd6fc15bee
• refac
  Timothy Jaeryang Baek · 2026-11-06 10:27:47 +09:00
  98f7a6146e
• refac: skip background work for accounts that were deactivated meanwhile (#33801)

  Follow-up generation after a response and replies to channel mentions are now skipped when the account that triggered them has been deactivated in the meantime.

  Classic298 · 2026-11-06 07:53:32 +09:00
  dd42f4e913
• refac
  Timothy Jaeryang Baek · 2026-11-05 20:47:26 +09:00
  bb89844517