Commit graph

540 commits

Author SHA1 Message Date
Marco Beretta
7d0e79786f
🪶 fix: Time Out Client Refresh and Trim Lodash Imports (#17467)
* perf: Bound client hygiene paths (lodash imports, timeouts, listener cleanup, upload concurrency)

* feat: Make client request timeouts configurable

* test: Cover the configured refresh deadline end to end

* feat: Rename client timeouts to client limits and expose upload concurrency

* fix: Keep the published refresh deadline for the next page load
2026-10-27 23:30:08 +01:00
Marco Beretta
c1dfd6bc0f
📦 refactor: Move the useChat Facade and ChatContext into the Chat Package (#17445)
* refactor: Move the useChat Facade and ChatContext into @librechat/chat/react

The facade, ChatContext, the chat contract types and the resume request atom now
live in the chat package. The message cache subscription and the app's tool
outcome rules reach the facade through the contract, and useChatHelpers reads
its pane conversation through ChatSettings instead of the app store.

* fix: Key Cached Message Views on the Host's Tool Outcome Rules
2026-10-26 22:46:55 +01:00
Danny Avila
aa8e5849e0
⬆️ feat: Migrate to Zod v4 (#17442)
* ⬆️ feat: Migrate to Zod v4 (GHSA-mrhx-c7xc-m3w5), openai 6.49, zod-openapi 6

* 🔒 chore: Regenerate bun.lock

* 🐛 fix: Keep omitted fields absent under Zod 4 partial/optional defaults

* fix: Preserve Config Record-Key Diagnostics After Zod 4 Migration

* fix: Require Agents SDK 4.1.1 for Zod 4 Accounting

---------

Co-authored-by: Lia <lia@librechat.ai>
2026-10-26 14:16:22 +01:00
Atef Bellaaj
6e397c33a2
🎴 feat: Use Langfuse Prompts from Cards and the Slash Command (#17104) 2026-10-24 13:51:01 +02:00
Atef Bellaaj
bf0b8a9031
🖐️ feat: Make External Prompt Groups Read-Only (#17008)
Reject edits, deletes, new revisions, promotion and revision deletes on
prompt groups whose source is not native with a read_only service error,
mapped to 403 "Externally managed prompts are read-only". The guard reads
the stored group, so the MANAGE_PROMPTS bypass is covered. Sharing,
usage counts and resolution are unchanged.

The client hides Edit and Delete for external groups, shows a read-only
detail view with a Langfuse notice and keeps Share.
2026-10-24 13:48:26 +02:00
lia-by-librechat[bot]
5cf87548cd
🩰 fix: Keep Subagent Guidance in Main Chat Order (#17394)
* fix: Keep Applied Subagent Guidance in Main Chat Order

* fix: Preserve Pending Controls and Unmatched Legacy Guidance

* fix: Type Retained Control Read Parameters

* fix: Keep Guidance Receipts Truthful Across Delivery States

* fix: Retain Projected Steering Client Identities

* fix: Retain Ordered Guidance Across Terminal Child States

* style: Keep Public Observation Parsing Flat

* fix: Preserve Usable Legacy Activity During Reprojection

* test: Type the Legacy Recovery View Adapter

* fix: Preserve Shared Progress Identity and Public Reasoning

* fix: Forward Host Steering Through Shared Progress

* fix: Replace Tool Argument Placeholders Before Streaming

* fix: Retain Late Child Calls and Parent Steering Content

---------

Co-authored-by: Lia <lia@librechat.ai>
2026-10-24 12:12:57 +02:00
Danny Avila
0abbf3313d
🔐 fix: Apply Base Config Overrides Before Sign-In and Refuse Script Policy Links (#17351)
* 🔐 fix: Apply Base Config Overrides Before Sign-In and Refuse Script Policy Links

Sign-in decisions made before the user is known now read librechat.yaml plus the `__base__`
override of the request's tenant, or of the deployment outside a tenant, and fail closed
(`resolvePreAuthAppConfig`). Registration, the first phase of password reset and the first
email-domain check of the LDAP, OpenID, SAML and social strategies use it. The second check
applies the account's role overrides with or without a tenant, and a new account is checked
against the role it will be created with before anything is inserted. OpenID checks again when
the admin claim or role sync changes the role. Password reset issues no link when the
account's config cannot be read.

The signed-out `GET /api/config` serves Base `registration.socialLogins` and the pre-login
interface fields (`resolvePreLoginAppConfig`), falling back to librechat.yaml when overrides
cannot be read. `turnstile` becomes a base-only section, so Turnstile comes only from
librechat.yaml.

Config reads that merge documents stay in one tenant partition (`tenantPartition`, Mongoose
binding `tenantPartitionFilter`): the active tenant's documents, or the tenantless ones outside
a tenant. The config store's Mongoose binding reads, writes, lists and restores role documents,
`__base__` included, in that partition, and its `listActive` draws every document from it;
group and user documents stay addressed by id. Only a `list` with `acrossTenants` reads every
partition, which `listConfigTombstones` uses so the startup MCP tombstone report still names
each tenant's documents. The tenant-isolation conformance suite gains single-partition cases.

Privacy policy and terms of service `externalUrl` must be http(s), `mailto:`, `tel:`, relative
or blank (`isSafeLinkUrl`). Admin writes of another scheme are refused, a librechat.yaml link is
dropped with a warning at load, a stored one is dropped at merge, and every payload and the
client remove one that reaches them. The admin config meta reports
`features.preAuthBaseOverrides: true`.

* 🧪 test: Layer a Required-Field Override Through interface.currency Instead of Turnstile

Turnstile is set in librechat.yaml only now, so profile overrides of it are skipped and the
layering scenario could no longer see a role's Turnstile options completed by a user's site key.
The scenario now layers `interface.currency`, whose `code` and `rate` are both required: the role
stores only the rate, the user only the code, and /api/config serves both.

* 🛂 fix: Admit a First OpenID Login Under Its Claimed Role Before Creating the Account

The admin-role claim and role sync are now decided before a first-login OpenID account is created, and createUserOnce admits the email under that role's config, read in parallel with the USER role's, before inserting anything. A login the claimed role refuses creates no account and no start balance. Admitted logins are unchanged: the account is still created as USER (now explicitly), moved into the claimed role, re-checked and audited as before, with the claims decided once. An account a concurrent first login created gets the claims decided again for its own role and tenant.
2026-10-22 22:49:54 +02:00
lia-by-librechat[bot]
4fad3d75a9
🚜 fix: Release Heavy Chat State on Conversation Switches (#17291)
* 🚜 fix: Release Heavy Chat State on Conversation Switches

* test: Preserve Warm-Cache Revalidation in Navigation Regression

* fix: Track Message Writes and Rendered Conversation Ownership

---------

Co-authored-by: Lia <lia@librechat.ai>
2026-10-22 09:58:05 +02:00
lia-by-librechat[bot]
1871d31401
🪏 fix: Restore Explicit File Search Uploads (#17226)
* fix: Restore Explicit File Search Uploads

* fix: Preserve Unified Assistants Upload Sources

* style: Format Upload Provider Condition

* fix: Keep Unified Code Uploads Implicit

* fix: Respect File Search Upload Role Permissions

* fix: Activate File Search After Upload Persistence

* fix: Recover File Search Activation for Retained Drafts

* fix: Distinguish File Search Choices From Preference Sync

* fix: Preserve Upload Operation and Draft Ownership

* fix: Bound Draft Recovery and Own Staged Upload Cancellation

* fix: Preserve Composer Draft Ownership Across Navigation

* style: Match Pinned Prettier Union Formatting

* fix: Bind Deferred Uploads to Their Originating Composer

* fix: Preserve Upload Ownership Through Acknowledged Composer Handoffs

* test: Pass the New Conversation Sentinel as a String

* fix: Refresh Composer Ownership Atomically on New Chat Reset

* fix: Preserve Composer Ownership During URL Prompt Cleanup

* fix: Refresh Composer Ownership After Project Route Changes

* fix: Fence Upload Activation With Current or Retained Composer Ownership

* fix: Retire Composer Ownership Across History and Reloads

* fix: Preserve New-Chat Upload Ownership During Bootstrap

* fix: Fence Retained Uploads During Composer Cache Recovery

* fix: Transfer File Search Preferences Only on First Assignment

* fix: Preserve Upload State Across Acknowledgement Races

* test: Use Production Pending Draft Keys in Autosave Regressions

* fix: Preserve Upload Ownership Through Assistants Sync

* test: Supply Required Assistants Submission Metadata

* fix: Remove Retired Upload Chips by File Identity

* test: Fix Sync Fixture Type and Regression Formatting

* fix: Preserve Retained Uploads and Final Tool Preferences

* test: Align Final Frame Fixtures With Upload Retirement

---------

Co-authored-by: Lia <lia@librechat.ai>
2026-10-21 23:53:29 +02:00
Marco Beretta
fd85fed204
💬 fix: Mirror Chat Messages, Markdown and Code Blocks for RTL (#17267)
* fix: Mirror Chat Surfaces For RTL Layouts

* fix: Keep Short Subagent Ticker Lines at Their Reading Start

Adds RTL chat scenarios covering code, markdown blocks, sibling arrows and virtualized lists.

* fix: Resolve Quote and List Direction From Their Content

dir=auto skips descendants that carry their own dir, so a quote or loose list holding dir=auto paragraphs always resolved left-to-right. Lists now take one direction so markers and indent stay on the same side.

* fix: Keep Tables, Callouts and Trace Axes on One Direction

Tables take one direction from their content so cell borders share a frame; strong-direction detection skips Arabic-Indic digits, separators and marks; handoff and answer callouts use a logical start border; trace tick and range labels stay on the LTR axis.

* fix: Treat Every Script's Letters as Strong Direction

Direction detection now keys on Unicode letters, so Devanagari, Thai and other LTR scripts resolve LTR. E2E specs that selected rows by pl-6 now select ps-6.

* test: Cover the Shared Strong Direction Helper on Its Own

* fix: Read Bidi Marks and Native Script Digits as Strong Direction

* fix: Approximate Bidi Classes by Block So Symbols and Numerals Resolve

* fix: Resolve Strong Direction From Unicode Bidi Class Tables

* docs: Note How the Bidi Tables Are Generated and Where They Differ

* fix: Generate the Bidi Tables From Unicode 17 Including L-Class Marks
2026-10-20 16:19:14 +02:00
Marco Beretta
f51ea67ab4
⌨️ feat: Keyboard Submit, Focus and Escape for Ask User Cards (#17231)
* ⌨️ feat: Keyboard submit for ask_user_question answer box

The interactive ask_user_question card's answer textarea had no key
handling, so the answer could only be submitted by clicking. Route its
keydown through resolveComposerKeyDown so it follows the composer's
Enter-to-send preference, a rebound submit chord, and IME composition.
The run is paused rather than generating, so it resolves as idle and
Ctrl/Cmd+Enter submits instead of reaching the during-run actions.

* ⌨️ feat: Keyboard focus and confirm for batched ask_user_question

- Focus the first question's controls when a batch arrives, only when
  focus is idle (body, or the empty composer that sent the turn), and
  focus into the next step on advance instead of the fieldset: the picked
  or first option, else the answer field.
- Enter on the already-picked single-select option confirms the step;
  Enter on an unpicked option stays its click, so a pick never submits
  by itself (WCAG 3.2.2). Multi-select rows only toggle.
- Ctrl/Cmd+Enter confirm from the answer field like Enter; Shift+Enter
  never does.

* 🐛 fix: Keep Held Enter and Remounts From Picking Batched Answers

Review findings on the batched ask_user_question card, and what this
commit does about each.

1. Held or double-tapped Enter could pick answers and submit the batch.
   After Enter confirmed a step, focus moved to the next step's first
   option. A keyboard Enter on a focused button is its click, so the
   key repeat of a held Enter (or a quick double-tap) picked that option
   and advanced again. On the last step the next repeat landed on the
   now-pressed option, confirmed it, and submitted the whole batch with
   answers the user never chose.

   Fix: after a step change, focus goes to the step's picked option,
   else its answer field. An unpicked option is only a focus target when
   a batch first arrives. Repeats now reach a text field, which can page
   on but never picks an option or submits on the user's behalf.

2. Focus-on-arrival ran on every mount, not only on arrival. Its effect
   has empty deps, so moving the batch between the composer popover and
   the chat card, or remounting a message that still holds an
   unanswered batch (reopening a conversation, a Share view), pulled
   focus onto an option of that batch. The next Enter or Space would
   then answer it.

   Fix: `AskUserQuestions` takes a `focusOnArrival` prop, set only by
   the surface showing the live pause (the popover, or the chat card
   while it is live and visible), so other mounts never take focus.
   Focus is placed at most once per batch, tracked by action id, so a
   move between surfaces is not treated as a new arrival.

Tests: a held Enter from an answer field picks nothing and never
submits; a surface that isn't the live pause leaves focus alone; a
remount of the same batch doesn't take focus again. All three fail
without this change. The Chat/Messages/Content, Chat/Input, Chat/ask
and hooks/Input suites pass, apart from TokenUsage/index.spec.tsx,
which fails the same way without this change. tsc, ESLint and Prettier
are clean on the changed files.

* feat: Escape to Skip Ask Cards and Move the Popover to Chat

Escape in the chat card skips the question or batch, but only before
anything is entered, so a stray Escape cannot discard an answer and
resume the run. Escape with focus inside the composer popover moves the
question to the chat, as it already did from the composer, and returns
focus to the composer once the popover closes. Also drops the em dashes
from the batched card's comments.

* fix: Read Enter-to-Send From the Chat Surface Host in the Ask Card

* test: Cover Ask Batch Keyboard Control in E2E Scenarios

* fix: Keep Held and Modified Enter From Submitting Ask Answers

Ignore auto-repeated Enter before confirming a picked option, so a held
Enter cannot both pick and submit the last question. In the answer
field, Shift, Alt and repeated Enter now prevent the enclosing chat
form's implicit submit instead of returning early. Escape that cancels
an IME composition no longer moves the popover to the chat, and the
arrival-focus flag lives in the batch's Jotai form state.

* fix: Honor a Submit Shortcut Rebound Off Enter in Ask Answer Fields

The window shortcut handler yields submitMessage in every editing field
except the composer, so a chord such as Ctrl+J did nothing in the ask
answer fields. Both the single-question answer box and the batched
answer field now act on it, through a shared isReboundSubmitChord.

---------

Co-authored-by: elie605 <ebtien@gmail.com>
2026-10-18 20:17:36 +02:00
Marco Beretta
b06224bf60
🧽 refactor: Import Composer State and Restore from the Chat Package (#17163) 2026-10-18 17:43:59 +02:00
Marco Beretta
268ff45bf9
🔢 fix: Pair English Plural Keys as _one/_other for Locize (#17223)
* fix: Pair English Plural Keys as _one/_other for Locize

Locize groups keys by plural suffix and generates every form a language
needs. Families that paired a bare base key with _one surfaced empty-source
_other rows, and literal keys ending in _other or _one spawned unrelated
plural siblings. Rename the bases to _other, rename the colliding literal
keys, and guard the English file against a regression.

* test: Cover Plural Version Count and Other Issue Feedback Tag

* fix: Announce a Single Running or Finished Chat in the Singular

* fix: Resolve Plural Forms From Base Keys So Locale Plural Rules Apply

Selecting an explicit _other key bypassed i18next's plural resolution, so a
single running chat was announced in the plural and locale forms such as
_zero and _many were never chosen. Call sites pass the base key with a
numeric count again, and TranslationKeys accepts plural base keys.

* fix: Let i18next Pick Duration Plural Forms From a Numeric Count

Duration and elapsed announcements selected an explicit _one or _other key
and passed the formatted number as count, so locale forms such as _few and
_many were unreachable. They now pass the base key with a numeric count and
interpolate the locale-formatted number as value.
2026-10-18 14:11:02 +02:00
Marco Beretta
f7a56e843b
🖼️ fix: Render Files Saved by Tools Inside a Subagent Run (#17204)
Some checks are pending
Backend Unit Tests / Build packages (push) Waiting to run
Backend Unit Tests / Codegraph select (push) Waiting to run
Backend Unit Tests / TypeScript type checks (push) Blocked by required conditions
Backend Unit Tests / Circular dependency checks (push) Waiting to run
Backend Unit Tests / Tests: api (shard 1/3) (push) Blocked by required conditions
Backend Unit Tests / Tests: api (shard 2/3) (push) Blocked by required conditions
Backend Unit Tests / Tests: api (shard 3/3) (push) Blocked by required conditions
Backend Unit Tests / Tests: data-provider (push) Blocked by required conditions
Backend Unit Tests / Tests: data-schemas (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 1/4) (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 2/4) (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 3/4) (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 4/4) (push) Blocked by required conditions
Codegraph E2E Votes / vote (full suite) (push) Waiting to run
Docker Dev Branch Images Build / publish (push) Waiting to run
Frontend Unit Tests / Client build recovery regression (push) Waiting to run
Frontend Unit Tests / Codegraph select (push) Waiting to run
Frontend Unit Tests / Build packages (push) Waiting to run
Frontend Unit Tests / TypeScript type checks (client) (push) Blocked by required conditions
Frontend Unit Tests / Tests: @librechat/chat (push) Blocked by required conditions
Frontend Unit Tests / Tests: @librechat/client (push) Blocked by required conditions
Frontend Unit Tests / Tests: Ubuntu (shard 1/2) (push) Blocked by required conditions
Frontend Unit Tests / Tests: Ubuntu (shard 2/2) (push) Blocked by required conditions
Frontend Unit Tests / Vite build verification (push) Blocked by required conditions
* fix: Render Files Saved by Tools Inside a Subagent Run

* test: Cover Subagent Nested Tool Images After Reload

* fix: Hoist Subagent Child-Run Files With Grouped Tool Calls

* fix: Route Live Subagent Child Files Through the Part Attachment Map

* fix: Keep Subagent Child File Routing Through Previews and Ownership Rules

* test: Match Subagent Image Names Exactly

* fix: Key Subagent Child Files by Their Owning Part

* fix: Apply Attachment Scope Rules to Subagent Child Calls

* fix: Carry Child Call Scope Through Previews and Live Progress

* fix: Retain Live Subagent Progress Readers and Seen Child Calls

* fix: Keep Live Progress Keys Retained Across Streamed Deltas

* fix: Assign Subagent Child Files Once Per Message

* fix: Route Late and Id-less Subagent Child Files

* fix: Keep Seen Subagent Child Calls With Their Invocation

* fix: Use Streamed Index and Call-Level Owner for Subagent Child Files

* fix: Reserve Scoped Child Files From Unscoped Top-Level Calls

* fix: Record Subagent Child Calls When Progress Is Written

* fix: Keep Agent Scope on Remembered Subagent Child Calls

* refactor: Share One Subagent Child Call Collector

* fix: Derive Live Signature From Remembered Child Calls

* fix: Keep Child Calls a Bounded Batch Evicts

* fix: Bound Remembered Subagent Child Calls and Include Replay Segments

* fix: Refresh Owners of Shown Files in the Bounded Call History

* fix: Keep Remembered Call Order Stable Across Eviction Replays

* fix: Scope Preview Hints to Attachments and Walk Nested Calls Iteratively

* fix: Bound Wildcard Preview Hints and Own Live Calls by Their Run

* fix: Own Stored Subagent Child Calls by Their Persisted Identity
2026-10-17 22:14:48 +02:00
Dustin Healy
f757a673aa
🐛 fix: Restore MCP App Rendering and Actions (#16382)
* 🐛 fix: Restore MCP App Rendering and Startup

* 🐛 fix: Sort MCP App Bridge Imports

* 🐛 fix: Scope MCP App Validation to Current Role

* 🐛 fix: Keep MCP App Frames Mounted Through Layout Changes

* 🐛 fix: Reuse Principals for MCP App Validation

* Revert "🐛 fix: Keep MCP App Frames Mounted Through Layout Changes"

This reverts commit 54152c2ec5.

* 🧪 test: Preserve Dev MCP App Rendering Coverage

* fix: Restore Stable Inline MCP Apps and Queued Actions

* fix: Preserve MCP App Resource Owners Through Content Shifts

* fix: preserve message attribution and sources across MCP Apps

* test: separate MCP App detach and navigation revocation

---------

Co-authored-by: Lia <lia@librechat.ai>
2026-10-16 13:27:29 -07:00
Marco Beretta
07299822e5
🧪 refactor: Move Test-Only Helpers Out of Production Modules (#17139)
* refactor: Drop Queue Reset Helper From The Client Queue Module

* refactor: Drop Unused Shortcut Getters And Subagent Batch Wrappers

* refactor: Move HITL Approval Payload Builder To Test Fixtures And Drop Dead Helpers
2026-10-16 21:58:08 +02:00
Danny Avila
0a1f4df643
🪄 fix: Ground the Default Artifacts Prompt in What the Renderer Supports (#17024)
* 🪄 fix: Ground the Default Artifacts Prompt in What the Renderer Supports

* 🧪 test: Stub IntersectionObserver with a Class the Checker Accepts
2026-10-16 07:00:27 -04:00
Marco Beretta
995a56b117
✂️ refactor: Split the Chat Ask Function Into Turn Modules (#17115) 2026-10-15 18:13:05 +02:00
Marco Beretta
e693deddb0
📦 refactor: Move Steer Queue and Composer State into the Chat Package (#17155) 2026-10-15 17:39:34 +02:00
Marco Beretta
0354562075
🔁 fix: Keep the Error Card When a Stream Reattached Without Resume State Fails (#17112) 2026-10-15 17:22:28 +02:00
Marco Beretta
86c2ac7dce
🧮 refactor: Move Token Usage Math Into the Chat Package (#17106) 2026-10-15 17:18:58 +02:00
Marco Beretta
d1c06145ab
🧭 refactor: Move Steer and Queue Pure Logic into the Chat Core (#17107) 2026-10-15 15:49:27 +02:00
Marco Beretta
a247a12a3d
🧹 refactor: Remove Dead Client Hooks, Store Modules and Utilities (#17111) 2026-10-15 12:22:13 +02:00
Marco Beretta
79b836d79f
📃 fix: Enforce Terms Acceptance on the Server and Mark Backfilled Consent (#17063)
* fix: Enforce Terms Acceptance on the Server When modalAcceptance Is On

* fix: Mark Backfilled Terms Acceptance Timestamps

* test: Cover Server-Enforced Terms Acceptance in the Mock Harness

* fix: Gate Management Routes and Skill Sync and Resolve Terms Policy Fail-Closed

* fix: Evict Cached Auth Documents When Terms Acceptance Is Reset

* fix: Guard Skill Sync Behind Terms Acceptance for Every Skill List Route

* fix: Move Terms Skill-Sync Guard Into the API Package and Evict All Users on Reset

* fix: Batch Terms Reset Cache Eviction and Sign the Spec User In Fresh

* fix: Let Stop Through the Terms Gate, Refresh Startup Config, and Wait Out Failed Eviction

* refactor: Narrow the Terms Exemptions and Share One Refusal Path Across Clients

* refactor: Compose the JWT Terms Gate Through an API Package Helper

* style: Sort Imports for the Shared Terms Refusal Helper

* test: Expose the Terms Gate Helper in the JWT Auth Spec Mock

* test: Cover the Terms Refusal Code on Pre-Stream Upload Errors
2026-10-14 17:45:28 +02:00
Marco Beretta
a06ee14b75
🔐 fix: Encrypt User Plugin Credentials With Random-IV v3 Format (#16996)
* fix: Encrypt User Plugin Credentials With Random-IV v3 Format

* test: Cover Credential Encryption Formats in Mock E2E Scenarios

* test: Round-Trip Real Credential Helpers in PluginService Spec

* 🙈 fix: Remove SharePoint Picker Payload Logging (#16997)

* fix: Add credentials.writeFormat to Gate v3 Credential Writes During Rollouts

* test: Expect 201 When the Legacy Write Format Override Is Created

* 🔊 fix: Clear TTS Audio Cache On Session End and Hash Its Keys (#16998)

* fix: Clear TTS Audio Cache On Session End and Hash Its Keys

* fix: Read Manual TTS Replays From the Hashed Cache Key

* fix: Purge Legacy TTS Cache Keys and Fence Writes Across Logout

* fix: Keep TTS Cache Writes Off the Playback Path

* test: Expect Hashed Keys in the StreamAudio Cache Lookup

* test: Use a Single-Token Reply Label in the TTS Cache Scenario

* fix: Settle TTS Cache Clear Before IdP Logout and Across Tabs

* test: Cover the TTS Cache Fence When Another Tab Logs Out

* test: Wait for the Second Tab Before Logging Out in the TTS Scenario

* fix: Latch TTS Cache Writes Shut Until the Tab Authenticates Again

* fix: Reopen TTS Cache Writes When Authentication Completes In Place

* fix: Leave for the IdP Even When TTS Cache Cleanup Fails

* fix: Retry a Failed Legacy TTS Purge and Fence Other Tabs on Manual Clear

* fix: Rerun the Legacy TTS Purge After Each Clear and Sign-In

* fix: Rerun the Legacy TTS Purge When Another Tab Clears

* fix: Fence Pre-Auth TTS Writes, Retry Failed Clears, and Fall Back to Storage Events

* fix: Version the Hashed TTS Cache Key Path

* fix: Move TTS Audio to a New Cache and Keep It Closed Until a Failed Clear Succeeds

* fix: Persist a Pending TTS Cache Delete Across Navigation

* fix: Reopen TTS Caching Only on Session Start and Fence Cache Reads

* fix: Keep the TTS Delete Fence in Cache Storage and Close Reads After Logout

* refactor: Keep Read-Aloud Audio in Tab Memory Instead of Cache Storage

* test: Return to the Conversation After Re-Login in the TTS Logout Scenario

* test: Close the Phone Sidebar Before Replaying in the TTS Logout Scenario

* fix: Bound the In-Memory TTS Cache by Size as Well as Count

* fix: Scope Cached TTS Audio to the Signed-In User

* fix: Keep the Settings Cache Delete Available While Legacy Audio Remains

* fix: Recheck Legacy TTS Audio After a Settings Clear and on Unowned Handoff

* fix: Fence TTS Writes Started Before an Account Signs In

* test: Opt the Fresh TTS Account Into Enter-to-Send
2026-10-12 16:33:08 +02:00
Marco Beretta
e1b4e09d7c
🥟 ci: Type-Check Workspaces with bun check (#17009)
Some checks failed
Backend Unit Tests / Build packages (push) Waiting to run
Backend Unit Tests / Codegraph select (push) Waiting to run
Backend Unit Tests / TypeScript type checks (push) Blocked by required conditions
Backend Unit Tests / Circular dependency checks (push) Waiting to run
Backend Unit Tests / Tests: api (shard 1/3) (push) Blocked by required conditions
Backend Unit Tests / Tests: api (shard 2/3) (push) Blocked by required conditions
Backend Unit Tests / Tests: api (shard 3/3) (push) Blocked by required conditions
Backend Unit Tests / Tests: data-provider (push) Blocked by required conditions
Backend Unit Tests / Tests: data-schemas (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 1/4) (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 2/4) (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 3/4) (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 4/4) (push) Blocked by required conditions
Codegraph E2E Votes / vote (full suite) (push) Waiting to run
Docker Dev Branch Images Build / publish (push) Waiting to run
Frontend Unit Tests / Client build recovery regression (push) Waiting to run
Frontend Unit Tests / Codegraph select (push) Waiting to run
Frontend Unit Tests / Build packages (push) Waiting to run
Frontend Unit Tests / TypeScript type checks (client) (push) Blocked by required conditions
Frontend Unit Tests / Tests: @librechat/chat (push) Blocked by required conditions
Frontend Unit Tests / Tests: @librechat/client (push) Blocked by required conditions
Frontend Unit Tests / Tests: Ubuntu (shard 1/2) (push) Blocked by required conditions
Frontend Unit Tests / Tests: Ubuntu (shard 2/2) (push) Blocked by required conditions
Frontend Unit Tests / Vite build verification (push) Blocked by required conditions
Main Promotion Policy Tests / Main promotion denial and fast-forward tests (push) Has been cancelled
* ci: Type-Check Workspaces with bun check

Make every workspace tsconfig valid under TypeScript 7 semantics while
staying clean on the installed tsc 5.9: explicit types arrays (TS 7 no
longer auto-includes node_modules/@types), es2017 target for
data-provider, rootDir for api specs that import client contracts, and
noUncheckedSideEffectImports off for the CSS and matchMedia mock imports.

Fix the four client type errors newer DOM and Intl libs expose, and drop
the fetch.preconnect copy in useRum that only existed to satisfy the
leaked @types/bun globals.

Switch the client typecheck script and the CI type-check steps to
bun check (Bun 1.4.3); tsc --noEmit stays available as typecheck:tsc.

* chore: Fall Back to tsc When bun check Is Unavailable

Add scripts/typecheck.mts, which runs bun check when the installed Bun
provides it and the repository's tsc otherwise, so contributors without
Bun can still type-check. The client typecheck script and the
static-checks TypeScript gate both resolve their checker through it,
keeping local runs on the same checker CI uses whenever Bun is present.

* ci: Type-Check the Chat Package Through the Shared Checker

* ci: Run the Type Check When Only the Shared Checker Changes

A change to scripts/typecheck.mts alone started neither frontend review
nor the static-checks TypeScript gate, so a broken resolver could merge
unexercised. Add it to the frontend-review triggers and to every
typecheck project's paths.

The suppression-baseline scenarios copy static-checks.mts into synthetic
roots; copy its new typecheck.mts import alongside i18n.mts so the runner
loads there. Add scenarios for the checker choice and its fallback.
2026-10-12 06:40:07 -04:00
Marco Beretta
bdc4bafce2
🚰 refactor: Move the Pure Stream Code into the @librechat/chat Core (#16979)
The step appliers, frame normalizer and SSE transport move from client/src/hooks/SSE into packages/chat/src/core with their specs, and the client imports them from @librechat/chat. The ask-user-question predicates the content applier reads move with them, and the client's approval module re-exports them so its consumers are unchanged.
2026-10-11 23:04:47 +02:00
Marco Beretta
9902a215eb
📎 fix: Resolve useChat Tool Parts Against Live Attachments (#16960)
* fix: Resolve useChat Tool Parts Against Live Attachments

* test: Cover useChat Live Attachment Scenarios
2026-10-11 01:05:39 +02:00
Marco Beretta
7e9ec0f858
🧭 refactor: Normalize Model-Authored Artifact Types in One Place (#16947)
* refactor: Normalize Artifact Type Spellings in One Place

* test: Keep Backticks Out of the Short React Artifact Source

* test: Retry a Timed-Out Sandpack Boot in the Short React Scenario

* fix: Case-Fold Canonical Artifact Types as Well as Their Aliases
2026-10-10 00:40:44 +02:00
Marco Beretta
b7da0e0f76
🎯 a11y: Move Field and Focus Call Sites Onto the Control Roles (#16929)
* fix: Let Field and Focus Call Sites Use the Control Roles

Drop the border-heavy focus rings on the memory value fields, the tool
output details link and the Mermaid dialog controls, so each takes its
primitive's focus-control ring or the global outline. Give
TextareaAutosize a field variant and move the bookmark description onto
it. Drop the quiet border overrides on form controls so they keep the
border-control outline, move defaultTextProps and InputNumber onto it,
and prune the no-restyle counts these call sites no longer carry.

* test: Expect the Edge Focus Treatment on ClickHouse Bookmark Fields
2026-10-10 00:21:24 +02:00
Marco Beretta
b2c635aa30
👆 a11y: Show Hover-Revealed Actions to the Touchscreen on a 2-in-1 (#16943)
* fix: Keep Hover-Revealed Row Actions Visible Wherever a Finger Can Reach

* fix: Apply the Coarse-Pointer Reveal to the Composer Palette and Model Menu

* test: Assert the Reveal on an Earlier Reply, Not the Always-Visible Latest One

* test: Read the Timestamp From the Hovered Reply's Own Row

* fix: Hide Until Hover Only Where Hover Exists and No Pointer Is Coarse
2026-10-10 00:20:56 +02:00
Marco Beretta
b77b4cff19
🪄 feat: Adopt the Continue Icon, Artifact Timing, Avatar Border and Dropdown Intents Tailwind 3 Never Rendered (#16941)
* feat: Adopt the continue icon, artifact timing, avatar border and dropdown intents Tailwind 3 never rendered

Sizes the continue action's glyph to the 19px of the actions beside it, times the artifact sheet's close to the 250ms its unmount waits for and the docked panel's open to 350ms, frames agent avatars with the 1px border they asked for, and lets the dropdown menu primitive cap its height, grow from its trigger and tint a destructive item's icon.

* fix: Cap the dropdown submenu at the space Radix measures

* test: Stop pinning the adopted artifact durations as inert
2026-10-09 23:08:06 +02:00
Marco Beretta
e4274abf6f
🎨 a11y: Draw Every Prompt Category Icon Muted Under ClickHouse (#16935)
* feat: Route Every Prompt Category Icon Through a Per-Slot Role

* test: Retry Category Icon Reads While the Prompt List Settles

* fix: Carry the Renamed Category Icon Role to Its Slot 4 Name

* fix: Carry the Renamed Category Icon Role Through Every Color Reader

* fix: Keep Renamed Color Roles Out of the Unknown Token Warnings
2026-10-09 21:49:24 +02:00
Marco Beretta
8b9a7c521d
🔠 feat: Add 10, 11, 13 and 15px Steps to the Theme Type Scale (#16827)
* feat: Add 10, 11, 13 and 15px Steps to the Theme Type Scale

* test: Prove the Off-Scale Type Steps in the Mock Harness

* style: Sort cn Imports

* refactor: Name the 13 and 15px Steps 1xs and 1sm

* test: Probe the Type Step Roles Instead of Unused Utilities
2026-10-07 16:02:26 +02:00
Danny Avila
0fea0240d6
⏳ feat: Reset Balance Allowances Without Rollover (#16781)
* feat: add periodic balance reset without rollover

* fix: synchronize balance policy before periodic reset

* style: preserve context balance class order

* fix: Synchronize Reset Policy Before Granting Allowances

* fix: Apply Current Balance Policy During Admission
2026-10-05 11:44:00 -04:00
Danny Avila
3f442e4dbe
🪶 perf: Load Tool-Call Previews and Fetch Full Parts on Demand (#16753)
* 🧾 perf: Load Tool-Call Previews and Fetch Full Parts on Demand

Long agent conversations shipped every tool output, argument string and
subagent transcript on load, though the cards render collapsed: 12-18 MB
of message JSON per chat, enough to crash iPhone Safari tabs.

A client that adds ?toolPreviews=1 to the conversation load now receives
bounded previews of settled tool calls (start and end of long outputs,
JSON arguments and outputs kept valid with only their longest strings
shortened, exit-status trailers kept whole, subagent transcripts omitted)
with explicit markers and full lengths. Opening a card or a subagent
panel fetches the stored part from a new owner-scoped endpoint,
GET /api/messages/:conversationId/:messageId/parts/:partIndex, cached
under its own React Query key. Clients that do not ask, exports and share
links keep the full payload; bounds are configurable under
toolCallPreviews in librechat.yaml, and a client-authored message that
carries previews is refused rather than saved.

* 🧾 fix: Validate Part Reads in Parallel and Preview Fork Responses

The full-part read now starts beside conversation-access validation
instead of after it, and keeps the active-job fallback the conversation
read has, so a conversation still live before its first save can expand
its previews. Fork, duplicate and shared-link fork responses honor the
preview parameter, so they no longer seed the conversation cache with
the full history. Background-task results whose structure cannot fit a
valid JSON preview go whole, image cards keep their prompts, and the
subagent panel offers a retry when its stored part fails to load.

* 🧾 fix: Key Hydrated Parts by Preview Revision and Call Identity

A fetched part is now cached under the preview's revision and replaces
only the fields the server shortened, so a call whose stored output
changes later (a harvested background result) is fetched again rather
than rolled back. Part lookups carry the run-step and agent identity and
refuse an ambiguous fallback, since provider tool-call ids can repeat
within one response. A subagent that finished without final text has
its transcript omitted like any other settled call, and JSON nested past
a fixed depth falls back to a text preview; a call whose preview fails
is sent whole instead of failing the conversation load.

* 🧾 fix: Release Hydrated Parts With Their History and Bound JSON Work

Full tool-call parts fetched for a conversation are removed when its
message history is released or cleared, so they cannot outlive it under
their own key. The structure-preserving JSON preview now bails out before
cloning when the value has more nodes or strings than could ever fit,
keeps a __proto__ key as ordinary data, and the part endpoint accepts any
safe-integer index instead of an arbitrary ceiling.

* 🧾 fix: Count Property Names Before Cloning a JSON Preview

Property names are never shortened, so the pre-check now adds their
length to its budget and falls back to the text preview before any
cloning when they alone could not fit.

* 🧾 fix: Preview Artifact and Branch Responses and Rehydrate Subagent Prompts

Artifact edits and parallel-response branches merge the message the
server returns into the conversation cache, so both requests now ask
for previews and their routes honor it. The subagent panel reads the
prompt from the stored arguments once they load, and the part endpoint
no longer caps identifier length, so any previewed call can be fetched.

* 🧾 fix: Preview Only Tool Calls That Can Be Fetched Back by Identity

A call without an id has nothing but its position to name it, and the
position can shift on the client, so it is left whole instead of being
previewed. The part endpoint now requires a tool-call id, so an indexed
lookup always confirms the call it returns.

* 🧾 fix: Fetch Parts by Exact Identity and Preview Only Unique Ones

The part endpoint now finds a call by its exact identity (provider id,
run-step id, agent) instead of trusting the client's index, and the
preview pass only shortens calls whose identity is unique in their
message, so every preview names exactly one stored part. Legacy
web-search failures that carry their error phrase mid-output go whole,
since the collapsed card reads that phrase anywhere.

* 🧾 fix: Bound the JSON Fit Walk Before Queueing and Normalize Empty Identities

The structure check now counts an array's or object's children against
the node budget before queueing them, so a very wide value is refused
without building a work list its size. An empty run-step or agent id is
treated as absent by the part lookup, matching how the preview pass and
the client already treat it.

* 🧾 fix: Key Fetched Parts to the Stored Version and Hydrate Search Details

Each preview now carries `previewRevision`, when its message last
changed, and the client keys fetched parts to that plus a fingerprint of
the whole preview, so any change to the stored call is fetched again.
The web-search details card asks for the stored call when it opens, so
its query is never left shortened.

* 🧾 fix: Cache Fetched Parts by Identity and Hold Copy Until Hydrated

The part query key drops the client-side index, which only rides along in the request; the server locates the call by message and exact identity, so a shifted index serves the cached copy instead of downloading it again. Copy controls inside a previewed part are disabled until the stored content arrives, so a slow or failed fetch cannot export shortened text.

* 🧾 fix: Shape Shared Forks With the Recipient's Bounds and Keep JSON Numbers Exact

A shared-link fork resolves the share owner's config for its content checks, but the forked conversation belongs to the requester, so its preview bounds now come from the requester's tenant and role (prepareResultToolCallPreviews). A structure-preserving JSON preview now requires every number in the text to survive a parse and re-serialization as the same value; an integer past 2^53, an out-of-range exponent or an over-precise decimal falls back to the text preview (or the whole output for parsed-output tools) instead of showing a changed value.
2026-10-05 07:42:45 -04:00
Danny Avila
dc375a8e1c
🪪 feat: Name and Face Subagents Like Main Chat Turns (#16692)
* 🪪 feat: Name and Face Subagents Like Main Chat Turns

The subagent panel and its main chat entry points named children by agent
id ("Subagent: agent_…") and framed a parent agent's briefing as a
"System" turn under "Parent agent dispatch". They now use main chat's own
author treatment:

- MessageRow gains `showAuthor` (a user-side turn written by someone other
  than the reader carries the agent header, mirrored) and `outlined`
  (host-delivered body without a system heading). The agent header is a
  shared render helper with static classes, so main chat rows render the
  same tree as before.
- Panel: the parent's briefing and follow-ups are filled user turns under
  the parent agent's name and avatar; the header, composer placeholder and
  child turns share one resolved author. External events stay system turns.
- Main chat: a subagent wake-up is headed by the subagent's name and face,
  outlined, with an outcome icon; background-tool wake-ups stay "System".
  The subagent card leads with the agent's name, and a detached card shows
  the indexed task status from a leaf component.
- Shared conversations resolve the same authors from the shared thread.
- `resolveSubagentAgentId` reads an `agent_` type only when no identity was
  recorded, never for a graph child. Ids never reach visible text; an
  unresolvable agent is named generically.

* fix: Preserve Subagent Identity and Accessible Status

* fix: Skip Private Avatar Queries on Public Shares

* fix: Preserve Restored Authors and Reuse History Lookups

* fix: Respect Graph Identity and Await Historical Authors

* fix: Retain Indexed Identity and Shared Wakeup Authors

* fix: Render Wakeup Authors in Public Shares

* fix: Resolve Shared Wakeups from Persisted Dispatch Identity

* fix: Preserve Wakeup Provenance and Parallel Self Identity

* fix: Refresh Author Snapshots Between Subagent Dispatches

* fix: Align Wakeup Copy and Dispatch Identity

* fix: Resolve Restored Subagent Authors Consistently

* fix: Preserve Indexed Subagent Display Names
2026-10-05 07:15:04 -04:00
Danny Avila
82cde522f2
💳 feat: Show Balance in the Context Gauge as Credits, Currency, or Percent (#16762)
* 💳 feat: Show Balance in the Context Gauge as Credits, Currency, or Percent

Move the balance out of the account menu into the composer's context gauge,
below the context window, and add `balance.display` (credits | currency |
percent, default credits) to choose how it reads. Currency reuses
`interface.currency` at 1,000,000 credits per USD; percent shows only the
share of the period's allotment spent.

Settings > Account > Billing renders the same summary from the same hook, so
both surfaces show identical figures, bar and refill timing in every mode.

* 🧭 fix: Normalize the Balance Display Mode and Reuse a Fresh Reading on Hover

Admin overrides reach the client without schema validation, so an unknown
`balance.display` now reads as credits instead of being typed as a mode it is
not. Hovering the gauge mounts the balance reader each time the card opens; a
30 s stale window stops every hover from refetching, while the explicit
refetch after each turn still bypasses it.

* 🩹 fix: Restore Gauge Popover Fixes and Tighten Balance States

The popover extraction was written from a pre-sync read of TokenUsage, so it
dropped dev's viewport caps and scrolling, the hideOnInteractOutside close fix,
the Tailwind v4 outline-hidden rename, and the card's max-w-full; restore them.

Refill copy now says when a refill becomes available rather than promising a
deposit, since one lands only once the interval has passed and a charge would
exhaust the balance. An empty balance reads as fully used even without an
allotment, percent mode without one says usage is unavailable instead of
leaving the figure blank, the balance-only ring takes the balance tone (amber
until empty) and is a meter only once it has a value.

* 🪙 fix: Read a Non-Positive Refill Amount as No Auto-Refill in Settings

The server never refills when the amount is not positive, and the balance
summary already says so; Settings showed its load error instead.

* 💸 fix: Show the Insufficient-Funds Error in the Balance Display Mode

The token-balance error still printed raw credit figures, so `percent` leaked
the numbers it hides and `currency` mixed units with the gauge. It now reads
the same display mode and formatter as the balance summary: credits as before,
money in currency mode, no figures in percent mode.

The auto-refill settings row also renders its own loading and failure states,
since settings search can show it without the balance row beside it.

* 🎚️ fix: Keep Fractional Credits and Drop the Moved Popover's Suppression

Credit amounts keep up to two decimals, so an insufficient-funds message no
longer reads 100.4 against 100.3 as 100 against 100; whole amounts still print
without decimals.

The design-rule backlog may not follow code into a new file, so the extracted
popover uses the standard `transition` utility instead of the arbitrary
`transition-[opacity,transform]` (which also misses Tailwind v4's separate
`translate` and `scale` properties) and its suppression is removed. The
composer geometry spec now reads the classes from `Popover.tsx`, where the
gauge button lives.
2026-10-05 06:46:44 -04:00
Atef Bellaaj
3c90cde7d8
🔗 feat: use LibreChat prompt groups as agent instructions (#16686)
* 🔗 feat(agents): use LibreChat prompt groups as agent instructions

Agents can link a prompt group revision or Production as their instructions. The link resolves at the start of each turn through a cached resolver. The cache clears on promote and delete. Editors without VIEW on the group see a restricted placeholder.

* fix: remove duplicate logger import from agent initialization tests

* fix: honor prompt management capabilities for linked agent instructions

* test: seed prompt manager capabilities in authorization fixtures

* fix: clear acknowledged linked prompt edits before version restore

* test: adapt merged chain coverage to prompt-aware payload helper

---------

Co-authored-by: Lia <lia@librechat.ai>
2026-10-04 21:27:26 -04:00
Marco Beretta
7e575c047f
🔍 feat: App-Wide UI Scale Setting (#14903)
* feat: add app-wide UI scale setting

* test: align dev's new header, drawer and combobox specs with the scaled shell

* fix: keep design-recorded arbitrary values off the same-count swap

* fix: scale composer and reasoning spacing on the spacing scale

* test: reach scaled rows and wait on the composer under the unpainted drawer

* test: cover the scaled composer at both ends of the range

* test: reload the composer scenario at each scale from the live page

* fix: leave the root style untouched at the default scale

* test: align dev's tool output and subagent inset specs with the rem classes

* fix: scale a caller's combobox height cap with its rows

* fix: size the conversation list's row estimate on the scaled drawer breakpoint

* test: align dev's conversation row status spec with the scaled drawer breakpoint

* style: sort the settings dialog imports after the dialog layer merge

* fix: scale the collapsed combobox's fallback popover width

* fix: size the upload glyph on both axes so it grows with the scale
2026-10-04 23:20:04 +02:00
lia-by-librechat[bot]
0e3c9088f6
🫰 feat: Configure Tool Approval Modes Per Agent (#16707)
* 🫰 feat: Configure Tool Approval Modes Per Agent

* fix: Fence Remembered Tool Approval Authority

* fix: Unify Tool Approval Execution Invariants

* fix: Revalidate Learned Approval at MCP Invocation

* fix: Preserve One-Time MCP Review at Invocation

* fix: Execute Reviewed Calls on Templated MCP Connections

* fix: Scope Approval Witnesses to Executing Agents

* fix: Retain Approval Bindings for Hook-Rewritten Inputs

* fix: Pin Review Authority and Retire Settled Tool Calls

* fix: Fingerprint Effective MCP Request Headers

* fix: Preserve Routing Around Renewable MCP Token Fragments

* fix: Bind Tool Consent to OAuth Credential Generations

* test: Keep Mobile Approval Save Outside Drawer Escape Race

* fix: Fence OAuth Consent at MCP Transport Retries

* fix: Let Shared Agent Viewers Reset Personal Consent

* fix: Preserve Renewed Consent Across Reset Races

* fix: Resolve Verified Aliases for Personal Tool Reset

* fix: Fence Renewed OAuth Consent and Credential Review

* fix: Require Foreground Execution for Review-Only MCP Calls

* fix: Pin Invocation Ownership and Stable MCP Consent

* fix: Fence Superseded Tool Consent Completion Writes

* fix: Scope Consent Epochs to Effective MCP Authentication

* fix: Scope Approval Admission to Reachable Agent Tools

* fix: Preserve Approval Epochs for Runtime-Detected OAuth

* fix: Address Tool Approval Review Findings

* fix: Preserve Captured Consent When Tool Approval Is Inherited

* fix: Preserve Approval Admission Through Lazy Metadata

* fix: Fence Programmatic Reviews and Unresolved Lazy Approval Keys

* fix: Account for Normalized and Skill-Contributed Lazy Tools

* fix: Scope Lazy Approval to Selected Tool Spellings and Servers

* fix: Honor Disabled MCP Capability During Lazy Approval Admission

* test: Preserve Approval Merge Regressions After Rebase

* fix: Preserve One-Time Review During Non-OAuth Grant Outages

* fix: Retain One-Time Consent Across Resume Recovery

* fix: Preserve Reviewed Consent Through Transport Outages

* fix: Preserve Case-Variant Lazy Approval Hook Admission

---------

Co-authored-by: Lia <lia@librechat.ai>
2026-10-04 13:14:48 -04:00
Danny Avila
741978c954
🔭 feat: Recover Stale Chunks Without the Error Page and Ship Client Logs to RUM (#16701)
Some checks are pending
Backend Unit Tests / Build packages (push) Waiting to run
Backend Unit Tests / Codegraph select (push) Waiting to run
Backend Unit Tests / TypeScript type checks (push) Blocked by required conditions
Backend Unit Tests / Circular dependency checks (push) Waiting to run
Backend Unit Tests / Tests: api (shard 1/3) (push) Blocked by required conditions
Backend Unit Tests / Tests: api (shard 2/3) (push) Blocked by required conditions
Backend Unit Tests / Tests: api (shard 3/3) (push) Blocked by required conditions
Backend Unit Tests / Tests: data-provider (push) Blocked by required conditions
Backend Unit Tests / Tests: data-schemas (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 1/4) (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 2/4) (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 3/4) (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 4/4) (push) Blocked by required conditions
Codegraph E2E Votes / vote (full suite) (push) Waiting to run
Docker Dev Branch Images Build / publish (push) Waiting to run
Frontend Unit Tests / Client build recovery regression (push) Waiting to run
Frontend Unit Tests / Codegraph select (push) Waiting to run
Frontend Unit Tests / Build packages (push) Waiting to run
Frontend Unit Tests / TypeScript type checks (client) (push) Blocked by required conditions
Frontend Unit Tests / Tests: @librechat/client (push) Blocked by required conditions
Frontend Unit Tests / Tests: Ubuntu (shard 1/2) (push) Blocked by required conditions
Frontend Unit Tests / Tests: Ubuntu (shard 2/2) (push) Blocked by required conditions
Frontend Unit Tests / Vite build verification (push) Blocked by required conditions
Sync Locize Translations & Create Translation PR / Sync Translation Keys with Locize (push) Waiting to run
Sync Locize Translations & Create Translation PR / Create Translation PR on Version Published (push) Blocked by required conditions
* 🔭 feat: Recover Stale Chunks Without the Error Page and Ship Client Logs to RUM

Stale chunks: a tab left open across a deploy that opens a code-split panel
requests a hashed chunk the new deploy removed. Vite's preload handler hands
the failure to the stale-asset recovery, which reloads, but the import then
resolves to `undefined` and `React.lazy` throws a TypeError into the route
error boundary, so the error page flashes before the reload. Lazy imports now
go through `lazyWithRecovery`/`importWithRecovery`, which turn that result into
a `ChunkLoadError`; the route boundary recognizes chunk failures (and any error
while a recovery reload is underway), asks the page recovery once, and renders
a localized "Updating to the latest version…" status. When the loop guard
declines, the normal error page with its reload action shows instead. The
page recovery is now idempotent within a page, so concurrent callers join the
in-flight reload rather than tripping the guard.

Client logs: with RUM in proxy mode, the client logger's warn/error calls,
error-boundary catches and stale-asset recovery events are exported as OTLP
log records through the authenticated `/api/rum/v1/logs` proxy. Records carry
allowlisted, scrubbed fields only, follow RUM session sampling, dedupe repeats
with a count, are budgeted per minute and per page, batch with backoff, flush
with keepalive on page hide, and stop after persistent failures. The proxy
now refuses non-OTLP content types and applies a per-user rate limit.
`RUM_CLIENT_LOGS=false` turns the export off.

* 🔒 fix: Keep Client Logs Opt-In and Drop Application Error Messages

- RUM_CLIENT_LOGS now defaults to off, like console capture, so enabling
  RUM proxy mode never starts a new log stream on its own.
- Error messages are exported only for engine, browser and library
  generated types (TypeError, SyntaxError, DOMException, AxiosError,
  chunk failures); application errors keep type, status and stack only,
  since their messages can echo prompt or response text. All quoted
  fragments are now redacted.
- Batches are measured in encoded UTF-8 bytes of the exact request body,
  and page hide drains every queued record that fits the keepalive quota.
- Queued stale-asset events are delivered as soon as the log exporter
  starts, independent of the RUM SDK loading, and marked so they are
  never logged twice.

* 🔒 fix: Export Only Known Generated Error Messages and Ack Queued Events

- Error messages are exported only when the whole text matches a known
  engine, browser or library message shape (property access on
  undefined, "x is not a function", fetch/abort/axios status, chunk and
  CSS preload failures). The error class alone no longer qualifies, since
  any code can throw a TypeError carrying arbitrary text.
- Queued stale-asset events are marked logged only after the collector
  accepts the record carrying them, so an undelivered event replays on the
  next page; in-flight events are skipped by the SDK path.
- A fractional RUM_PROXY_USER_MAX below one falls back to the default
  instead of flooring to a limit of zero.

* 🔒 fix: Hold Unacknowledged Asset Events, Re-send In-Flight Logs on Hide

- The RUM SDK flush no longer drops queued stale-asset events whose client
  log record is still unacknowledged: they stay queued and persisted,
  flagged so their SDK action is not repeated, and leave the queue once
  the collector accepts the record.
- Page hide re-sends the records of an unanswered regular request with
  keepalive; each record belongs to the latest request carrying it, so a
  late response to the original request neither marks nor requeues it.
- Client-log export stops when the authenticated layout unmounts.
- The proxy refuses /v1/logs while client logs, console capture and replay
  are all off, so turning RUM_CLIENT_LOGS off also stops tabs that still
  hold an older startup config.

* 🔒 fix: Export Only Complete Stack Frames, Never the Message Header

Stack reduction now strips the V8 `name: message` header (including every
line of a multi-line message) and keeps only lines with a complete V8,
Gecko or WebKit frame shape that ends in a URL or absolute path with a
line number. A message ending in a source-position-like suffix can no
longer pass as a frame.

* fix: centralize RUM delivery and asset recovery lifecycle

* fix: preserve RUM page lifetime and collector acknowledgements

* fix: retain page transport quotas and recover functional chunks

* fix: scope RUM client sessions to authenticated identity

---------

Co-authored-by: Lia <lia@librechat.ai>
2026-10-03 23:17:56 -04:00
lia-by-librechat[bot]
19092e55bd
🖲️ fix: Enable Running Chat Menus and Preserve Renamed Titles (#16697)
Reconciles current dev while preserving manual title ownership, existing menus, and configuration regressions.

Co-authored-by: Lia <lia@librechat.ai>
2026-10-03 23:17:15 -04:00
Lia
ac2b51e98f fix: Order Server Snapshots Against Pending Read Intent 2026-10-03 17:56:52 -04:00
Lia
c85795d08f fix: Fence Reply Read State and Preserve Snapshot Clears 2026-10-03 17:56:52 -04:00
Lia
4bc9c9e5c0 fix: Preserve Unread Intent Across Mixed Backend Versions 2026-10-03 17:56:52 -04:00
Lia
d621cd8b69 fix: Preserve Legacy Unread Reminder Placement 2026-10-03 17:56:52 -04:00
Lia
c41413ad21 fix: Keep Manual Unread Reminders in Date Groups 2026-10-03 17:56:52 -04:00
Marco Beretta
fb1dd57a9b
🔓 feat: Remember Tool Approvals Per Conversation (#16557)
* feat: Remember Tool Approvals Per Conversation

Adds an opt-in "Always allow" choice to the tool approval card. When
endpoints.agents.toolApproval.allowAlways is true, the server marks eligible
paused calls with allow_always; approving with scope "session" stores that
exact tool name on the conversation, and later runs in the same conversation
fold the stored names into the policy as exact-name allow entries.

The server enforces every step: the resume route rejects a session scope the
pause did not offer, eligibility is rechecked against the live policy before
storing, the list is written only through an owner-scoped bounded method, and
generic saves and imports cannot set or clear it. Admin deny and ask rules and
programmatic hooks still win, stored names are ignored under dontAsk or when
the flag is off, and native code tools stay under the code approval picker.
The flag defaults to false, so existing deployments keep prompting.

* fix: Share the Effective Approval Policy and Persist Allows After Resume Fences

Offering, resume re-check, scheduled admission and createRun now read one
policy from buildEffectiveToolApprovalPolicy: endpoint rules healed against
MCP alias spellings, then the conversation's remembered tools. A call held by
a healed ask rule is no longer offered "Always allow", and a scheduled fire
whose known tools are all remembered is no longer rejected as pause capable.

The remembered-tools cap and name length cap move to
toolApproval.allowAlwaysMaxTools and allowAlwaysMaxToolNameLength (defaults
64 and 256). The card stops offering the choice for new tools once the cap is
reached instead of silently approving once.

The resume route stores remembered tools only after the schedule and project
context fences pass; a storage failure still approves the call once.

* fix: Offer Always Allow Only When It Will Hold

Offer allow_always only when storing the name would auto-approve the next
identical call on the run's own path: every MCP spelling of the tool passes
the healed static policy and no programmatic or plugin approval hook can
apply to it (the pause payload does not record which hook asked).

Remembered names now expand to every alias spelling of the same tool, and a
deny or ask on any spelling keeps the tool ineligible. A table-driven spec
walks the invariant through the real hook wiring.

* fix: Recheck Approval Hooks Before Remembering a Resumed Approval

The resume-time eligibility recheck now applies the same programmatic and
plugin PreToolUse hook check as marking, with a hook context built from the
resume request and the live plugin hook source. A hook registered after the
pause turns the choice into a one-time approval: nothing is stored and the
resume continues.

Document that toolApproval.allowAlways should be enabled only once every
replica supports it, since older replicas ignore the choice.

* fix: Judge Always Allow Offers Against the Run's Live Aliases and Active Cap

* fix: Charge Only New Tool Names Against the Remembered Approval Cap

* fix: Recheck Remembered Approvals Against the Paused Run's Aliases

* chore: Sort Imports in Agent Run After Rebase
2026-10-03 11:47:32 +02:00
Danny Avila
c945cafa34
🏃 fix: List Every Running Chat in the Sidebar's Running Group (#16668)
* 🏃 fix: List Every Running Chat in the Sidebar's Running Group

The Running group partitioned the Chats list's own rows, so a running chat
filed in a project, a pinned chat, or one past the loaded pages never
appeared in it. Running chats the loaded rows do not hold are now fetched
by id and merged in newest first, with a project badge on filed chats.
Narrowed lists (search, filters, facets, archive) keep only their own rows.

* fix: Keep Fetched Running Rows Current, Accessible, and Scoped

- Fetch only under the newest-first sort that shows the Running group.
- Re-ask within two seconds for a record not written yet, so a short
  run is not missed; keep the 15-second refresh once it exists.
- Leave archived chats out of Running.
- Patch and clear the fetched rows through updateConvoInAllQueries and
  removeConvoFromAllQueries, so renames, pins and removals show at once.
- Carry the shared-link state the list endpoints derive.
- Seed an empty conversation cache with the fetched record for navigation.
- Describe the focusable row with its project name.

* fix: Preserve Running Chat Cache Updates and Picker Keyboard Activation

* fix: Open the Assistant Picker Through Its Supported Keyboard Handler

* test: Keep SSE Cleanup Query Client Cancellation Compatible

* fix: Keep Temporary Chats Out of the Running Sidebar

* fix: Preserve Running Rows Across Initial Fetch Cancellation

* fix: Preserve Running Removal and Server Read Authority

* fix: Record Running Removal Before Query Creation

* test: Type Running Query Regression Props Explicitly

* fix: Keep Chat Settings Out of Running Sidebar Rows

---------

Co-authored-by: Lia <lia@librechat.ai>
2026-10-02 20:28:02 -04:00