* fix: Drop the Agent Icon From the Greeting Welcome Heading
* docs: Describe the Greeting Heading Without Its Icon in the Example Config
* test: Cover the Greeting Heading Without the Agent Icon in E2E Scenarios
A panel opening beside the conversation narrows the thread, every row wraps
onto more lines, and the end moves down past a reader who was on it: they are
left some way above the newest message, with the scroll-to-bottom control
offering to take them back. The session rail, the side panel and a resized
window all do it.
The thread followed its end only while a reply streamed. It now also follows
when the width it is laid out in changes and the reader was on the end before
the change. That is read from the position recorded while the layout was last
at rest, because the scroll event the browser sends for a re-wrap arrives
before the resize observer and already measures the thread after it. A reader
further up is left to scroll anchoring.
* 🛤️ feat: Session Rail for Subagents and Background Tasks
A column beside the conversation, opened from the chat header, that lists what
the conversation has running: its subagents, then its background tools. It
replaces the header popover, whose control only appeared once there was
something to list. The control is now always offered, and the rail keeps its
own column past the side panel, so a subagent opened from it stays in view of
the list. A running subagent's row says what the child is on now, read from
the thread the page already follows for the card.
interface.sessionRail (default true) turns it off and restores the popover.
* 🪤 fix: Hold Focus in the Session Rail's Small-Screen Sheet
The sheet covers the conversation, so it now traps Tab and answers Escape
through the shared focus trap the other sheets use, and says it is modal.
Focus still starts on the close button rather than on Stop all.
* 🪶 perf: Render Nothing but the Rail When the Session Rail Toggles
Opening or closing the rail changes the chat column's width once. The composer
bar kept its row's measured width in state, so it and everything under it
rendered for every frame of the composer's width change: 6 times on open and
18 on close, and the same on a sidebar toggle. It now reads only whether its
chips fit, through useElementSizeSelect, and renders when that answer changes.
The scan that titles background tool rows from the loaded messages, which runs
on each update of a streaming thread while the rail is open, now passes over
every tool call no task names before building its keys.
Adds rail.perf.spec.ts beside the sidebar's benchmark.
* 🪶 perf: Keep an Open Session Rail Still While the Thread Streams
Measured by replaying a recorded reply into long agent chats with the rail
closed and then open and listing running work.
A once-a-second clock held by the header control rebuilt every row object, so
every row rendered each second while anything ran. The clock now belongs to
the duration text: one shared timer, read only by the running rows' elapsed
times, and a row renders when what it shows changes.
A running row's title no longer sweeps. Each sweep is three compositor layers,
and every frame of the streaming thread paid for them in style, layerize and
commit: six running rows took the page from 9 layers to 33. The row keeps its
pulsing dot and its counting duration.
The rail's layout slot is memoized: its parent renders for every stream frame.
The replay benchmark gains FADE_PERF_RAIL, and rail.perf.spec.ts a test that
grows the last reply beside the rail and prints the layer count.
The paste preview e2e waited for a history response across a reload and read its body afterwards. A response from the outgoing document could match, and its body is gone once the page navigates. The test now reads the persisted history through the API before it reloads.
* 📈 fix: Keep the Context Gauge Counting While a Reply Streams
* 📊 feat: Feed a Side Chat's Usage to Its Composer's Gauge
* 📉 fix: Drop a Failed Side Chat Reply's Counted Usage
* ✨ feat: Support Model Spec Handoff Targets
* fix: Preserve Effective Config and Transcript Identity for Preset Handoffs
* test: Provide Query Client for Search Transcript Handoff Fixture
* fix: Match the Subagent Icon Display Contract
* 🪟 feat: Open a Conversation Beside the Chat From Its Menu
A conversation's menu in the sidebar offers to open it as a side chat
beside the chat on screen. The item appears only where there is a chat
to sit beside and side chats are on, and not for the chat on screen or
an archived one. The conversation's full record is read first, since a
side chat builds its turns from it.
* 🪟 fix: Give a Side Chat the Panel Slot It Was Asked For, Beside the Chat It Was Asked Beside
A side chat opened while an artifact or a child's activity is showing
now takes their place, as each of them takes its. A record lookup that
finishes after the reader has moved to another chat, or to the very
conversation asked for, opens nothing.
* 🪟 fix: Let the Newest Side Chat Request Win, and Test the Real Menu
An older Open beside chat whose record arrives late no longer replaces
the reader's newer choice, or a side chat opened another way meanwhile.
The item's tests now drive the production menu, hooks and strings, and
replace only the request for the conversation's record.
* 🪟 fix: Withdraw a Pending Side Chat for a Newer Panel, and Open It Clear of the Drawer
A side chat still being fetched no longer arrives over an artifact or a
child's activity opened after it was asked for. On a small screen the
sidebar drawer leaves first, the way it does when a conversation is
selected, so the side chat is not opened behind it. Once its
conversation is in, focus moves to its composer.
* 🪟 fix: Ask Again Whether a Side Chat Is Still Wanted Once the Drawer Has Left
The drawer takes a few frames to leave, and the checks that a side chat
was still the reader's newest ask ran before that. The request now
stays theirs until the side chat is written, and is asked about again
at that point.
* 🧪 test: Answer the Real Config Query in the Presentation's Side Chat Tests
* 🪟 feat: Continue a Subagent's Thread as a Chat Beside the Conversation
* 🪟 fix: Take a Side Chat's Streamed Attachments Where Main Chat's Go
What a tool hands back while a side chat's generation runs (search
sources, a generated file) reached no handler, so it was missing from
the rows and from the app's file, memory and preview caches. The side
chat's stream now uses the app's attachment handler.
* 📜 fix: Read a Child Thread's Messages a Page at a Time
The child messages route read a thread's whole stored history, and a
card previewing a running child triggers that read without anyone
asking. Every read is now one page (50 rows or 2 MiB, newest first)
with a cursor for the page before it, the followed pane keeps the pages
it has read and offers the earlier ones, and a client or server that
predates paging still gets a list.
* 📜 fix: Start a New Follower From Its Own Newest Page
A follower recreated over rows another one left in the cache kept them
without knowing where they began, so the earlier-messages control was
gone. It now places its first page itself and takes that page's
cursor.
* 🪟 feat: Show a Running Subagent's Current Row on Its Card
* 🪟 fix: Draw the Card's Row Live and Skip Label Reservations That Draw Nothing
* 🪟 fix: Show a Card's Row Only While Its Thread Is Followed, and Throttle a Detached Row Too
* 🪟 chore: Sort the Card Spec's Imports
* 🪟 fix: Draw the Card's Row as a Picture That Registers, Claims and Reveals Nothing
* 🪟 test: Give the Artifact Preview Test the Props Its Type Requires
* 🪟 refactor: Keep the Shared Follower Registry in Provider-Scoped Jotai Atoms
* 👀 fix: Look Again for a Run the Caller Knows Of Before Taking It to Have No Stream
* 🧵 feat: Open a Background Subagent's Thread as a Conversation in the Panel
* 🧵 test: Keep the Subagents Host Spec and Add the Follow Cases Beside It
* 🧵 fix: Give the Followed Thread Its Panel Gutter and Assert It in the Browser Specs
* 🧵 test: Do Not Wait on a History Fold That Closed Before It Was Clicked
* 🧵 test: Draw a Steer the Child Took Before the Panel Opened Where It Was Taken
* 🧵 fix: Fall Back to the Durable View Only on a Confirmed Missing Stream or History
* ↩️ feat: Show Guidance a Followed Subagent Has Not Taken Yet, With Its Withdraw
* feat: Add Gemini Hydrogen Model Support
* fix: Restore Google History For Reachable Agents
* fix: Preserve Mixed Google Signature History
* refactor: Inject Google billing configuration at application boundary
* fix: Preserve Call Signatures From Unsupported Google Output
* chore: Use Released Agents SDK 4.2.5
---------
Co-authored-by: Lia <lia@librechat.ai>
* 🪟 perf: Skip Thread Rows Far From the Viewport
Opening or closing the sidebar beside a long thread laid out and painted
every row of it on every frame of the 300 ms slide, because the slide
changes the chat pane's width. In a 246-row thread that was 17 ms of main
thread per frame, 55 ms on a CPU four times slower, where the slide ran at
about a dozen frames a second with tasks over 100 ms.
A row more than a screen from the thread's viewport is now skipped by the
browser (`content-visibility: auto`), so a change that touches the whole
thread costs only the rows near the reader. Rows within a screen are left
exactly as they were: none of them gains the clipping and containment that
skipping implies. A skipped row keeps the size it was last laid out at, so
the scrollbar, the navigation rail and the mount anchor see the same
thread, and it stays reachable by find-in-page, focus and anchors.
The skip sits on the row element the rail and the mount anchor measure:
reading the box of an element inside a skipped row makes the browser lay
that row out again. Screenshot export lays every row out before it clones
the thread, since a clone has no remembered size.
The navigation rail measured every row on each frame of a width change.
It now waits for the width to hold still and measures once; a height
change, which is what a streaming reply is, is still followed frame by
frame. Alone that saved nothing, because its reads forced a layout the
frame needed anyway; with rows skipped it is a fifth of what remains.
* 🧮 fix: Keep Rows Laid Out Until Every Overlapping Capture Is Done
`revealOffscreenRows` handed each caller the thread's `watch` function as
its resume. Two captures that overlap (a second screenshot export started
before the first finished) each got one: the first to finish resumed
skipping while the second was still cloning the thread, and the second
then created another observer without disconnecting the first, which no
cleanup released. A resume called after the thread had unmounted created
an observer for a thread that was gone.
Each thread now counts its outstanding reveals. Skipping resumes when the
last one is done, a resume counts once however often it is called, and
does nothing once the thread has unmounted.
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.
Move grouped tool rows and compact reasoning into the props-only ToolGroupBody component in @librechat/chat, retaining app-owned expansion, approval lifetime and attachment behavior.
Select mock model options by exact descendant text so mobile Pin controls do not change the match.
Related to berry-13/LibreChat#463.
The keyboard-focus scenario rejected a transparent outline with
`/,\s*0\)$/`, which also matches opaque black, `rgb(0, 0, 0)`: the
default light theme's focus outline. It passed only because the card
eases its colors, so the outline read straight after Tab was still on its
way from the text color (`rgb(33, 33, 33)`) to black. On a slower runner
the transition had finished and the test failed; with a 600 ms pause
before the read it fails every time.
The scenario now waits for the outline to settle on the theme's
`focus-outline` color and checks transparency with a pattern that needs a
four-part `rgba()`. The focus-ring scenario picked its opaque shadow layer
with the same loose pattern and would have skipped a black ring; both use
one helper now.
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