* fix: Keep the Snapshot When the Terminal Write Settled for Reconciliation
* fix: Promote a Reconciled Compaction Snapshot to the Terminal Row
* fix: Anchor and Envelope the Reconciled Snapshot by Its Claim
* test: Cover the Abandoned Compaction Settling After Its Run in E2E
* fix: Withhold the Disconnect Snapshot of Any Durably Settled Turn
* fix: Promote Only a Same-Epoch Reconciled Snapshot and Settle Stopped Compactions
* fix: Plan the Disconnect Snapshot in packages/api and Check the Response Row Before Promoting
* fix: Read the Disconnect Snapshot Rows in the Response Conversation
* fix: Check the Anchor-Derived Error Row Before Promoting a Reconciled Snapshot
* fix: Log a Failed Disconnect Snapshot Plan Instead of Rejecting the Listener
* fix: Let a Reconciled Compaction Promote After an Earlier Live Snapshot
* refactor: Decide the Repeat Disconnect Write in the Snapshot Plan
* refactor: Report Failed Snapshot Row Reads Through the Plan
* fix: Stamp a Promoted Disconnect Snapshot and Read Its Rows Together
* fix: Derive the Compaction Error Row ID Through the Shared Helper
* fix: Plan a Saved Live Compaction Snapshot Again Once Its Turn Settles
* refactor: Queue Disconnect Snapshots and Settle Them in packages/api
* fix: Never Count the Compaction Anchor as Its Own Terminal Row
* fix: Settle Disconnect Snapshots Before Terminal Cleanup Releases the Turn
* refactor: Add the Core Chat Class With a Serial Job Executor and React Query State
* fix: Report an Attachment's HTTP Failure as a Disconnect and the Turn's Conversation on Finish
* fix: Report a Stream That Fails While It Is Read as a Disconnect
* fix: Keep an Attachment Failure a Disconnect When the Host Reducer Throws on It
* fix: Treat a Resumed Start as an Attachment and Drop a Replaced Start's Optimistic Rows
* fix: Undo the Whole Optimistic Write of a Start the Server Replaced
* fix: Give Each Optimistic Write One Rollback Record and Stop a Disposed Chat Writing State
A turn keeps its optimistic write on the active request, so a disposal before the start was sent undoes those rows as a replaced start already did, and a removed row is restored next to its surviving neighbors instead of at its old index. A disposed chat no longer moves the shared status or connection, so a listener that disposes on a rollback notice cannot leave the state reconnecting. A start that fails with ERR_INTERNET_DISCONNECTED is a disconnect like ERR_NETWORK, and the React Query state rechecks a host store that changed between a version read and its subscription.
* fix: Roll Back the Rows a Store Committed, Not the Rows the Chat Handed It
A React Query cache with structural sharing commits a changed row as a copy, so a replaced start compared its rollback record against objects the cache never held and kept the optimistic edit. The record now takes the list as the state reads it back after the write.
* fix: Record the Optimistic Rows a Store Committed Before Telling Subscribers
A listener that writes the shared state when the chat announces its optimistic write no longer lands in that write's rollback record, so a replaced start keeps the listener's rows. The record is taken before anyone is notified, and a store's report of the chat's own write waits for the chat's announcement instead of running inside the write.
* fix: Stop a Stream Event Once a Listener Disposed the Chat on Its Write
A listener that disposes the chat while an event's write is announced no longer lets that event move the shared status to streaming or reach onEvent after teardown.
* fix: Scope Optimistic Rollback to the Rows the Write Itself Changed
The rollback record kept the whole list the store committed, so a row a store subscriber appended while the write was committed was undone with the turn, and a subscriber that disposed the chat inside the write left the turn's rows behind because no record existed yet. The record now holds, by message id, only the rows the write added, replaced or removed, each under the identity the store committed it with; undo restores or drops those and leaves every other row. A dispose inside the write is undone once the record exists.
* fix: Leave a Turn Row a Store Subscriber Edited Inside the Write Out of Its Rollback
A store that notifies its subscribers synchronously can hand back one of the turn's rows already edited by a subscriber, and the rollback of a replaced start then deleted or overwrote that edit. The record now claims a committed row only when it is the written row or a structural copy of it.
* perf: Index Hot Lookups and Make Message Cursor Pagination Stable
Add narrow indexes for session refresh-token deletes, user-only tool call deletes, queued-turn delivery and reconciliation claims, agent code environment references, and updatedAt message pages. Add a TTL index to the KeyvMongo collection. getMessagesByCursor now sorts and pages on a unique (sortField, _id) tiebreaker with a millisecond-precise cursor while still accepting legacy cursors, and GET /api/messages caps pageSize in a TypeScript helper.
* fix: Keep the Message Id for the Cursor Under the Client Projection
* fix: Declare select on the Message Cursor Method Type
* feat: Make the Message Page Size Ceiling Configurable
* fix: Clamp the Default Message Page Size to the Configured Ceiling
* test: Cover Message Cursor Paging and Page Size Cap End to End
* fix: Continue Message Cursors Whose Sort Value Is Empty
* fix: Include Missing Sort Values When Paging Messages Descending
* perf: Resolve the Message Page Ceiling Beside the Ownership Read
* fix: Observe the Ownership Read While the Page Size Resolves
* style: Sort Imports in the Message Page Module
* refactor: Move Page Size Read Observation Into the API Package
* fix: Keep Missing and Empty Sort Values Distinct in the Message Cursor
* fix: Page Past Messages With a Missing Timestamp
* fix: Honor Documented Azure Model Assistants and fileConfig.stt Keys
Read the model-level Azure assistants flag from the group's models entry,
validate and merge fileConfig.stt, drop two never-read image tool env vars
from .env.example and fix the SharePoint scope example.
* test: Cover Model-Level Azure Assistants Through Config Overrides
The mock harness runs without CONFIG_REDERIVE_ENDPOINTS, so override
groups are never resolved there; cover the override path in the
resolution spec instead of e2e.
* fix: Return approved tool and generation error text instead of raw exceptions
* fix: Redact generation error text without the data-schemas helper
* fix: Redact credentials and emails from shown generation errors
* refactor: Move the Wolfram status policy into packages/api
* test: Fix the Wolfram probe constructor and jest summary match
* test: Match the jest pass count through color codes
* fix: Redact credentials a tool input error echoes from its arguments
* fix: Drop free-text fields from typed generation errors under a content policy
* fix: Keep only the code and numeric fields of typed errors under a content policy
* fix: Fence ACL Viewers and Surface Revocation Failures When Removing Shared MCP Servers
Account erasure and server deletion now enumerate users the view ACL names
directly or through a group, so viewers without a personal OAuth token are
fenced and disconnected too. Erasure runs the OAuth teardown in strict mode,
which clears local credentials and then fails when the provider refuses a
revocation, keeping the server as the retry anchor, and holds every user's
teardown fence until the server delete commits.
* test: Type the Revocation Failure Cleanup Fixtures
* fix: Renew Retained OAuth Teardown Fences Before Deleting the Server
A teardown lease lasts 15 minutes, so a large erasure could outlive the
first fences it holds. Leases can now be renewed by their owner, and
erasure renews every retained fence right before the delete, failing
without deleting when one lapsed and another writer took it.
* fix: Report Refused MCP Revocations Without Blocking Account Erasure
A provider that refuses revocation, combined with a viewer who signs in
again between attempts, could keep an erasure failing indefinitely. The
strict teardown now throws a coded MCPOAuthRevocationError after clearing
local state and handing over its fence; server removal collects those as
refusals, logs each user and token type whose grant may remain valid, and
proceeds. Local failures (token delete, fence, ACL) still fail closed.
* fix: Annotate the Revocation Error Code for Isolated Declarations
* 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
* fix: Harden Timer Sweeps, SSE Writes, and Violation Counters
Guard SSE writes against ended or destroyed responses through one helper, catch and single-flight the job store and TTL cache cleanup timers, serialize in-process counter updates, cap the violation log, prune stale OAuth failure records, batch the active-job lookup, and count Redis keys with DBSIZE.
* refactor: Drop the redundant violation log entry copy
* refactor: Log single-flight sweep failures from the API package
* test: Cover active generation listing and client disconnect mid-stream
* refactor: Configure violation log retention and move title timeout into the API package
* feat: Configure OAuth failure retention through mcpSettings
* fix: Prune OAuth failures promptly under short retention
* fix: Mark the Escape that closes a Dropdown list as handled
A Headless UI dialog such as Settings closes on any Escape not already
handled, and the Dropdown list closed on Escape without marking it, so
one press closed the list and Settings together. The list now marks the
Escape it handles, so its container stays open until a second press.
* fix: Leave Escape to the container once the Dropdown list is closing
The list closes with a transition and Ariakit keeps it mounted until the
transition ends, so an Escape pressed right after a pick still reached
the list's handler and was marked handled, leaving Settings open.
The drawer collapsed on any Escape that reached the document, including
one a dialog above it had already handled, so a single press closed the
dialog and the drawer and the dialog could not return focus to its
trigger. The drawer now stands down when the Escape was already handled.
* refactor: Restyle Connected Accounts Settings Row
* test: Cover Connected Accounts States in Mock Scenarios
* test: Open Settings Through the Drawer on Mobile
useAdaptiveSSE and useResumableSSE now live in the chat package and own the
run, the stream id and how a stream re-attaches. The app supplies the services
a resumable stream runs on and the Assistants stream through a StreamHost,
mounted in Root beside the chat and steer hosts.
useChatHelpers now builds the pane contract from a ChatHost the app supplies:
its pane store, message query cache, turn builder, thread selection, abort
transport and settings. The stop path lives in its own module, its spec runs
in the package against a host with no app behind it, and the app mounts its
host in Root beside the steer host.
* 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
Callers sized and layered Dropdown lists through ad hoc sizeClasses, while
DropdownPopup takes sameWidth, minWidth (capped to the room the list has)
and gutter. Dropdown now takes the same three, and the Settings dropdowns
move onto them and drop z-50 classes the dialog layer already overrides.
Dialog, DialogContent, DialogTitle and the other parts, and
DialogTemplate, are now exported beside their OG names as the same
components, so new code and the docs can use the plain names while the
existing call sites keep working unchanged.
* ci: Add README Translation Sync Workflow
* ci: Pin create-pull-request Action in README Sync
* ci: Check Translation Content and Attribute Text in README Sync
* ci: Harden README Translation Validation and Switcher
* ci: Validate Protected Tokens in README Translations
* ci: Keep Link Order and Fence Boundaries in README Translation
* ci: Validate README Translations Against the Markdown Tree
* ci: Check Short Prose and Link Metadata in README Translation
* ci: Handle Brand Suffixes, Titles and Table Alignment in README Validation
* ci: Preserve Emoji, Image Alt and Raw Code in README Validation
* ci: Stop Rejecting Faithful Translations That Keep Language Names
* ci: Refresh Switchers in Unselected README Translations
* ci: Compare Comment Contents and Deduplicate Pending README Sections
* ci: Revalidate Cached README Translations and Resolve Reference Links
* ci: Keep Code in Raw HTML Blocks and Accept Full-Form Reference Translations
* ci: Read Alt Text of Reference-Style README Images
* ci: Test the README Translation Helpers on Pull Requests
* ci: Keep Reference Image Alt Text and Translate Definition Titles
* ci: Resolve README Reference Definitions Before Classifying Prose
* ci: Resolve README Footnotes When Validating Chunks
* ci: Point README Fragment Links at Translated Heading Anchors
Same-document links kept the English heading slug, which no longer exists once GitHub derives anchors from the translated heading text. Assembly now rewrites #fragment links in Markdown links, definitions and raw HTML hrefs to the slug of the heading at the same position, using github-slugger.
Closesberry-13/LibreChat#384
* fix(agents): skip the empty-memory notice for agents that cannot use memory
Since #16301 formatMemoryContext('') returns the bare memory instructions sentence, and
prepareRuntimeAgent applied it to the primary agent whenever the user had no saved memories.
An agent with no memory tools and no automatic memory extraction can neither read nor write
memory, so the sentence told the model nothing it could act on, yet it reached the model as
per-turn context. The empty-store notice is now added only when the agent has memory tools or
automatic extraction is on. Saved memories are still injected as before.
* fix(agents): distinguish relocated context from user input
* fix(agents): narrow runtime context types
---------
Co-authored-by: shars <32410570+Shabonasar@users.noreply.github.com>
Co-authored-by: Lia <lia@librechat.ai>
* 🪡 style: Separate Attachments from Message Bubbles
* fix: Include Attachments on Structured User Rows
* fix: Normalize Attachment Text Parts Before Trimming
* fix: Preserve Attachments on Protected User Messages
* fix: Keep Message Width Independent of Attachment State
---------
Co-authored-by: Lia <lia@librechat.ai>
Accordion, Breadcrumb, CheckboxButton, FormInput, QuestionMark,
InputWithDropdown and the Radix DropdownMenu had no users in the app or
the package. The account menu's dividers were the DropdownMenu's
separator inside an Ariakit menu; they are now the Ariakit menu's own
separators and draw the same.
The assistant picker, the assistant model field, the assistants endpoint
settings and the dynamic parameter dropdown were the last users of the
HeadlessUI SelectDropDown and its MultiSearch. Dropdown gains a muted
placeholder and an aria-invalid field state, and each field is now named
by its visible label.
* refactor: Remove Legacy Dialog and DialogTemplate from @librechat/client
The assistant delete confirmation was the last consumer of the legacy
Radix Dialog and its DialogTemplate. Move it to OGDialog and
OGDialogTemplate with the shared Button trigger, matching the agent
delete button, then drop both components, their barrel exports and the
spec entries that listed them.
* test: Cover the assistant delete confirmation dialog
* test: Match toast text exactly and clear the delete mock before cleanup
* test: Move the close-target and scrim scenarios off the removed Dialog
* feat: Let Dropdown work inside dialogs and take the field list roles
Inside a dialog the list renders in place, so the dialog's focus trap and
aria-hidden pass no longer cut it off, and it layers above the dialog. A
field Dropdown's list now takes listMinWidth, listMaxHeight and the icon
size role, and is never narrower than its trigger.
* refactor: Move the code tool selects onto Dropdown and remove Select and Combobox
The four code tool settings selects were the last users of the Radix
Select, and Combobox, its only other consumer, had none. Their tests and
the nested popover scenarios now drive the Dropdown.
* refactor: Read the Pane Conversation Through ChatSettings and Drop the Orphan Abort Scroll Atom
* test: Cover Returning to a Running Chat Through the Router
- GET /resolved resolves a group or user profile in the partition its document belongs to, as
writes judge it: for an admin without a tenant reading a tenant's profile, that tenant's
librechat.yaml and __base__. GET /catalog resolves such a scope there too, instead of
answering 404, and GET /effective finds a user by id the way profiles are addressed and
resolves them in their own tenant: their role, groups and documents there.
- findPartitionUser becomes findPrincipalUser, which also returns the user's tenant.
- Admin role operations address the role of the caller's tenant partition: the role lookup
(getPartitionRole), listing, creation's name check, the members a rename migrates or a deletion
reassigns, the members listed and counted, and the ACL entries (deletePrincipalAclEntries) and
grants a deletion removes. A member added or removed by id must be a user of that partition.
- getRoleByName, which every request's permission checks read, reads the role of the caller's
partition too: outside a tenant and under the system context the platform-level one, never an
older tenant role of the same name. updateRoleByName without an id and updateAccessPermissions
for a role read without its _id write that role, so the legacy permission route changes the
platform role. The grants route checks a role exists with getPartitionRole.
- runInPartition moves a read into another partition only from outside a tenant, and rejects
leaving an active one.
- deleteGrantsForPrincipal and findGrantsForPrincipal without a tenantId reach only
platform-level grants, as moveGrantsToPrincipal does.
- updateRoleByName takes { id } to change one role document; renames, their rollback,
description updates and updateAccessPermissions write the document they read.
- The exported keyed rename helpers (applyConfigChange rename, renameConfigEntryTombstones)
refuse a new name no keyed path can address, as the admin routes do.
Move every local prompt group and native-revision read and write behind
one PromptStore (createPromptStore) and reduce the native adapter to
resolvePrompt, the contract the Langfuse adapter already has. The
service receives { store, sources } and dispatches resolution by group
source. Service behavior, errors (including unsupported), database
calls and result shapes are unchanged.
Co-authored-by: Rebase Probe <probe@example.com>
* chore: Update package dependencies across multiple modules
- Upgraded `@azure/identity` to version 4.14.0 in package.json files.
- Updated `multer` to version 2.5.0 and `nodemailer` to version 10.2.1.
- Incremented `undici` to version 7.30.1.
- Updated `@happy-dom/jest-environment` to version 21.0.4.
- Incremented `qs` to version 6.16.1 and `fast-uri` to version 3.1.9.
- Updated `serialize-javascript` to version 7.1.4.
- Updated `zod` to version 4.6.7 in multiple modules.
These updates ensure compatibility with the latest features and security improvements.
* chore: update bun.lock file
* fix: Close Gaps in the css-colors Triplet Check and the Disabled-Recipe Rule
The triplet check now reads angle channels, and the disabled-recipe rule accepts spelled recipes under the same or fewer enclosing variants, resolves cva and constant class strings, and handles spread strings, per-dim primitive coverage and implied selectors.
* fix: Read Recipe Markers Anywhere in the Variant Stack and Keep Object Spreads
* test: Cover Spelled-Out Disabled Recipes in the Design Lint Scenario
* fix: Keep Stateful Arbitrary Disabled Selectors Unrestored and Order Arbitrary Enclosing Variants
* fix: Order Enclosing Variants Whenever an Arbitrary Selector Is Present
* fix: Pin the Disabled Marker Position When Arbitrary Variants Enclose a Dim
* fix: Order Child Selector Variants Like Arbitrary Ones
* fix: Skip Unplaced Disabled Variants and Read Math Functions by Token
The disabled-recipe rule now skips utilities under arbitrary variants it cannot place instead of guessing how a recipe orders against them, and unwraps TypeScript assertions on spread and class-map recipes. css-colors classifies any innermost math function by its tokens, so rounding strategies and constants no longer hide an angle-led triplet.
* fix: Read Any Fixed Math Function as a css-colors Channel
A math function over numbers and angles is a fixed channel in any position, so unit cancellation (calc(90deg / 1deg)) needs no unit algebra, and trigonometric functions and sign are fixed whatever their arguments (atan2(1px, 1px), sign(90deg)).
* fix: Unwrap Constant Class Strings and Honor Class-Map Overrides
A const initializer under as const or satisfies is read like a plain string, and a class-map recipe entry no longer counts when a later spread or the same key can overwrite it.
* fix: Keep Angle Math Results and Disjoint Spreads Out of Overrides
An angle-valued math result stays an angle, so it reads only as a leading hue, and a later object-literal spread invalidates a class-map recipe only when it sets the same key.
* fix: Place Valued data-disabled Self Selectors in disabled-recipe
* feat: Branch Tool Fold Rails Into Each Row
Draw each open fold's rail as a trunk with a curved branch into every
row, measured from the rows themselves. Hovering a row lights the route
along the tree: out of the previous branch, along the trunk and into the
new one, at a steady pace. Layout changes under a still pointer (folding,
streaming, scrolling) re-hit-test instead of clearing the path.
* fix: Retrace the Fold Path When Its Row Moves Mid-Trip
A row that moved while the lit path was still traveling to it kept the
trip measured to its old position, so the path ran the old distance and
jumped the rest. Start a fresh trip from the path's current position
whenever the destination row moves.
* test: Cover the Tool Fold Tree With Scenario Specs
One tagged Playwright scenario per contract behavior: branches into each
row, the hover route from the header, nested folds, travel along the
tree, a click that unfolds the hovered row, reduced motion, right-to-left
mirroring and touch.
PromptService gains importSourceGroup, which finds or creates a source
pointer group, grants the PUBLIC viewer role and rolls the group back if
the grant fails. The Langfuse catalog sync calls it instead of four
storage callbacks and two Mongo error predicates, and the prompt service
is composed once in api/server/services/Prompts.js and passed to the
prompt routes, linked instructions, instructions prompt access and the
Langfuse sync runner.
Co-authored-by: Rebase Probe <probe@example.com>
* feat(prompts): sync Langfuse prompts into the catalog
* refactor(prompts): compose the Langfuse prompt sync runner outside the admin handler
Add createLangfusePromptSyncRunner, which binds the lock, the prompt-group
methods, the ACL grant and the Mongo error predicates once and returns a
runner that takes the per-request source, connection-bound listPrompts,
lock lease and page cap. The admin handler receives that runner as one
dependency instead of forwarding its parts, and its config method
signatures return a LangfuseAdminConfig interface in place of Mongoose
document types.
In api, api/cache/distributedLock.js creates the one DistributedLock for
the process and api/server/services/LangfusePromptSync.js composes the
runner once with it; the admin route imports the composed runner.
* fix(prompts): report incomplete Langfuse syncs and gate the sync action
- Refresh the prompt-group and effective-permission queries after a failed
sync too, because earlier imports can already be committed.
- Return `complete: false` when the page limit stops a sync before the last
upstream page, and show a warning instead of the success message.
- Show the Sync prompts action only to users with `manage:prompts`, the
capability the sync route requires. Resolve the Langfuse startup-config
capabilities in one batched lookup.
- Document that an interrupted import can leave a group without its initial
PUBLIC grant, and that a page in progress can outlast an expired lease.
---------
Co-authored-by: Rebase Probe <probe@example.com>
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.