* 🛌 perf: Defer Search Key Dialog Initialization Until First Open
* test: Reuse the Search Dialog Trigger Label in Lifecycle Tests
---------
Co-authored-by: Lia <lia@librechat.ai>
* fix: Move conversation project and PR icons to the leading edge
* fix: Preserve Conversation Focus With Leading PR Icons
* test: Check Icon Order After Leaving Pinned Section
* test: Enable Project Chats Before Checking Their Badges
Localize source pagination labels and the default sources error fallback. Add focused regression coverage and stabilize the oversized screenshot export test.
* fix: Read the Account and Session Together and Test Cancel on a Real Database
- Start the setup user and refresh session lookups together in the cancel controller instead of one after the other, as the opt-in confirmation already does
- Run the cancel controller spec on mongodb-memory-server with the real data-schemas methods, so the session and compare-and-swap predicates under test are the production ones, and add a negative case for each
- Keep only a module wiring test in the CJS controller spec, since the database behavior is now covered where it can run for real
* test: Pin the Cancel Response When the Session Lookup Fails
Both lookups now run before any cookie or write, so a failed session lookup answers 500 with the browser and the stored state untouched. Cover that on the real database.
* fix: Keep the Saved Files Draft Until the File List Loads
After a reload the live file map is empty until the server's file list arrives, and the restore that rebuilds it needs that list. The save effect rewrote the stored draft from the empty map in between, so a pasted-text chip or any other attachment was gone before it could be restored. It now waits for the list. This is what turned the composer-attachments restore scenario red on dev.
* fix: Keep the Provider Message on Classified Rate Limit Errors
* fix: Honor maxProviderErrorChars for Classified Generation Errors
* test: Cover Classified Gateway Errors in the Mock Harness
* test: Cover a Zero Provider Detail Limit on Generation Errors
* refactor: Resolve Classified Provider Errors in the TypeScript Backend
* fix: Redact Provider Details Before Truncating Them
* fix: Wrap Label and Prose Text Between Words Instead of Mid-Word
* test: Cover Word Wrapping in the MCP Trust Disclosure and Bookmark Delete Dialog
* test: Reopen the MCP dialog per width and treat hyphens as break points
* test: Open the bookmark delete confirmation from the keyboard
* fix: Let the MCP Dialog Segmented Controls Wrap on Narrow Screens
* 📏 fix: Measure Usage Percent Against the Allowance Each Period Granted
Store the credits granted at the start of each balance period on the record and measure the usage percent against it, so changing refillAmount or startBalance no longer moves a user's percent until their next grant. Legacy records fall back to the configured amount.
* 🕰️ fix: Ignore a Stored Allotment a Later Refill Has Replaced
Stamp each stored allotment with the time of its grant and measure against it only while no refill is more recent, so a refill by a replica that predates the field falls back to the configured amount instead of reporting usage against the prior period's allowance.
* 🔒 fix: Write the Allotment Grant Atomically and Return Its Period Start
Insert lastRefill with the credit, allotment and grant time when a balance record is created, so a racing creator never moves another's period start past its grant. Return lastRefill even without auto-refill so the client can place a stored allotment in its period, and fall back when it cannot.
* perf: Prefetch Conversation Messages From the Chat Route
The messages request started only when ChatView mounted, after startup config, roles, endpoints, models and the conversation record resolved, although it needs only the route id. ChatRoute now starts it as soon as the id is known for a conversation the cache has never held, sharing the view's query function, and the view's first mount uses that payload instead of fetching it again.
* fix: Keep the Messages Prefetch Mark for the Observer That Uses It
Child observers of the same conversation mount first and cleared the mark before the conversation view subscribed, so the view loaded the messages a second time.
* fix: Show a Failed Messages Prefetch Instead of Requesting It Again
A prefetch that failed left no data, so the view loaded the messages again on mount, and a link to a missing conversation sent two requests. The view now shows a fresh prefetch failure, and the prefetch retries like the view's own load except on a 4xx.
* test: Cover Route-Level Messages Loading on Cold Load, Sidebar Switch and Missing Conversation
* fix: Retry Rate-Limited and Timed-Out Messages Prefetches
* fix: Prove Prefetched History by Reply Identity and Honor Invalidation
A URL load's prefetch starts before the conversation record is cached, so it captured no reply stamp and the seen check loaded an unread conversation's history a second time. Once the record lands, the prefetched history is proven when it holds the exact reply the record names. The mount guards also yield to an invalidation, and the failed-prefetch guard is the default for every observer of the conversation's messages.
* fix: Match Vendor Chunk Rules Against the Module Path, Not the Checkout
The vendor chunk rules tested the absolute module path, so a repository under a directory whose name contains a rule's text (fetch, ky, zod) sent every dependency to that chunk and the PWA precache limit failed the build. The rules now see the path from the first node_modules segment on.
* test: Cover Vendor Chunk Rules Under a Hostile Checkout Path
* refactor: Move Part Helpers and activityLabels Into the Chat Package
activityLabels moves to packages/chat/src/core/parts and exports from
@librechat/chat. useLazyCollapseBody, useProgress and useThrottledValue move
to packages/chat/src/react/parts (@librechat/chat/react). useExpandCollapse,
CopyButton, ActionButton, LangIcon and its icon paths move to
packages/chat/src/components/parts (@librechat/chat/components), since they
read @librechat/client. Specs move with them, client importers and mocks point
at the package entries, and design-lint suppressions follow the moved files.
The fold-type set in activityLabels is built on first use so the module reads
no data-provider enum at load, with a spec pinning its members.
* test: Point the About Spec's Localize Mock at the Package's Copy Button
* chore: Retest Against Current Dev
* fix: Require a Click to Submit Email Verification Links
Mail security scanners (Microsoft Defender Safe Links, Sophos, Hornetsecurity)
open links in incoming mail and run the page's scripts, so the verify page
submitted the single-use token on load and the user's own click then failed.
The page now waits for an explicit confirm button for both sign-up
verification and email-change confirmation.
* test: Cover verification links opened before the user clicks
* test: Isolate the verify click scenario from the submission limiter
* test: Confirm the sign-up link in the email e2e setup
* test: Exercise the shared Button in the verify page spec
* fix: Treat Empty Sandpack Bundler URLs as Unset
An empty SANDPACK_BUNDLER_URL or SANDPACK_STATIC_BUNDLER_URL (common with
${VAR:-} passthrough in Docker Compose) was handed to Sandpack as the
bundler URL, leaving artifact panels blank. buildSandpackOptions now falls
back to the default bundler for an empty value, and the shared-link startup
payload omits empty bundler URLs.
Related to #17790
* test: Cover Empty Sandpack Bundler URLs in Artifact Previews
* fix: Key Sidebar Chat Rows by Conversation Id
Virtualized chat rows were keyed by row index, so a row's local state (an
open delete dialog, a rename field) stayed in its slot while another chat
moved into it, and confirming deleted the wrong chat.
* test: Cover Sidebar Row State When Rows Move
* test: Scope Sidebar Row Scenario Clicks to the Open Menu
* test: Release the Held Archive Reply Before Removing Its Route
* fix: Stop Sidebar Toggle Buttons Forwarding the Click Event as afterSlide
The desktop toggle and the mobile close button passed their onClick handlers
straight through to handleCollapse(afterSlide), so React's click event reached
setSidebarOpen as the afterSlide callback and threw when invoked (directly, or
via requestAnimationFrame on the animated mobile drawer).
Related to #17861
* test: Cover Closing the Sidebar Without a Runtime Error
* fix: Keep the Projects Section Expanded by Default
* fix: Label the Streaming Dot With a Tooltip and an Accessible Name
* fix: Move the Welcome Screen Footer Directly Under the Composer
* fix: Drop the Agent Name From Responses When the Selector Already Shows It
* fix: Align the Sidebar Section Headings With the Date Labels
* feat: Make the Welcome Footer Placement and Response Author Configurable
* fix: Hide the Memories Panel on the Agents Route
* test: Cover the Launch QA Chat Chrome in E2E Scenarios
* test: Assert the Section Heading Padding Merge Without Mocking App Internals
* fix: Read the Response Author Setting Through the Messages Host
* test: Give the Consumer Spec's Messages Host the Author Setting
* refactor: Move the Queued Follow-Up Row Into @librechat/chat
The package owns which queued turn is drawn, when it follows the reader to the end of the thread, and where the composer's queued actions attach. The app keeps who sent it, their icon and how the text reads, passed in as props.
* test: Tag the Queued Follow-Up Row Scenario
The spec already drives the queued turn through its reveal and handoff in the browser; the tag lets the gate record it as evidence for the row the package now draws.
* chore: Retest Against Current Dev
* test: Keep Jotai's Real Exports in the Search Route Spec
PendingTurn now ships from the package components entry, which loads the steer rows and the pane submission atom at import. The spec replaced the whole jotai module with useAtomValue alone, so atom() was undefined and the suite failed to load.
* refactor: Move Conversation Starters Into @librechat/chat With a Starter Button Variant
The welcome screen's suggested first messages render through a package component built on a new starter Button variant instead of a raw button. The app keeps resolving which starters apply (agent, spec, assistant) and sends the chosen text.
* test: Pin the Starter Variant Under the ClickHouse Reference Theme
A starter takes its fill and ink from the theme roles in light and dark, so a theme that repaints the surface repaints the chip.
* fix: Cap the Starter Width at the Call Site, Not in the Button Variant
The Button primitive spec rejects fixed sizes in the variant recipe, so the 16rem cap moves to the package component that lays the chips out.
* fix: Keep the Starter Stagger Ahead of the Unlayered Fade Rule
The unlayered fade-in rule sets the animation shorthand, which resets the delay and fill mode a layered utility sets, so every chip animated at once. The variant now declares the whole animation in one utility, and the cap scenario asserts the computed delay and fill mode.
* fix: Ship the Starter Fade From the Shared Tailwind Preset
The starter variant referenced a keyframe that only the app stylesheet defines, so a host using the published preset would get no entrance. The keyframe and its staggered animation now live in the preset next to the loading dots, and the variant uses the animate-starter-in utility.
* chore: Retest Against Current Dev
* refactor: Move the Attachment Row Into @librechat/chat Behind the Files Host
* test: Cover the Attachment Row Against a Fake Files Host
* test: Run the Files Host Deletion Against the Real Hooks and Mock Only the Service Call
* test: Drive the Fallback Deletion Through the Real File Card
* test: Run the Row's Host Cases Against the Real Thumbnail and File Card
* test: Read the Host Preview From the Thumbnail Image Source
* chore: Retest Against Current Dev
* refactor: Move the Scroll Button Into @librechat/chat
* refactor: Make the Package Scroll Button the Message List Default
* test: Pin the Scroll Control Fade and Its Reduced-Motion Path
* fix: Drop the Scroll Control's IntersectionObserver Guard
The observer starts in an effect, which never runs in a server render, and every browser has the API. The guard existed only for jsdom, which now gets an inert observer from the package's jest setup.
* chore: Retest Against Current Dev
* refactor: Retire Host Tool Outcome, Sibling and Approval Members
The package now owns the tool outcome rules and the attachment merge they
read, selects the visible sibling through its own atom, and derives the steer
path's code approval mode from raw inputs. ChatHost loses getMappingOptions and
useSetSiblingIdx; SteerHost.useCodeApprovalMode becomes useCodeApprovalInputs.
* refactor: Select the Branch Tail Inside @librechat/chat
The tail of the branch on screen becomes package logic, read through
useBranchTail. ChatHost loses useLatestMessage and useLatestMessageId;
SteerHost.useLatestMessage becomes the useRouteConversationId adapter.
* test: Exercise Steering Against a Real Message Cache
The steering spec mocked React Query to return one message list for every key, so
it could not notice a read of another conversation's cache or a tail that stops
following the cache. It now provides a real QueryClient, seeds each conversation
key, and covers the route and another chat holding different tails and a cache
that hydrates after mount.
* fix: Show MCP Server Titles in the Tool Library and Search by Them
Tool Library cards and agent tool rows showed the MCP server's config key because buildCatalog named each item after it, and search could only match that key. Name items from the resolved title in server.metadata, falling back to the key. Search also matches the key through the item id, as the MCP Servers panel does, so existing key searches keep working.
* test: Cover MCP Server Titles in the Tool Library and Agent Tool Rows
* test: Find the E2E Memory Card and Row by Title in MCP Specs
* refactor: Read the Thread Panel's Jotai State Through the Chat Surface
* refactor: Move the Subagent Thread Panel Into @librechat/chat
* test: Spec the Subagent Thread Panel Against Fake Hosts
* test: Cover the App Subagents Host Adapters the Panel Move Relies On
* fix: Style the Moved Subagent Panel With Shared Variants
* test: Pin the Shared Variants the Panel Draws Its Picker and Inline Actions With
* perf: Keep the Subagent Thread Panel Out of the Boot Bundle
* refactor: Add the Thread Panel's Reads, Writes and Layout to the Subagents Host
* refactor: Read the Subagent Thread Panel's App Capabilities Through the Subagents Host
* fix: Hand the Thread Panel the Query's Own Stable Refetch
* refactor: Read Subagent Conversation Data Through the Subagents Host
* refactor: Move Subagent Conversation and Shared Activity Dialog Into @librechat/chat
* test: Spec the Subagent Conversation and Shared Dialog Against Fake Hosts
* fix: Keep the Panel Selection Atom Out of the Components Entry
* test: Open a Shared Child Run in Its Activity Dialog
* fix: Style the Moved Subagent Dialog With Variants and Static Classes
* test: Pin That a Shared Child Run Card Stays Closed
* chore: Retest Against Current Dev
* refactor: Derive a Send's Code Decision Inside @librechat/chat
TurnServices.resolveCode computed the code workspace and approval a send
carries in the app. It becomes readCodeInputs, a storage read of the raw values,
and the package derives the decision through resolveTurnCode. The read goes
through a ref updated each render, so a captured adapter still reads the newest
render's values.
* test: Close Mocked Readers Over Each Render in the Freshness Spec
* test: Close the Mobile Drawer Through the Race-Tolerant Helper in Two Agent Specs
Two specs closed the drawer after selecting an agent with a bare click on
Close sidebar. The drawer closes itself as the selection lands, so the click
waited on a button that stopped being visible and ran into the 120 s test
timeout on phones. closeMobileDrawer, which #17764 added for this, handles that
race and keeps the inert check.
* refactor: Ship Icon Sizes, Status Type and the Label Sweep From @librechat/client
* test: Prove a Consumer Gets the Shared Part Classes From the Published Stylesheet
* test: Stop Asserting the Blockified Display of the Elapsed Reading
* fix: End the Status Row Type Chain in a Length for Standalone Consumers
* refactor: Move the Message Rows Into @librechat/chat
MessageRender, Message, MessageContent, ContentRender, MessageParts and the thread's ThreadMessage now live in the package, and the thread renders them directly, retiring MessagesHost.renderMessageRow. Pieces owned elsewhere reach the rows through new host slots.
* test: Render the Real Thread Message in the Thread Specs
The thread specs replaced ThreadMessage with a fabricated row, so sibling paging and edit assertions drove the stub. They now render the real row chain with fake hosts and page and edit through its real controls.
* test: Keep a 12,000-Message Chain Covered at the Row Resolver
The thread specs now render real rows, so their large-chain case was cut to 60 messages. The 12,000-message chain, which guards the iterative branch walk and row reuse on a long conversation, moves to the resolver spec where it does not mount every row.
* test: Keep the Child Thread Spec Rendering Real Rows Under the Client Mock
The child-thread spec relied on the test host's renderMessageRow slot to draw nothing. The thread now mounts the package rows directly, so the spec's agents map and client package mocks have to cover them.
* fix: Encode Unicode Filenames in Project File Uploads
Project uploads sent the raw filename, which multer reads as latin1 and the upload route then decodes with decodeURIComponent. Non-ASCII names were garbled, a stray percent sign failed with a 400, and a valid escape such as %20 was silently rewritten. Percent-encode the name the same way chat uploads do.
* test: Cover Unicode and Percent Project Upload Filenames
* fix: Let Native Azure Deployments Declare Their Reasoning Efforts
The composer effort control needs explicit capability evidence on Azure,
because a deployment name does not identify its model, but the native
Azure config had no way to supply any, so the control could never appear.
Add an optional per-model reasoningEfforts list to Azure groups. The
endpoints config serves only model names and efforts, and the composer,
the submit check and the server override validation all resolve them
through getReasoningParamDefinitions. Undeclared deployments stay without
a control and model spec locks still apply.
* test: Assert Auto as the Reset Button in the Azure Effort Scenario
* test: Ignore Looping Animations When the Memory Alert Settles
The spec waited for every animation in the document to finish. A looping one
never does, so it hung whenever earlier specs in its shard left a chat list
long enough to show pulsing skeleton rows. Adding any spec can move it there:
the shard planner places it in shard 9 instead of 6 with this branch.