* fix: Count Memory Tokens After the o200k Encoding Loads
Memory create and update routes, the by-id handler, and the memory agent's
set_memory tool persisted Tokenizer.getTokenCount, which returns the UTF-8
byte length for long text while o200k_base is still loading. Await
countTokens instead so the stored tokenCount is the real count.
Related to #17842
* test: Cover Memory Token Counts Saved Before the Tokenizer Loads
* test: Mock countTokens in Memory Tool and Route Specs
* 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: Report Zeroed Summary in SharedLink Permissions Dry Run With No Links
The dry run returned early without a summary when the sharedlinks collection was empty, so the CLI crashed reading result.summary.totalLinks. Dry run now falls through to the summary counts; live runs keep the early no-op return.
Related to #17887
* test: Cover SharedLink Migration CLI on Empty and Legacy Collections
* 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
* fix: Resolve User and Group Balance Overrides on Sign-In
Login routes pass the lean user document from the passport strategy, which has _id but no id, so the balance sync resolved config from the role alone and wrote role-level balance settings over user and group overrides on every login.
* test: Cover the Sign-In Balance Sync With a User Override Scenario
* fix: Report Union, Object, Array and Later Fields in Tool Validation Feedback
Type checks now cover integer, array, object and null, accept any member
of a declared type union, and scan every schema property. The cap of 8
applies to reported fields instead of inspected properties, so a mismatch
past the eighth property is still named.
Related to #17875
* fix: Read anyOf, oneOf and nullable Types in Tool Validation Feedback
Pydantic and zod describe an optional object as an anyOf of object and null,
and the Gemini sanitizer collapses unions into a type plus nullable: true.
Both shapes now report the field, and a valid null is no longer flagged.
Adds a mock MCP tool with a nullable object after its eighth property and a
scenario that checks the model receives the field name but not the value.
* 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.
* test: Cover a Deployment Skill File Removed at Runtime
* fix: Name the Skipped Skill File in the Console Log
The default console format prints the message and request context but drops metadata, so a relativePath passed as metadata only reached the JSON file log.
* test: Keep the Removed-File Fixture Skill Out of the Palette
As a user-invocable skill it added a row to the virtualized composer palette and pushed the Your files section out of the rendered window, which broke palette-show-all.spec.ts.
Multer assumes latin1 for multipart filenames, and the skills routes have no decode step, so a non-ASCII name reached the handlers garbled. A file name content filter could not match it on import, and the file upload route stored the garbled name.
* 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
A deployment skill file deleted from a running instance stays registered, and
fs.createReadStream only reported the missing path as a stream error once the
multipart upload was already in flight, which aborted the whole batch. Open the
file first so ENOENT rejects the promise primeSkillFiles already inspects, and
log the relative path of any file whose stream could not be acquired.
The withheld-reply scenario restored the unread baseline in Mongo right after the reply tab finished, while that tab was still posting its own seen acknowledgement. When the acknowledgement landed second it overwrote the baseline, the first tab polled a conversation the server considered read, and its dot never appeared. The sibling scenario already waits for the acknowledgement; this one now does too.
* 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.
The shared client setup gained an inert IntersectionObserver in #17753. It
never reports, so useArrivalFocus no longer arrived in jsdom: the positive
cases failed and the negative ones passed without testing anything.
Remove it inside the arrival focus blocks so the hook takes its no-observer
path, and restore it afterward. Scroll-dependent cases keep their own observer.
* fix: Retire Credentials by Their Committing Write and on Opt-In 2FA
Re-date password reset and enrollment cutoffs once the write that set them commits, so a credential minted while the write is in flight is retired. Opt-in 2FA confirmation now stamps twoFactorEnrolledAt and rotates the session like required enrollment. OpenID refresh ends a session established before a reset or enrollment instead of spending its IdP grant.
* fix: Bind Opt-In 2FA Rotation to the Caller's Refresh Session
Confirmation now requires the refresh session the request was issued with, rotates it in place and revokes only the others, so an access token on its own cannot trade enrollment for a long-lived session. The OpenID retirement check moves into the refresh recovery service and ends the session through the existing session-missing path, leaving the CJS controller unchanged.
* fix: Clear a Retired OpenID Session Against the User It Was Checked For
* refactor: Inject the Refresh Secret Into OpenID Recovery
* fix: Report a Reset Whose Cutoff Could Not Be Re-Dated
A failed re-stamp now propagates as RETIREMENT_RESTAMP_FAILED. The reset controller still revokes sessions and passkeys and answers CREDENTIAL_RETIREMENT_INCOMPLETE; the CLI re-stamps after its revocations and exits non-zero; enrollment revokes sessions before the re-stamp and mints nothing when it fails.
* fix: Re-Date the Reset Cutoff Only After the Link Is Consumed
The web reset re-stamps credentialsChangedAt in the controller once resetPassword has committed, consumed the token and sent the notice, so a failed re-stamp can no longer leave the link replayable. Revocations still run and the response reports CREDENTIAL_RETIREMENT_INCOMPLETE.
* fix: Retire Credentials on Every Exit Path After a Reset Commits
resetPasswordWithToken owns the post-commit steps: deleting the link and sending the notice no longer throw, and a link issued before the account's last credentialsChangedAt is refused, so it is spent even when its deletion fails. The reset write is conditioned on the cutoff it read, so one link commits once. The controller re-dates the cutoff and revokes sessions and passkeys whenever the password changed, and answers CREDENTIAL_RETIREMENT_INCOMPLETE if any of that fails.
* fix: Spend Undated Reset Links and Move the Reset Notice Into TypeScript
* fix: Tell the User When a Reset Could Not Sign Out Every Session
The reset page now recognizes CREDENTIAL_RETIREMENT_INCOMPLETE, shared from librechat-data-provider, and shows a localized warning that the new password is active with a sign-in action, instead of reporting the spent link as invalid.
* perf: Re-Date the Reset Cutoff From the Committed Write
The committed reset hands its credentialsChangedAt back through PasswordResetResult, so the controller re-stamps without a second user read.
* fix: Retire Every Superseded Credential Before Minting on 2FA Enrollment
Opt-in confirmation and setup finalization now revoke sessions, re-date twoFactorEnrolledAt and wait for the auth cache to drop the pre-enrollment document, running every step even when one fails. If any step fails they mint nothing and answer CREDENTIAL_RETIREMENT_INCOMPLETE; the settings dialog keeps 2FA on with a warning and the setup screen sends the user back to sign in with the new factor.
* test: Cover the Settings Warning When 2FA Enrollment Leaves Sessions Behind
* fix: Send the User Back to Sign In After an Incomplete Opt-In Enrollment
Enrollment retires the confirming tab's bearer, and an incomplete retirement mints no replacement, so the settings dialog now shows the backup codes and then signs out to the login page, whether the user completes setup or closes the dialog.
* test: Run the Retirement Warning Scenarios Against Their Own Signed-Out or Fresh Accounts
* test: Open the Sidebar Drawer Before the Account Menu on Phones
* fix: Report a Committed Opt-In Enrollment When Rotating the Session Fails
Once 2FA is promoted, a later failure in confirm2FA withdraws whatever session it may have minted and answers CREDENTIAL_RETIREMENT_INCOMPLETE, so the settings dialog hands over the backup codes and signs the user in again instead of reporting an invalid code.
* test: Prove an Incomplete Reset Does Not Resume the Retired Session
The Sign in action sends a browser with a live session through /login for about 150 ms before it lands in chat, so the signed-in version of the warning scenario only passed when the URL check caught that window. The warning scenario runs signed out, and a new scenario holds a pre-reset session and asserts its refresh is refused and the user stays on the login page.
* fix: Settle the Auth Cache After the CLI Reset's Final Cutoff Write
* test: Require the Login Form After Signing In From a Signed-Out Reset
* fix: Explain an Incomplete Session Retirement Before Restarting Sign-In After Required 2FA Setup
* perf: Start the Opt-In Enrollment User and Session Reads Together
* refactor: Move the Context Usage Popover Pieces Into @librechat/chat
* test: Cover the Context Usage Pieces in the Chat Package
* fix: Ship the Collapsible Animations With the Shared Tailwind Preset
* test: Keep the Expanded Breakdown Choice Across Remounts
* test: Assert the Absent Compaction Hint by Its Fixed Copy
* refactor: Give Collapsible and HoverCard the Breakdown Disclosure Styles
* test: Cover the Breakdown Roll and Remembered Choice in the Browser
* chore: Retest Against Current Dev
* refactor: Move the Messages View Provider Into @librechat/chat
* refactor: Render the Package Message List by Default in ChatScreen
* fix: Drop the Rail's IntersectionObserver Guard for a Package Spec Stub
Nothing renders the rail without a browser: its observer starts in an effect, which never runs in a server render. The guard existed only because jsdom lacks the API, so jsdom now gets inert observers and matchMedia from the package's jest setup, and the spec's own stubs, which no longer matched the DOM lib's IntersectionObserver type, are gone.
* test: Scroll a Sidebar Row Into View Before Dragging It
A row under the fold has no pixel the mouse can press, so the drag selected text instead. Whether a run hit it depended on which earlier specs shared its shard and left chats in the Running and Finished sections.
* test: Give the Client Specs an Inert IntersectionObserver
With the rail's guard gone, a client spec that renders the message list reaches the observer jsdom lacks. The shared setup provides an inert one, as the package's jest setup does, and the child-thread spec's partial client mock gains the rem scale hook the rail reads.
* chore: Retest Against Current Dev
* test: Give the Test Messages Host the Row Hook Members
The messages host gained the assistant, added-conversation, streamed-attachment and feedback hooks when the row hooks moved into the package, so the shared test host supplies them too.
* refactor: Move Leaf Content Parts Into the Chat Package
Container, ToolAuthWarning, ToolPreparation, the failed-reveal pill, the fold
rail, the background task guidance keys, MemoryInfo, PendingSkillCall,
ResumeAuthorHeader, DialogImage and ToolCallLimitNotice move from
client/src/components/Chat/Messages/Content to packages/chat/src/components/parts
and export from @librechat/chat/components. Their specs move with them.
Client importers and mocks point at the package entry. Design-lint
suppressions follow the moved files.
* fix: Ship the Tool Row Type Scale With the Component Library
The progress-text rules move from the SPA stylesheet to packages/client/src/theme/parts.css, which ThemeProvider loads into @librechat/client/style.css, so the package's PendingSkillCall row keeps its type size without the app's CSS. The two class names join the no-unknown-classes allow list, and PendingSkillCall needs no suppression.
* test: Check the Tool Row Label Keeps the Chat Type Scale
* test: Find the Tool Row Label Around Its Toggle
* test: Capture the Staged Skill Row in Its Loading State
* fix: End the Tool Row Type Chain in a Length for Standalone Consumers
--font-size-base and --markdown-font-size are declared only in the app's
stylesheet, so the .progress-text-wrapper font-size and line-height were invalid
for a consumer that loads the published theme alone. The chain now ends in
var(--font-size-base, 1rem), and the consumer spec reads the published
stylesheet for it.
* test: Cover the Memory Limit Alert in Both Themes and Modes
* 💬 feat: Show Ask-User Questions Inline in the Chat Instead of Over the Composer
A live ask_user_question pause now starts in its chat card, in thread order and at the thread's width, instead of a popover over the composer that covered most of the screen on phones. The card's chevron still moves a question into the composer popover, and the popover's chevron moves it back.
The shared atom flips from the questions moved to the chat (collapsedAskActionsAtom) to the questions moved to the composer (expandedAskActionsAtom), so the card is the default surface.
* 🔁 fix: Restore Saved Ask Answers in the Inline Card and Focus a Batch Only on Screen
A pending single question's answer is saved under its own draft key, which autosave restores only into the composer. With the chat card as the default surface, a reload showed an empty answer there; the card now reads that saved draft when no in-memory answer exists.
A batch arriving below a reader who has scrolled up took focus on a control out of view. Arrival focus now waits for the step to be on screen (re-measured against the viewport and scroll containers on each IntersectionObserver notification), and still only takes focus when focus is idle. The visibility measurement moves from Thinking.tsx to utils/viewport.ts so both share it.
* 🧷 fix: Keep a Restored Ask Answer When Draft Saving Is Turned Off
The answer restored from a pending question's saved draft lived only in the render-time fallback, so turning Save drafts off while the card was open recomputed it to empty and cleared the visible answer. It is now copied into the in-memory answers once restored, so later preference changes leave it in place, as they do for the composer.
* 🎯 fix: Clear Answered Ask Drafts and Focus the Popover on Handoff
A pending single question's answer is saved under its own draft key. Answered from the composer, autosave cleared it along with the composer; answered from the chat card, which is now the default, nothing cleared it, so every answered question left its text in localStorage. The key is now cleared as soon as the answer is accepted (even after navigating away) and when the question expires, so a saved answer lives exactly as long as its question.
Moving a question from the card into the composer left focus on the card's now-removed button. A single question now focuses the draft, its answer box, and a batch focuses its active step through a new focusOnHandoff prop that is not limited to the first arrival.
* ⌨️ fix: Focus a Single Question on Arrival and Always Focus a Batch Handoff
With the popover gone as the default, a single question arrived with no focus cue: keys typed next in the composer went out as an ordinary mid-run message instead of answering it. The single card now takes arrival focus like a batch does, on its first option or else its answer field, once per question, only once it is on screen and only when focus is idle (nowhere, or the empty composer that sent the turn). Both cards share a new useArrivalFocus hook for the on-screen wait.
A batch moved into the composer popover now takes focus unconditionally: the handoff is the user's own action, and Safari leaves focus on the previous owner of a clicked button, which can be the hidden chat card.
The deferred-tools HITL e2e scenario read its terminal line once as soon as it appeared, while the slow echo was still streaming into it; it now waits for the full text.
* 💶 fix: Price Mistral Large 4
Mistral Large 4 and its alias `mistral-large-4-0` fell back to the generic
`mistral-large` key at the Large 3 rate. Added at its published sale price,
with the list rate noted in a comment since no end date is published.
Related to #17025
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* 💶 fix: Use Mistral Large 4 List Price
Mistral has published no end date for the Large 4 sale, so bill at the list
rate ($1.36 / $4.18 per MTok). Deployments that want the sale rate meanwhile
can set it with `tokenConfig`.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* refactor: Move the Message Row Hooks Into @librechat/chat
* test: Point the Live Attachment Scenario at the Moved useAttachments Spec
The scenario ran the client's useAttachments spec by path, which moved into packages/chat with the hook. It now runs the spec from that workspace.
Seven settings are read only from librechat.yaml as loaded, from the
YAML-only base config, or once at startup, yet the admin config API
stored overrides for them as if they applied. List them in
DEPLOYMENT_ONLY_CONFIG_PATHS, so writes skip them (deployment_only_path),
the merge keeps the librechat.yaml value, and GET /meta reports them:
- clientLimits (operator): /api/config reads appConfig.config.clientLimits
- telemetry.rum (operator): /api/config and the RUM proxy read the raw
telemetry block, the proxy through a base-only req.config
- conversationList (operator): loadConversationListLimits reads the
base-only config
- fileConfig.skills.deletionCleanupConcurrency (operator): the skill
deletion service loads the base-only config
- endpoints.agents.managementApi (operator): the agent management M2M
auth reads the base-only config
- passwordHashing (startup): configureHashPool runs once in the startup
checks
- interface.colorModeFromUrl (startup): injected into the HTML shell at
boot
GET /api/files bounds an explicit limit with req.config.fileListLimit,
but AppService never copied fileListLimit into the app config, so the
librechat.yaml value never applied. AppService now copies it.
* refactor: Compose Message Toolbar Styles From Shared Button and Label Variants
* test: Cover an Open Fork Menu Holding the Message Toolbar Visible
* refactor: Compose Composer File Styles From Shared Primitives
* refactor: Compose Summary, Collapsible Text and Subagent Activity Styles From Shared Button Presets
* fix: Draw the New Button Variants From Theme Radius and Height Roles
* test: Find the Held-Open Scenario's Replies Inside the Message List
* fix: Restore the Feedback Note and Fork Checkbox Looks Through Primitive Variants
* refactor: Compose the Message Nav Chevrons With the Disabled Ink Recipe
* fix: Keep the Pre-Push Hook's Git Environment Away From Its Checks
Git exports GIT_DIR to hooks, absolute in a linked worktree, and the hook passed
it to the static checks. scripts/imports.test.mts builds scratch repositories
with git init, add and commit, so under a push those ran against the pushing
worktree: two fixture commits on the branch, its index replaced, and core.bare
set in the shared config.
The hook now unsets everything git rev-parse --local-env-vars lists before any
child runs. The imports suite clears GIT_* for itself as well, because the
pre-commit hook reaches it with STATIC_CHECKS_FULL=1.
* test: Cover the Hook's Git Environment Scrub in the Pre-Push Scenarios