Move the existing streaming fade engine into @librechat/chat and its waiting-dot, cursor and fade styles into the shared client stylesheet.
Use the effective host smoothing policy consistently in Markdown, including nested subagent content, while preserving optional renderer callbacks and raw fallback behavior.
Add theme-selected welcome backdrops and focus the composer when the welcome greeting settles. Preserve popup and touch-device focus behavior, with acceptance coverage for themes, focus, and composer layout.
- refactor: Move Reasoning Parts into the Chat Package
- fix: Lay Out the Web Search Details Button as a Flex Item
- test: Cover Part Disclosures and the Styles They Ship With
- test: Cover a Consumer Opening a Thought With the Package Styles
- fix: Size the Web Search Row Button by Its Content
- test: Hold the Part Motion and Peek Fade to Their Old Inline Styles
- refactor: Move Ask User Question Cards Into the Chat Package
- fix: Preserve Ask Card Styling Without Suppression Growth
- fix: Provide Live Ask Pauses As Scoped Context Data
- test: Cover the Settled Ask Record Collapse Cascade
- fix: Give the Ask Call Spec Host the Tool Call Chrome
* 🫁 fix: Ease Context Usage Popover Size Transitions
Expanding snapped the card to its wide width in one frame; collapsing snapped it narrow first, reflowed the details into one column and made the card taller than it had been before rolling up.
- The popover owns the card width and eases it at the pace of the roll it travels with.
- The details hold the wide card's width through both rolls, so the card uncovers one settled layout.
- The per-tool breakdown and the usage sections roll instead of jumping.
- A press inside the card pins it, so a control that shrinks it from under the pointer no longer closes it.
* 🫁 fix: Restart the Details Width Hold on Every Opening
A collapse reversed midway kept the details mounted with their mount-time hold already spent, so they reflowed to the narrowing card, flashed one column and gave the roll a taller height to snap back from. The hold is now keyed to the open state and restarts with each opening.
A card that opens already expanded resizes nothing, so it no longer holds: with a classic scrollbar on a viewport-capped card the held width could sit across the two-column threshold from the settled one.
---------
Co-authored-by: Lia <lia@librechat.ai>
- refactor: Move the Tool Call Card Into the Chat Package
- test: Render Tool Calls Through the App Host
- fix: Keep the Tool Call OAuth Bind Stable Across Catalog Updates
* 🎞️ perf: Run the In-Flight Label Sweep on the Compositor
The sweep on a running tool call, streaming reasoning and the elapsed timer
animated `background-position` under `background-clip: text`, which no
browser can hand to the compositor. Every frame of it ran style, paint and
commit on the main thread, and each paint walked the transcript around the
label, so the cost of a frame grew with the conversation and the sweep
stuttered whenever the main thread was busy.
`Shimmer` in `@librechat/client` draws the same sweep from two transforms
that cancel: a masked band slides across the label while a second copy of the
text inside it slides back, so the glyphs hold still and only the gap in the
mask moves. The copy is generated content, so the label is still one text
node. Every in-flight label renders through it.
`e2e/benchmarks-fade` measures a frame and each kind of stream event inside
an exported conversation, from a Chromium trace of the built client.
* 🧪 test: Let the Frame Benchmark Open a Chat in a Chosen Theme
* 🧵 perf: Keep the Composer, Nav Rail and Row Toolbars Out of Every Stream Event
A streamed delta rewrites one row, but each one also re-rendered the composer
form (and re-measured its textarea), the message nav rail (re-translating a
label per message), the sidebar's chat provider and the pending-steers row,
because each subscribed to the whole streaming message or the whole messages
array to read something a delta never changes.
- The chat contract and steering read a projection of the branch tail (where it
sits, whether the run is paused) and fetch the message itself when a turn is
built, through `useBranchTailGetter`. `ChatTurnsParams` carries
`getLatestMessage` in place of `latestMessage`.
- The compact action and pending steers select what they use of the tail.
- The URL-prompt hook observes the history only while a submission waits on it.
- The nav rail's ribs are memoized apart from the rail.
- A row's toolbar keeps one element per glyph and stable handlers, so a send
and its completion no longer re-render every button of every row.
`e2e/benchmarks-fade` gains a render-reason probe (`FADE_PERF_WHY`), a whole-run
profile, and windows for the send and its confirming frame.
* 🫥 perf: Conceal Rerun During a Run Instead of Unmounting It on Every Row
A run starting or ending withholds, then restores, the rerun control on every
row of the thread at once. Unmounting and remounting a button on each row made
the browser re-style the whole transcript both times: the stylesheet holds
`:has(:disabled)` rules and a message row is a `:has()` anchor, so a button
entering, leaving or flipping `disabled` inside a row invalidates that row's
entire subtree. In a 250-message thread that was 80 to 100 ms inside the send
keypress and again inside the final frame.
The control now stays mounted for as long as the row has a rerun to offer and
is concealed by visibility while a run is in flight: no focus, no pointer, no
place in the accessibility tree, and no layout where the toolbar starts at the
row's edge. Below `lg`, where the toolbar is centered, it leaves the flow as
before. It is deliberately not also `disabled`. The reply being written still
mounts no controls at all.
* 🎯 perf: Write :has() Rules So a Change in a Row Does Not Re-style the Row
Two selector shapes in the stylesheet left the browser unable to tell which
elements a `:has()` rule could reach, so it re-styled the whole subtree of
every `:has()` anchor above any change:
- Tailwind's `group-has-[…]`, which compiles to
`.x:is(:where(.group):has(…) *)`. Message rows and their toolbars are
`group`s, so a button mounting or unmounting in a row re-styled the row.
- `theme-disabled-within:[&_*]:…`, which compiles to `…:has(:disabled) *`.
With it in the sheet, a `disabled` flip did the same.
Either one alone was enough: flipping `disabled` on one button per row of a
250-message thread took 100 to 110 ms, and mounting one took 88 ms. A run
starting or ending did one of those on every row.
The row-hover reveal, the header label crossfade and the toolbar's
hover-active hold now use `grouped-*` custom variants that emit
`:where(.group):has(…) .x`: the same elements at the same specificity, with a
subject the browser can read. A wrapper's parts take the disabled fill from
classes the component adds while it is disabled, through `theme-disabled-fill`,
instead of from `:has(:disabled) *`. The same two changes now cost 25 to 42 ms
and 27 ms.
`has-selectors.spec.ts` reads the stylesheet the app ships and fails on either
shape; `restyle.perf.spec.ts` measures the cost.
* 📱 fix: Keep a Concealed Rerun Hidden on Narrow Screens
The narrow-screen stylesheet forces every toolbar button visible from outside
any cascade layer, so it outranked the utilities that conceal a rerun while a
run is in flight: below 1024px the button stayed on screen and in the tab
order, inert. A concealed button now carries `data-concealed`, and that rule
leaves it alone.
Covered at a narrow and a wide viewport by what the reader gets: the settled
reply's rerun is hidden and cannot take focus during a run, and is back after.
* 🧮 perf: Skip the Pause Scan in Pending Steers When None Are Pending
The pending-steers row follows the conversation's messages, so it renders for
every streamed delta, and it resolved the run's pause state before checking
whether it had anything to show. That check walks every part of every message.
It now runs only with a steer to display.
- refactor: Move the Composer Palette Into the Chat Package
- fix: Keep the Palette Usable Without a Windowed List or Catalog Host
- test: Cover Picking Palette Rows With the Mouse
- fix: Leave Palette Keys to IME Composition and Focus to the Field a Press Moved It To
- fix: Localize the Palette Without Its Data Host
- fix: Ship the Composer Popover Motion With the Client Package
- test: Check the Composer Motion Survives the App Cascade
- fix: Offer Palette Favorites Only Where the Host Stores Them
- fix: Name the Palette Favorite Shortcut Only Where It Works
- fix: Leave the Bookmark Shortcut Alone Where the Palette Stores No Favorites
- refactor: Move Attachment and Retrieval Rows Into the Chat Package
- refactor: Drop Dashes From the Moved Attachment Comments
- test: Cover the Moved Attachment and Retrieval Rows
- refactor: Keep the Shared Button on the Attachment Preview Download
- test: Pin the Fold and Settle Motion Against the App Stylesheet
- refactor: Render Pending Turn and Steers from the Package
- refactor: Keep Package Pending Rows Inert Without a Steer Host
- fix: Read the Host Thread Mode on Every Render
- fix: Point the Hosts Guard at the Messages Loader
- fix: Follow the Moved Pending Rows in the Guard and Lazy Chunk Specs
- fix: Ship Message Body Typography With the Shared Theme Styles
- fix: Keep the App Message Typography Cascade With the Shared Styles
* 🎞️ perf: Run the In-Flight Label Sweep on the Compositor
The sweep on a running tool call, streaming reasoning and the elapsed timer
animated `background-position` under `background-clip: text`, which no
browser can hand to the compositor. Every frame of it ran style, paint and
commit on the main thread, and each paint walked the transcript around the
label, so the cost of a frame grew with the conversation and the sweep
stuttered whenever the main thread was busy.
`Shimmer` in `@librechat/client` draws the same sweep from two transforms
that cancel: a masked band slides across the label while a second copy of the
text inside it slides back, so the glyphs hold still and only the gap in the
mask moves. The copy is generated content, so the label is still one text
node. Every in-flight label renders through it.
`e2e/benchmarks-fade` measures a frame and each kind of stream event inside
an exported conversation, from a Chromium trace of the built client.
* 🧪 test: Let the Frame Benchmark Open a Chat in a Chosen Theme
- refactor: Move the Code Workspace Menu Into the Chat Package
- refactor: Share the Composer Chip Classes From the Chat Package
- test: Provide the Shared Composer Class Helpers to the Workspace Menu Spec
* feat: Redesign the Slack Channels Setup and Management UI
* test: Cover the Channels UI and Keep the Channel Lifecycle Specs on the New Copy
* fix: Keep the Agent Id on a Channel Link Whose Agent Cannot Be Read
* fix: Name Channel States That Need Action and Keep Link Recovery in the App
* test: Follow the Channel Library in the Workspace Agent Setup Spec
The organization workspace setup spec still pressed the removed Add Slack
channel button, timed out, and left its agent behind for the retry. It now
opens the Channel Library, reaches row actions by hover, gives each attempt
a unique agent name, and carries scenario tags so verify runs it.
* style: Restyle the Fork Popover and Calm the Feedback Hover
* fix: Follow the Stored Fork Mode and Update the Specs for the New Fork Popover
* test: Find the Fork Options Link by Both of Its Names
* feat: Add Choice Cards, Raised Radio Tone and Section Add Button
* fix: Size the Section Add Button From a Theme Role and Cover the Shared Controls in E2E
* test: Cover the New Shared Controls Under a Reference Theme
* test: List the Shared Controls Theme Spec in the Guard Manifest
`TooltipAnchor` subscribed to its store's `anchorElement` and `open` to
resolve a physical `left`/`right` side against the anchor's direction.
`anchorElement` changes from null to the element as soon as the anchor
attaches, so every anchor rendered its provider tree a second time right
after mounting, and again on every open, even though the resolved side
only ever differs for a `left`/`right` side under RTL.
The anchor now selects the resolved side itself. Ariakit re-runs the
selector on every store change, so opening still re-resolves after a
language switch flips the direction without a remount, but the anchor
only re-renders when the answer changes. `resolveSide` also returns a
`top`/`bottom` side before reading the computed direction, since those
never mirror and the selector now runs on each store change.
Message rows mount hundreds of these anchors (copy, edit, fork,
regenerate, feedback). On the conversation-navigation benchmark's warm
switch this removes about 1,450 of 10,700 component renders.
* 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: Refresh Copied Client Bundle Files After Build
fs.cp keeps the source mtime on Windows, so dist/tokens.css and the other
copied theme files never looked newer than packages/client inputs written
later by a checkout, and the pre-commit freshness check failed after every
rebuild. Stamp the copied outputs in tsdown's build:done hook.
Related to #17731
* test: Cover copied client bundle freshness where cp keeps mtimes
* 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: 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: 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 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 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
* 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: Simplify Tool Activity Headers
* fix: Preserve Interactive Flattened Tool Results
* test: Update Fold Tree Scenarios for Hidden Markers
* fix: Restore Tool Activity Tree Markers
* fix: Smooth Streaming Tool Disclosures and Show Command Timers
* fix: Align Tool UI Imports With Shared Chat Components
* fix: Hide Durations on File Read and Authoring Cards
* fix: Phrase Tool Durations as Part of the Label
* style: Match Thoughts Panel Radius to Tool Panels
* fix: Keep the Bash Copy Button Clear of the Command
* style: Space Thoughts Rows Like Tool Rows
* style: Render Agent Handoff as a Tool Disclosure
* style: Even Padding on the File Search Relevance Badge
* feat: Show Loaded Skill Instructions With an Open Skill Action
* style: Align Memory Panel Typography With Tool Panels
* style: Show Full File Paths and Match the Diff to Code Panels
* style: Pin Tool Durations and Chevrons to the Row End
* style: Use an Icon Button to Open a Loaded Skill
* style: Always Show Disclosure Chevrons
* style: Compact, Evenly Inset Copy Buttons in Tool Panels
* fix: Draw No Fold Rail Around a Lone Tool Call
* fix: Put a Titled Command's Time on Its Command Line
* fix: Hide a Bare File Edit Summary
* style: Compact Copy Button on Thoughts Headers
* fix: Move Titled Web Search Details Into the Sources Panel Header
* fix: Show Titled Web Search Details Beside the Title Chevron
* fix: Import Tool Call Phase Types From the Chat Package
* test: Cover Tool Activity Header Scenarios
* fix: Read Smooth Streaming Through the Message Parts Host
* fix: Keep a Command's Measured Time When Its Title Takes Over
* fix: Show a Loaded Skill Only When Its Name Is Unambiguous
* fix: Keep Nested Group Rails and the Handoff Label Text
* fix: Keep Skill Execution Warnings Beside Its Instructions
* fix: Label Loaded Skill Instructions as the Current Version
* feat: Add the Composer Placement Transition Recipe
* refactor: Move the Composer Layout Into the Chat Package
* test: Expect No Refocus on a Coarse Pointer in the Composer Frame Scenario
* fix: Render No Context Rail for a Boolean Slot
* feat: Add a Composer Variant to TextareaAutosize
* refactor: Move the Composer Field and Action Slot Into the Chat Package
* test: Wait for the Collapse Transition in the Composer Field Scenario
* fix: Keep the Composer Touch Font Floor in the Shared Field Stylesheet
* test: Floor a Small Chat Font on the Composer Draft on Touch
* feat: Add a Hint Variant to Button
* refactor: Move the Ask Question Popover Into the Chat Package
* fix: Keep the Ask Hint's Hover Ink
* fix: Return Focus to the Draft When the Ask Chevron Moves the Question
* test: Exercise the Real Composer Overlay Hook in the Ask Popover Spec
* 🥐 chore: Standardize Bun-First Workspace Typechecks
* fix: Preserve Bun 1.4.3 Checker Compatibility
* chore: Pin Bun 1.4.4 for Local and CI Typechecks
---------
Co-authored-by: Lia <lia@librechat.ai>
* chore: Prepare the Chat Package for Message Components
Give packages/chat a lint-only Tailwind entry so the design rules resolve the
library's theme utilities, allow the app status selectors its components carry,
expose the active language from @librechat/client, and let the locale check
accept keys that resolve through plural forms.
* refactor: Move Message Row Leaves into @librechat/chat
Move the hover style helpers, SubRow, SiblingSwitch, the elapsed timer with its
duration labels, HeaderLabel and the system event header into
packages/chat/src/components/messages, export them from
@librechat/chat/components, and point the client at the package.
* test: Cover Message Row Leaves in the Mock Harness
* chore: Drop the Chat Lint Entry in Favor of components.json
* test: Run the Elapsed Spec Against the Package
* 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: 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.
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.
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.