713 Commits

• refac
  Timothy Jaeryang Baek · 2026-11-15 16:56:45 +09:00
  31ef2064da
• refac
  Timothy Jaeryang Baek · 2026-11-14 14:16:19 +09:00
  d7b3d08b4f
• fix: a tag's chosen color shows in a folder's filter menu, group headers and board columns (#34390)
  G30 · 2026-11-14 06:41:02 +09:00
  0cce86d535
• refac
  Timothy Jaeryang Baek · 2026-11-14 00:45:43 +09:00
  6378f94a65
• refac
  Timothy Jaeryang Baek · 2026-11-14 00:14:28 +09:00
  121bc0ec50
• 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
• feat: deleting an account removes the access grants that name it (#34223)
  G30 · 2026-11-13 19:03:00 +09:00
  44d2dd3d52
• fix: chat reopens on an older turn after an out-of-date window saves an edit (#34160)

  A window that had missed a turn, for example a laptop that just woke up and has not reconnected yet, saved its own, older idea of where the chat was when it saved an edited message. The chat then reopened on that older turn, and the next message started a new branch there, so the newest reply moved behind the branch switch and the model no longer saw it. A save now keeps the chat on the newest turn of the branch it is on, the same turn the chat already shows once it has caught up.
  
  Fixes #34126

  Classic298 · 2026-11-12 21:42:21 +09:00
  3d36b436c6
• refac
  Timothy Jaeryang Baek · 2026-11-11 13:49:51 +09:00
  28c5fba889
• refac
  Timothy Jaeryang Baek · 2026-11-10 17:22:51 +09:00
  b01fe7fae2
• refac
  Timothy Jaeryang Baek · 2026-11-10 15:56:52 +09:00
  da850248d1
• refac
  Timothy Jaeryang Baek · 2026-11-10 13:05:45 +09:00
  98f94057bb
• refac
  Timothy Jaeryang Baek · 2026-11-09 15:35:53 +09:00
  537e223ede
• refac
  Timothy Jaeryang Baek · 2026-11-08 21:15:39 +09:00
  6d3123b5b4
• refac
  Timothy Jaeryang Baek · 2026-11-08 19:06:43 +09:00
  9b9bea514d
• refac
  Timothy Jaeryang Baek · 2026-11-08 11:52:13 +09:00
  f0f4a24afa
• refac: limit the number of search words used for chat search (#33844)

  Chat search now uses at most the first 12 distinct words of the query.

  Classic298 · 2026-11-08 10:43:19 +09:00
  639766f7f9
• refac
  Timothy Jaeryang Baek · 2026-11-08 01:28:41 +09:00
  834c47ee02
• 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 20:31:42 +09:00
  d4e8493cc5
• chore: remove the Show Files on Terminal Select setting (#33855)
  G30 · 2026-11-07 16:47:42 +09:00
  def1d048bc
• refac
  Timothy Jaeryang Baek · 2026-11-06 13:40:53 +09:00
  18f7633afa
• perf: opening a chat no longer loads the whole conversation to mark it read (#33666)

  Every time a chat is opened, the server marks it as read, and to do so it loaded and parsed the full chat, images included, just to save the last-read time. Marking a chat as unread and removing a tag from a chat did the same. These now touch only the few chat fields they change, which makes them 4 to 6 times faster on large chats.
  
  Measured on SQLite, best of 7 runs, sizes are the chat as stored in the database:
  
  | Chat | Action | Before | After |
  | --- | --- | --- | --- |
  | 7 MB, text only | open (mark read) | 19.8 ms | 3.5 ms |
  | 7 MB, text only | mark as unread | 20.7 ms | 3.5 ms |
  | 7 MB, text only | remove tag | 21.2 ms | 3.4 ms |
  | 49 MB, with images | open (mark read) | 122.2 ms | 30.0 ms |
  | 49 MB, with images | mark as unread | 124.2 ms | 29.1 ms |
  | 49 MB, with images | remove tag | 120.5 ms | 28.6 ms |

  Classic298 · 2026-11-05 22:38:25 +09:00
  c165ee14f0
• refac
  Timothy Jaeryang Baek · 2026-11-05 22:38:02 +09:00
  7efb494a2b
• refac
  Timothy Jaeryang Baek · 2026-11-05 12:01:25 +09:00
  69189cbaad
• refac
  Timothy Jaeryang Baek · 2026-11-05 12:00:17 +09:00
  99f4541e3b
• refac
  Timothy Jaeryang Baek · 2026-11-05 11:41:25 +09:00
  404d27a36e
• refac: limit nesting depth of model settings (#33759)

  Model meta and params are now rejected when they are nested too deeply.

  Classic298 · 2026-11-05 07:19:09 +09:00
  051c357f98
• perf: channel message pages load much faster when many messages are replies (#33691)

  Opening a channel looked up every replied-to message one by one, so a page of 50 mostly-reply messages ran well over a hundred database queries. The replied-to messages and their authors are now fetched together, and the response is unchanged. Measured on a local SQLite database with a 50-message page where 46 messages are replies:
  
  | | before | after |
  |---|---|---|
  | queries | 147 | 3 |
  | time (median) | 46 ms | 1.9 ms |

  Classic298 · 2026-11-05 06:43:43 +09:00
  9f748cb5c9
• perf: channel list loads much faster with many channels (#33690)

  Opening the channel list ran several database queries for every channel, so the load time grew with the number of channels. The last message time, unread count, mute state and direct message participants are now fetched for all channels at once, so the number of queries stays the same no matter how many channels a user has. The response is unchanged.
  
  Measured on SQLite with an admin user in 23 visible channels (50 seeded), 2000 messages per channel:
  
  | | before | after |
  |---|---|---|
  | database queries | 93 | 9 |
  | response time | 255 ms | 47 ms |

  Classic298 · 2026-11-05 06:43:25 +09:00
  332f6a2586
• perf: chat access checks no longer load the whole conversation (#33667)

  Typing indicators, sending a message, shared links, comments and file access all check whether the user may access the chat, and each check loaded the full chat, images included, only to look at who owns it and which folder it is in. On large chats that delayed every other request on the same server process by up to a few hundred milliseconds per check. The check now reads just those few fields, and who gets access is unchanged.
  
  Measured on SQLite, best of 5 runs, sizes are the chat as stored in the database:
  
  | Chat | Checked for | Before | After |
  | --- | --- | --- | --- |
  | 7 MB, text only | the chat owner | 34.6 ms | 0.36 ms |
  | 7 MB, text only | a user with access through a shared folder | 35.1 ms | 2.58 ms |
  | 57 MB, with images | the chat owner | 249.8 ms | 0.72 ms |
  | 57 MB, with images | a user with access through a shared folder | 249.0 ms | 2.80 ms |

  Classic298 · 2026-11-04 05:33:17 +09:00
  323f7353bf
• chore: format
  Timothy Jaeryang Baek · 2026-11-03 17:36:03 +09:00
  0c64e5d596
• refac
  Timothy Jaeryang Baek · 2026-11-02 12:47:34 +09:00
  2840f0e07b
• refac
  Timothy Jaeryang Baek · 2026-11-02 12:45:15 +09:00
  ddb43c83ba
• refac
  Timothy Jaeryang Baek · 2026-11-02 11:37:00 +09:00
  789a0f402a
• refac
  Timothy Jaeryang Baek · 2026-11-02 08:48:51 +09:00
  d99ec1c02c
• refac
  Timothy Jaeryang Baek · 2026-10-31 16:50:01 +09:00
  3814b7b2f1
• refac
  Timothy Jaeryang Baek · 2026-10-30 16:01:47 +09:00
  9d1b4ef362
• refac
  Timothy Jaeryang Baek · 2026-10-30 07:08:28 +09:00
  7618df3f53
• refac
  Timothy Jaeryang Baek · 2026-10-29 17:39:31 +09:00
  44a9d499db
• perf: knowledge base changes slow down as the knowledge base grows (#33335)

  Adding, updating or removing knowledge base files through the API sent back the metadata of every file in the knowledge base, and so did renaming a knowledge base or changing its access. These calls got slower as the knowledge base grew, so bulk ingestion through the API lost speed with every batch. Adding or updating files now returns only those files, while removing a file, renaming or changing access returns an empty files list. API clients that read the files list from these responses now get only the affected files; the full list stays available, paginated, from `GET /api/v1/knowledge/{id}/files`. Timings with a local mock embedding server that answers instantly, median of 5 runs (at 1,000 files the per-file work of a batch still hides the difference):
  
  | Files already in the knowledge base | Call | Before | After | Response size before | Response size after |
  |---|---|---|---|---|---|
  | 1,000 | batch add of 100 files | 519 ms | 528 ms | 437 KB | 39 KB |
  | 10,000 | batch add of 100 files | 679 ms | 476 ms | 4.0 MB | 39 KB |
  | 10,000 | single file add | 184 ms | 36 ms | 4.0 MB | 0.6 KB |
  
  Closes #31397

  Classic298 · 2026-10-29 17:00:29 +09:00
  a59cab0aa9
• fix: member's chat loses its pin when the shared folder owner moves it (#33342)

  When the owner of a shared folder moved a chat a member created to another folder inside the shared folder, the chat lost the member's pin and dropped out of their Pinned list. The owner's move now keeps the member's pin, just as it already keeps the chat's unread status for them. Moving your own chat into a folder still unpins it, as before, so it shows up in that folder.
  
  Fixes #33341

  Classic298 · 2026-10-29 08:05:16 +09:00
  226dca18cd
• perf: kb_exec reads the full text of the whole knowledge base on every call (#33332)

  Every kb_exec command (ls, cat, grep and the rest) and the knowledge base sync check listed the knowledge base by loading each file's full extracted text, even though only names, folders, sizes and hashes were used. On large knowledge bases every call took seconds, held hundreds of MB of memory and blocked the server for other users while it ran. The listing now reads only those fields, and file text is still loaded per file when a command needs it, as before. Output is byte-identical.
  
  5,005 files (5,000 of 50 KB in 50 folders plus 5 of 10 MB, 292 MB of text), median of 3 calls, Postgres 17:
  
  | kb_exec command | before | after | peak memory before | after |
  |---|---|---|---|---|
  | `ls` | 2.34 s | 0.20 s | 874 MB | 243 MB |
  | `ls folder_000/` | 2.15 s | 0.20 s | 873 MB | 243 MB |
  | `cat folder_000/doc_000_001.md` | 1.07 s | 0.17 s | 855 MB | 243 MB |
  | `grep -n needle folder_000/` | 1.24 s | 0.31 s | 871 MB | 243 MB |
  | `grep -c needle large_0.md` | 1.19 s | 0.22 s | 874 MB | 306 MB |
  
  On SQLite the same calls drop from 0.50-1.03 s to 0.16-0.29 s.
  
  Fixes #33322

  Classic298 · 2026-10-29 05:26:02 +09:00
  517f824eb4
• feat: choose the Mistral OCR model and pass extra OCR request options (#33333)

  Mistral OCR always sent the mistral-ocr-latest model with no other request options, so admins could not stay on an older OCR model or send the model name a Mistral-compatible endpoint such as Azure AI Foundry expects. A new Parameters field under Admin Panel > Settings > Documents, shown when Mistral OCR is the extraction engine and also available as the MISTRAL_OCR_PARAMS environment variable, takes a JSON object that is merged into every OCR request: {"model": "mistral-ocr-2512"} replaces the default model, and any other field is sent to the OCR endpoint as given. It works the same with and without the Use Base64 switch, and when it is left empty the request is unchanged.
  
  Closes #19707

  Classic298 · 2026-10-29 05:25:53 +09:00
  f1f0a194ae
• feat: moving a chat into or out of a folder keeps its last activity date (#33327)

  Filing an old chat into a folder made it look recently active: it jumped to the top of the sidebar under Today, and a batch of old chats sorted into folders ended up ordered by when each was moved. Moving a chat into or out of a folder now keeps its last activity date, so it is sorted and grouped by when it was really last active. Moving your own chat still clears its unread dot as before, and when the owner of a shared folder reorganizes your chat within it, the chat no longer turns unread for you.
  
  Closes #30362

  Classic298 · 2026-10-29 05:21:30 +09:00
  40a9fba81f
• refac
  Timothy Jaeryang Baek · 2026-10-28 10:25:04 +09:00
  7f03b6e778
• refac
  Timothy Jaeryang Baek · 2026-10-28 10:02:45 +09:00
  b34885efc6
• fix: the Local source filter on Workspace > Knowledge lists knowledge bases made with Create (#33199)
  G30 · 2026-10-26 17:31:16 +09:00
  6635a45df4
• fix: a model's Chats tab in Analytics follows the User group filter (#33207)
  G30 · 2026-10-26 17:27:32 +09:00
  02821c5058