* feat: Let Users Connect Their Own Account for Pull Request Lookups
* fix: Refuse Cross-Tenant Pull Request Callbacks and Surface Key Failures
* fix: Keep Pull Request Grants Through Outages and Remove Them on Disconnect
A token endpoint server error is an outage even with an OAuth error body, so
it no longer deletes the grant, and a refresh outage reaches the lookup as
unavailable instead of falling back to no token. Disconnect removes every
pr_oauth row of the user, whatever app or host is configured now. A grant that
never expires extends its retention when used, and the flow, request and
retention limits are configurable. The connection routes are built in
packages/api, mounted behind the pre-auth tenant middleware in both servers,
and answer failures with stable codes.
* fix: Keep the Pull Request OAuth App Out of Overrides
A role, group, user or tenant override can no longer change or remove pullRequests.oauth, so the connect capability and the callback see the operator's app.
* fix: Read a User's Pull Request Token Only With the Feature On
* fix: Report a Malformed Stored Pull Request Grant as a Failure
* fix: Remove a User's Stored Tokens When an Administrator Deletes the User
* fix: Answer No Pull Request for a Conversation Without a Lane When the User Token Fails
* fix: Share One Grant Read Between Concurrent Callers and Report an Expired Grant Disconnected
* fix: Remove a Pull Request Grant Only on a Definite Refusal and Past Its Retention
* fix: Version Pull Request Grants and Coordinate Refresh, Refusal and Retention Through Them
* fix: Invalidate a Refused User Token and Read It Only for a Lane That Needs It
* fix: Finish a Pull Request Connection Under the User's Effective Config Behind the Login Limiter
* fix: Type the Pull Request User Token for Isolated Declarations and Settle Retention Before Answering
* fix: Bind a Pull Request Connection Flow to the Generation a Disconnect Replaces
* fix: Start a Batch's User Token Read Only Within Its Deadline
* fix: Fence Pull Request Token Reads Against a Disconnect and Report a Failed Retention Cleanup
* fix: Fence Connection Status Like Token Reads and Keep a Newer Read Joinable
* fix: Report a Pull Request Grant Without Its App and Name the Sign-In That Made It
* fix: Read a User's Unexpired Pull Request Grants Newest First
* fix: Mark the Connection Callback as an OAuth Navigation and Report a Failed Extension
* fix: Name the Pull Request Sign-In Flow on Its Landing Page
* fix: Remove a Pull Request Grant of a Replaced App When It Is Read
* fix: Keep a Replaced App's Grant Untouched and Extend Retention From Each Day's Use
* fix: Accept a Pull Request Grant Only Under the User's Current Connection Generation
* fix: Renew the Connection Generation With a Grant Still in Use
* fix: Restore the Previous Connection When a Sign-In Cannot Store Its Grant
* fix: Decide a Sign-In by What Was Stored When a Write Does Not Answer
* fix: Roll Back a Sign-In's Generation Along With a Grant It Must Remove
* fix: Refresh an Access Token a Lookup Was Refused With Before Ending the Connection
* fix: Undo a Sign-In Only for a Confirmed Fence, Not a Failed Check
* fix: Read a User Token Again When the Connection Changes Under the Read
* fix: Apply the Current Retention Again When Another Replica Changed the Grant First
* test: Answer Each Concurrent Sign-In by Its Own Code
* fix: Skip Retention Rewrites for Grants That Expire Without a Refresh Token
* fix: Retry a Token Rejection That Loses to a Concurrent Grant Write
* fix: Skip User Token Reads for Lanes Without a Commit and Reread Status After a Reconnect
* ci: Type-Check Workspaces with bun check
Make every workspace tsconfig valid under TypeScript 7 semantics while
staying clean on the installed tsc 5.9: explicit types arrays (TS 7 no
longer auto-includes node_modules/@types), es2017 target for
data-provider, rootDir for api specs that import client contracts, and
noUncheckedSideEffectImports off for the CSS and matchMedia mock imports.
Fix the four client type errors newer DOM and Intl libs expose, and drop
the fetch.preconnect copy in useRum that only existed to satisfy the
leaked @types/bun globals.
Switch the client typecheck script and the CI type-check steps to
bun check (Bun 1.4.3); tsc --noEmit stays available as typecheck:tsc.
* chore: Fall Back to tsc When bun check Is Unavailable
Add scripts/typecheck.mts, which runs bun check when the installed Bun
provides it and the repository's tsc otherwise, so contributors without
Bun can still type-check. The client typecheck script and the
static-checks TypeScript gate both resolve their checker through it,
keeping local runs on the same checker CI uses whenever Bun is present.
* ci: Type-Check the Chat Package Through the Shared Checker
* ci: Run the Type Check When Only the Shared Checker Changes
A change to scripts/typecheck.mts alone started neither frontend review
nor the static-checks TypeScript gate, so a broken resolver could merge
unexercised. Add it to the frontend-review triggers and to every
typecheck project's paths.
The suppression-baseline scenarios copy static-checks.mts into synthetic
roots; copy its new typecheck.mts import alongside i18n.mts so the runner
loads there. Add scenarios for the checker choice and its fallback.
* feat: Share Pull Request Lookups Across Replicas Through Redis
* fix: Bound the Shared Pull Request Cache and Drop Commands at Their Deadline
* fix: Pass the Cache Config to the Pull Request Store and Check It Before a Local Cooldown
* fix: Keep Batch Lookups Apart by Cache and Sharing Policy
* fix: Share Only Found Pull Requests and Rate Limits, Never Moving Them Backwards
* feat: Look Up Bitbucket Cloud Pull Requests
* fix: Keep the Pull Request Host Out of Overrides and Per-Host Keys
A role, group, user or tenant override can no longer change or remove pullRequests.host, so feature gating and link recording see the operator's host. Links are recorded only from the configured host, and the batch share key and the rate limit cooldown are scoped by host.
* fix: Compare Pull Request Link Hosts Through the Host Resolver
* test: Add Pull Request Scenarios Against a Fake GitHub Enterprise Host
* fix: Keep the Pull Request Provider Out of Overrides and the Batch Share Key
A role, group, user or tenant override can no longer change pullRequests.provider, so feature gating and link recording agree with the lookup, and a batch lookup for one provider is never joined by a request for another.
* fix: Read GitLab History Apart From Open Merge Requests
Merged and closed merge requests are listed on their own, so open fork merge requests on the branch name cannot crowd them out. Rate limit cooldowns are scoped by provider, and a workspace repository with a dot segment is rejected.
* fix: Revalidate Bitbucket Pull Requests and Skip Ones Without a Source Commit
Read a full closed page so a newer closed fork cannot hide an older pull request from the repository, recheck the source branch and fork status on the detail, and treat a pull request without a source commit as unmatchable instead of failing the lookup.
* fix: Follow Bitbucket's Next Link When Listing Pull Requests
* fix: Record the Lane Pull Request Without an Aggregation Pipeline Update
* fix: Match an Empty Lane Repository as Unknown
* fix: List Locked GitLab Merge Requests With the Open Ones
* fix: Replace an Expiring Fake Git Host Certificate
The step appliers, frame normalizer and SSE transport move from client/src/hooks/SSE into packages/chat/src/core with their specs, and the client imports them from @librechat/chat. The ask-user-question predicates the content applier reads move with them, and the client's approval module re-exports them so its consumers are unchanged.
* feat: Give the Checkbox Theme Roles for Its Fill and Corner
The shared checkbox painted no fill when unchecked and drew the rounded-sm
corner every small control shares, so the ClickHouse theme could not reach
Click UI's checkbox.color.background.default fill or its 0.125rem
checkbox.radii.all corner.
A checkboxRadius appearance role sets the corner and follows radiusSm, the
corner it drew before, when a theme names that and not this. A
checkbox-fill color role paints an unchecked box only when the new
checkboxFillStyle role is fill; the default transparent style keeps every
default theme pixel-identical, and the fill follows surface-primary when a
theme omits it. Checkbox and CheckboxGlyph read both roles.
The ClickHouse theme sets Click UI's fill and corner, and both entries
leave the drift guard's not-expressible list with their probes pinned to
match.
* test: Spell Each Checkbox Scenario Tag Literally
* test: Pin the Theme Cache Digest Built From the New Resolver
* 🧯 feat: Recover Conversations Whose Attachments Keep Failing
Once a branch carries a problem attachment, every turn resends it and
fails the same way. A failed response whose branch carries files now
offers "Retry without files" (re-asks the failed turn with no files as a
new version) and, when earlier turns carry files, "Branch without files"
(a copy up to the last good answer with every upload and code output
left out, with the failed message restored to the composer). File-shaped
errors say so in the card.
The edit view shows a user message's files as removable chips; "Update &
rerun" sends only the kept files and Save is disabled after a removal.
Fork is offered on a failed turn and gains a "Leave out files" option,
backed by a new `excludeFiles` fork option that drops `files`,
`attachments` and the conversation's `files` from the copy.
Bedrock rejects a request whose documents share a name, and history
resends every earlier document, so repeated names are now numbered
before formatting.
* 🧯 fix: Cover Steered Files, Hand Off the Whole Failed Turn, Name Replayed Documents Once
- Excluding files from a fork also strips attachments steered into a
response (`content[].files` on steer parts), which replay like uploads,
and the decision lives in `forkFileScope` in packages/api.
- The recovery card counts steered attachments as files, and reads the
specific code inside a generic `error` envelope, so a rate limit is not
offered files as the fix.
- "Branch without files" hands the failed turn to the copy's composer the
way a message is put back for editing: text through the in-memory
handoff, quotes, manual skills and the reasoning override through their
compose-time atoms.
- Document names are deduplicated over the formatted payload after the
steer stamp, so replayed steer documents are numbered too.
- Fork stays withheld on a failed response, whose copy would carry the
error as an ordinary answer; the card's branch action copies up to the
turn before.
- Remove-file buttons are natively disabled while the editor is locked.
* 🧯 fix: Keep Search Sources, Scope Root Retries, Skip Legacy Rate Limits
- A fork without files keeps metadata-only attachments (search sources,
file search results) and drops only file-backed ones; the recovery card
likewise counts only file-backed attachments as files.
- A turn sent at the root takes none of the conversation's file refs: its
siblings' uploads (an edited first message, or one retried without its
files) no longer come back through the unanchored-continuation fallback.
- Rows that carry a legacy LangChain model, key or rate-limit code are not
offered files as the fix.
* 🧯 fix: Align File Exclusion With Replay's File Shapes, Skip Assistants, Verify the Copy
- Shared `messageCarriesFiles` (with `isFileContentPart`,
`hasContentPartFiles`, `isFileAttachment`) in data-provider names every
shape historical replay reads a file by: uploads, file-backed
attachments, attached `files` on any content part, and `image_file`,
`file` or direct `file_id` locators. The fork drops all of them and the
recovery card detects all of them.
- Assistants conversations get no recovery actions: their upstream thread
keeps every attachment, and those endpoints offer no fork either.
- "Branch without files" checks the returned copy; a server that ignored
`excludeFiles` gets an error toast instead of a false recovery.
* 🧯 fix: Type Replay's Provider-Native File Locators for the Part Predicates
* refactor: Define the code highlight cadence default once
The interface schema, the config defaults and the client's normalizer read DEFAULT_CODE_HIGHLIGHT_THROTTLE_MS and MAX_CODE_HIGHLIGHT_THROTTLE_MS from data-provider, and normalizeCodeHighlightThrottleMs moves beside them so its bounds cannot drift from the schema's. A spec pins the schema, config defaults, normalizer and librechat.example.yaml to the same default.
* test: Read the cadence from the signed-in config payload
* feat: Let a theme reshape the sign-in field and button
The sign-in floating-label field, the submit button and their shared corner read the new authFieldHeight, authButtonHeight and authControlRadius appearance roles, whose defaults reproduce the 44px field, 48px button and 16px corner. The corner follows radius2xl when a theme names only that. The ClickHouse theme draws them at Click UI's single field and button size with the button's square corner.
* fix: Size the sign-in button by its height role alone
A fixed height with vertical padding left a short theme height less room than the label. Specs now expect the role classes on the sign-in field.
* fix: Keep the reset label and password controls inside a themed field height
The reset request label rests in the middle of the field instead of 12px from its top, and the password field's reveal and copy buttons size from the sign-in field height, 4px off its edges and never under 24px. Both keep their stock positions and sizes.
* fix: Hold the password field controls inside the padding it reserves
The reveal and copy buttons stop growing at the stock 2.25rem, so a taller sign-in field keeps them clear of the typed value.
* feat: Let a theme reshape the second-factor and reset-success actions
The 2FA verify and reset-success continue buttons read authActionHeight and authActionRadius, which follow the sign-in button's height and corner when a theme names those and otherwise the Button height and radiusLg they drew, so the stock screens are unchanged and ClickHouse draws them at 32px with its 4px corner.
* test: Reach the second-factor screen through a pending sign-in
* fix: Rest the reset label inside a minimum-height field and keep the action corner on radiusLg
The reset request label rests from an inset that centers it 2px low as before but never past the field's bottom edge, and the other sign-in actions resolve their corner before the sign-in corner is derived from radius2xl, so a theme that names only radius2xl keeps radiusLg on them.
* feat: Route Every Prompt Category Icon Through a Per-Slot Role
* test: Retry Category Icon Reads While the Prompt List Settles
* fix: Carry the Renamed Category Icon Role to Its Slot 4 Name
* fix: Carry the Renamed Category Icon Role Through Every Color Reader
* fix: Keep Renamed Color Roles Out of the Unknown Token Warnings
* feat: Give Prompt Category Icons a Purpose Color Role
* fix: Keep Token Formatting and Skip Hover on Touch in the Category Icon Scenario
* test: Refresh the Theme Resolver Pin After Rebasing on the Avatar Ink Change
* feat: Filter OpenRouter Reasoning Efforts by the Selected Model
* fix: Address Review Findings on OpenRouter Per-Model Reasoning Efforts
* fix: Report Catalog Failures, Share Lookups and Honor Direct Endpoints for Reasoning Efforts
* fix: Move Capabilities Handler Into packages/api and Harden Catalog Lookups
* fix: Scope Reasoning Capabilities to One Endpoint and Gate Editors Until They Load
* fix: Skip Catalog Reads for Explicit Definitions and Keep Staged Efforts While Loading
* fix: Retry the Reasoning Capabilities Query on Focus and Reconnect After a Failure
* fix: Remember Failed Catalog Lookups, Reject Locked Overrides Early and Keep Restored Efforts
* fix: Hide Efforts Until the Catalog Is Known, Keep Unlisted Models Unknown and Accept Auto
* fix: Mark OpenRouter Endpoints by Their Resolved Host so the Client Fetches Capabilities
* fix: Share One OpenRouter Catalog Rule, Build the Catalog URL Safely and Make the Lifetime Configurable
* fix: Forward Static Catalog Headers, Resolve Relative Next Links and Align Client Freshness
* fix: Limit Capabilities to Exposed Models and Revalidate Against the Server Entry Expiry
* fix: Hide Efforts After a Failed Refresh, Reject Malformed Pagination and Skip User-Scoped Catalogs
* fix: Use Own-Property Lookups, Skip the Catalog for Auto and Revalidate From the Remaining Lifetime
* fix: Treat Request Metadata Headers as Shared, Store Catalogs as Own Entries and Hide Efforts During Refresh
* fix: Keep Configured Query Parameters Across Catalog Pages and Treat Expired Idle Data as Unknown
* fix: Expose Only Configured Variants, Skip Identity Headers on Fixed Lists and Keep Staged Efforts
* feat: Infer Reasoning Effort Support From Known Custom Endpoint Hosts
* fix: Gate Inferred Reasoning on Provider Support and dropParams
* fix: Infer Reasoning for the OpenRouter Params Endpoint Set by the Loader
* feat: Derive the Theme Cache Version and Close the Color Token Drift
* feat: Add a Button Padding Role for the Default Size
* test: Run the Boot Script Through the Version Injection
* fix: Retain Signed-Out Provenance and Tighten Token Declarations
* feat: Add 10, 11, 13 and 15px Steps to the Theme Type Scale
* test: Prove the Off-Scale Type Steps in the Mock Harness
* style: Sort cn Imports
* refactor: Name the 13 and 15px Steps 1xs and 1sm
* test: Probe the Type Step Roles Instead of Unused Utilities
* feat: Show the Conversation Pull Request in the Sidebar List
Add a batch lookup route and a sidebar row mark: the state icon with the CI dot, opening the same card beside the row on hover. The row keeps the conversation's own title.
* fix: Address Review Findings on the Sidebar Pull Request Batch and Row Mark
Cap the whole batch with a configurable deadline, make the row mark a keyboard-reachable button that opens the card on focus, refresh rows when the window regains focus through the shared batch, and show a retryable failure state instead of treating a failed first lookup as no pull request.
* fix: Send Sidebar Pull Request Batches One at a Time
Queue every batch request behind the one before it, so an oversized list or an overlapping flush cannot multiply the server's configured lookup concurrency, and bound how long one request may hold the queue so a request that never answers cannot stop the rest.
* fix: Keep the Batch Request Timeout Above the Server Deadline
Default the client's request timeout to just past the longest batchTimeoutSeconds a deployment may configure, so a queued request never starts while the previous request's server-side lookups are still running.
* fix: Keep Batch Lookups Inside the Concurrency Limit and Per-Entry Failures Per Entry
Share one lookup limiter across every batch request so lookups that outlive a request's deadline keep their slot, answer a missing token only for the conversations that needed it, and point the row at its pull request description only while that text is in the page.
* fix: Bound Batch Reads, Scope Concurrency Per Credential, and Gate the Sidebar on the Batch Version
Start the batch deadline when the request arrives and bound the config and lane reads, count lookup slots per credential, advertise a batch route version and ask only a server that has it, take no row space for an absent mark, show a failed refresh over a cached empty answer, keep a malformed response from stalling the request queue, and repair the lane recording tests that still used a mock removed on dev.
* fix: Move Capability Resolution Into the Package and Harden the Batch Route and Queue
Resolve the pull request startup capabilities in packages/api so the route stays wiring only, bound the config and lane reads by the configured deadline, merge identical lanes before taking limiter slots, fall back to the single route when a replica has no batch route, and dispose the batch queue when the signed-in user changes.
* fix: Abort the Batch Fallback With Its Request So the Queue Never Overlaps It
Give the batch fetcher the request's abort signal and pass it to every single-route call, abort a request that times out or is disposed, and stop the fallback workers from starting more calls once it has.
* fix: Forward the Abort Signal to the Batch POST
Pass the request's abort signal through the batch fetcher, the data-provider call and Axios, so a batch request that times out or is disposed is cancelled instead of continuing beside the next one, and settle a request promptly when it is aborted.
* fix: Close the Pull Request Lookup Follow-Ups and Cancel Abandoned Sidebar Rows
* feat: Show Lia on the Welcome Screen
Adds the opt-in Show Lia setting (off by default) and the interface.mascot deployment flag (allowed by default). Lia mounts only on the landing page, loads lazily after first paint, stands on the composer's top edge clear of the greeting, reacts to typing, files and theme changes, and speaks through localized bubbles. She is decorative and hidden from assistive technology.
* fix: Keep Lia's Long-Message Reaction Re-Armed and Pointer Reads Per Frame
Deleting a message back under 280 characters now re-arms the long-message reaction, pointer handling reads layout at most once per animation frame, and the ChatView specs stub Lia like their other children.
* test: Open Settings from the Phone Drawer in the Lia Scenarios
The opt-in scenario no longer resets the stored preference on reload, and both Settings scenarios open the account menu from the mobile drawer on phones.
* fix: Measure Lia's Caret Like the Composer and Label Her When Idle
The caret mirror copies direction, alignment, indentation, wrapping and box sizing, so right-to-left and wrapped text measure like the composer. Hovering Lia between activities now says she is hanging out instead of showing nothing.
* fix: Wave Off Assistants Sends and Keep Lia's Canvas and Bubble Off Welcome Content
* fix: Keep Lia's Speech Bubble Inside Her Stage
* fix: Wrap Long Translations in Lia's Speech Bubble
* fix: Keep Lia's Long-Message Reaction Until It Plays and Pin the Scenario Greeting
* fix: Make Only Lia's Body Clickable So She Fits Beside Long Greetings
* fix: Let Lia Stand Beside the Composer When the Greeting Fills Its Top
* feat: Let Users Drag Lia Around and Keep Her Near the Composer
* test: Cover Picking Lia Up and Setting Her Down on the Composer
* refactor: Keep Lia's Preference Inside Her Feature
* fix: Let Keyboard Users Pet Lia and Move Her With the Arrow Keys
* test: Shift Only the Wall Clock for Lia's Morning Greeting
* test: Measure Lia's Keyboard Walk Both Ways So the Greeting's Width Cannot Pin Her
* fix: Bring Lia Back When a New Chat Opens During Her Farewell
* fix: Start Lia's Reactions on Her Own Clock After a Pause Without Room
* fix: Load Lia Through Stale-Asset Recovery and Skip the Farewell Before She Appears
* feat: Mark the Lia Settings Toggle as Beta
* feat: Show the Conversation Pull Request in the Chat Header
A header chip shows the pull request a code conversation opened: the agent picture with a CI status dot, the pull request icon and a truncated title. It opens a card with the number, added and removed lines, a link to GitHub, and state and checks badges. The chip renders nothing while loading, when there is no pull request, or when the first lookup fails.
* feat: Place the Pull Request Chip Beside the Model Controls and Move It to the Overflow Menu on Small Screens
On desktop the chip sits with the left header controls and its card opens to the right as an Ariakit hovercard that slides in from the left, on hover or keyboard focus. Small screens offer the same card from the header overflow menu through a dialog, following the dialog-item contract.
* fix: Address Review Findings on Pull Request Polling, Badges and Tooltip Layering
Advertise pullRequestsEnabled in the startup config and skip the lookup without it, keep polling a finished pull request while its checks run, render the card badges with the shared Chip, and portal the GitHub tooltip into the card's own layer.
* fix: Address Second Round Review Findings on the Pull Request Dialog and Chip
Scope the mobile dialog to the conversation it opened for and expose dialog semantics on its menu entry, only use the chat agent's avatar for the routed conversation, and make the hover tests move the pointer the way a browser does so they pass under NODE_ENV=development as CI runs them.
* feat: Quiet Prompt Editor Boxes, Table Columns and Destructive Buttons for a Theme
* fix: Outrank the Cell Border Color With the Column Rule Share
* fix: Keep the First Table Cell's Outer Edge Under the Inset Share
* fix: Keep the Batched Edit Divider on the Light Border
* fix: Keep Web Search Source Row Separators on the Light Border
* fix: Quiet the Result Switcher Divider and Keep the RTL Table Edge
* fix: Resolve Table Edges by Cell Direction and Keep the Variables Card Opaque in Details
* fix: Draw Table Frame Edges in Logical Terms So Direction Needs No Selector
* fix: Keep Soft Destructive Hover and Pressed Tints Above 4.5:1
* feat: Record Lane Git State and Serve Conversation Pull Requests
A conversation now stores the branch, head and repository its code lane last reported, written only by the server after a finished bash command and excluded from ordinary reads, generic saves, unset fields and imports. GET /api/convos/:conversationId/pull-request finds the pull request for that branch through an injected GitHub source with a bounded cache, answers null for an absence, and maps failures to stable codes without upstream text. The feature is off unless endpoints.agents.pullRequests is enabled with a token reference.
* fix: Address Review Findings on Pull Request Lookup and Lane Writes
Scope the lookup cache, shared in-flight request and rate limit cooldown to the credential, so one tenant's token never serves another. Ask for open pull requests on their own before falling back to the newest closed one, read every page of check runs up to a bound and never report an incomplete rollup as passing, order lane writes per conversation so an older write cannot land last, and name both required token permissions in the example config.
* fix: Address Second Round Review Findings on Pull Request Lookup
Clear the stored lane when the conversation moves to another workspace or leaves attached execution, so the previous workspace's pull request is never served. Fence the lane write on the time it was reported, so an older report from another replica cannot replace a newer one. Honor GitHub's reset window up to an hour instead of ten minutes, and expose the request timeout, whole lookup timeout and check run page limit as endpoints.agents.pullRequests settings with the previous values as defaults.
* fix: Authorize Pull Request Repositories and Fence Lane Writes
Require an administrator allowlist of repositories before the server token is used, since a worker reports its own repository. Match a pull request to the commit the conversation last ran at, so a reused branch name does not return another pull request. Fence the lane write on the workspace the command ran in, so a write queued before a move cannot bring the old lane back, and record a subagent thread's lane on the visible root conversation. Key the lookup cache and shared request by the recorded commit and the lookup policy, and document the worker flag in the example config.
* fix: Order Lane Reports by a Database Sequence and Tighten Head Matching
Replace wall clock ordering of lane reports with a per conversation counter reserved in the database when the command settles, so replica clock skew cannot reject a newer report. Treat a pull request whose head is behind the recorded commit as no match, and expose the candidate and comparison bounds of the history search as settings. Read the app config and the owner scoped lane together, inject the HTTP transport from the route instead of falling back to a global, skip a report identical to the last one written, and name the Contents permission that commit comparison needs.
* fix: Queue Lane Reports by the Visible Conversation and Read Checks for the Current Head
Order lane report reservations by the conversation the write lands on, so two subagent threads of one conversation share a chain, and write every report instead of skipping a repeat, since another recorder may have changed the lane in between. Read a pull request's detail before its check runs and use the head it reports, so line counts, mergeability and checks describe one commit. Treat an expired temporary chat as gone when reserving, writing and reading the lane, and make the shared cache capacity a setting.
* fix: Fence Lane Reports by Attachment Epoch and Place Recorders Before Reporting
Strip dotted descendants of lane fields from saves and imports, partition the pull request cache per credential, resolve the lane write target when the tool is created, and fence reports with a codeAttachmentEpoch that advances only on an owner move or detach.
* fix: Fence Subagent Lane Reports by the Root Epoch and Cover Forks and Moved Heads
Read the visible root's attachment epoch for a subagent report, gate lane recording on pullRequests.enabled, make the credential partition bound a config field, revalidate the detail head against the recorded commit, and find fork pull requests through the recorded commit.
* fix: Keep the Credential Cache Bound Deployment Wide and Budget Head Revalidation
Apply the largest configured credential bound to the shared cache, count cache hits as use, spend the comparison budget on a moved head, and fix the data-provider config default test.
* fix: Cool Down Headerless Secondary Rate Limits
A 403 whose message names a secondary rate limit now starts the credential cooldown for at least a minute instead of being cached as a ten second failure.
Code workers can report the branch and head commit of the lane a command ran in. LibreChat now accepts an optional laneGit key on execute_command results, bounded to a 256 character branch without control characters and a 40 or 64 character lowercase hex head, and rejects anything else. The data-provider gains the pull request types, endpoint, query key and service method, and an endpoints.agents.pullRequests config block that is off by default and takes the token only as an environment variable reference.
* fix: Keep Reasoning Out of Every Read Aloud Path
Read aloud spoke the Thoughts section along with the answer. The hover
button flattened think parts into the string it handed to TTS, browser
autoplay and the hooks parsed content without skipping reasoning, and
server streaming spoke the stored text field, which an aborted turn
persists with its reasoning included.
Add getSpeechText to data-provider as the single source for spoken text:
text parts only for structured content, and the legacy :::thinking block
stripped from plain text, treating a still-open block as reasoning so
streamed speech only ever grows. Route the hover button, browser
autoplay and server streaming through it, and skip reasoning in the TTS
hooks' own content parsing.
* fix: Speak String Message Content Without Its Reasoning
Imported or client-built messages can carry their answer as string
content rather than parts; read it like plain text instead of falling
back to an empty text field.
* fix: Keep Answers Between Repeated Legacy Thinking Blocks
Strip every closed :::thinking block before treating an unterminated one
as reasoning, so a second closed block no longer swallows the answer
that follows it.
* fix: Skip Read Aloud and Autoplay When Only Reasoning Remains
A turn stopped mid-reasoning has no answer to speak once reasoning is
filtered. Gate autoplay on the same speech text it will play, so the
external engine never opens a stream that can only time out, and hide
the Read aloud action when there is nothing to read. Every speech path
reads a finalized message, so speak an unmatched :::thinking marker as
the answer text the UI shows instead of dropping the rest.
* refactor: Move Speech Chunk Polling Into packages/api
The decision of what text to stream as speech lived in the legacy CJS
service. Move the chunk processor to packages/api as
createSpeechChunkProcessor, taking the message cache and lookup from the
caller, and leave streamAudio.js wiring them in. Its tests move with it
onto an in-memory cache instead of module mocks.
* fix: Speak Exactly the Answer the Message View Shows
Share the legacy :::thinking parser between the message view and speech,
so Read Aloud strips the same block the view collapses instead of a
separate pattern drifting from it. Trim structured speech text so a
whitespace-only answer is not speakable, and key autoplay's audio cache
by the spoken text, as manual playback already is, so audio cached with
reasoning before this change is never replayed.
* fix: Fall Back to Text When String Content Is Empty
* feat: Let a Theme Quiet Decorative Borders
* test: Cover the Chrome and Inset Border Roles in the Mock Harness
* fix: Draw the Selected Category Tab Edge at the Chrome Share
* fix: Route Chips, Subtle Icon Buttons and Hover Rings Through the Chrome Share
* fix: Draw the Remaining Inner Card Dividers at the Inset Share
* feat: Add a Focus Role for Rows Inside Content
* test: Cover the Subtle Focus Role in the Mock Harness
* test: Probe the Subtle Focus Role Through Its Theme Variable
* test: Focus the Probe to Read the Subtle Focus Utility
* test: Read the Subtle Focus Ring From Its Utility Property
* fix: Ring the Subagent Progress Disclosure in the Subtle Focus Role
* feat: Layered Surface Roles for the ClickHouse Theme
Adds purpose-named roles for the chat canvas, user message, cards, sidebar rows, settings tabs, menu panels, composer and search pill. Each follows the surface it painted before, so the default theme is unchanged; ClickHouse steps them apart with Click UI tokens.
* fix: Align Sticky Phase Headers, Boot Routes, and Row Fades With the Layer Roles
* fix: Cover Trailing Slash and Bare Dashboard Paths in the Boot Canvas Route
* fix: Match Boot Canvas Routes Case-Insensitively
* test: Expect the User Message Role on Other-Author Turns
* test: Expect the User Message Role on the Subagent Briefing
* feat: Tooltip, error alert and artifact preview theme roles
* test: Cover the Tooltip Theme Roles in the Mock Harness
* fix: Lighten the Dark Document Tile and Leave the Preview Color Scheme Alone
* fix: Let the Artifact Preview Frame Follow the System Scheme and Ink Autofill in the Field Text
* 🧾 perf: Load Tool-Call Previews and Fetch Full Parts on Demand
Long agent conversations shipped every tool output, argument string and
subagent transcript on load, though the cards render collapsed: 12-18 MB
of message JSON per chat, enough to crash iPhone Safari tabs.
A client that adds ?toolPreviews=1 to the conversation load now receives
bounded previews of settled tool calls (start and end of long outputs,
JSON arguments and outputs kept valid with only their longest strings
shortened, exit-status trailers kept whole, subagent transcripts omitted)
with explicit markers and full lengths. Opening a card or a subagent
panel fetches the stored part from a new owner-scoped endpoint,
GET /api/messages/:conversationId/:messageId/parts/:partIndex, cached
under its own React Query key. Clients that do not ask, exports and share
links keep the full payload; bounds are configurable under
toolCallPreviews in librechat.yaml, and a client-authored message that
carries previews is refused rather than saved.
* 🧾 fix: Validate Part Reads in Parallel and Preview Fork Responses
The full-part read now starts beside conversation-access validation
instead of after it, and keeps the active-job fallback the conversation
read has, so a conversation still live before its first save can expand
its previews. Fork, duplicate and shared-link fork responses honor the
preview parameter, so they no longer seed the conversation cache with
the full history. Background-task results whose structure cannot fit a
valid JSON preview go whole, image cards keep their prompts, and the
subagent panel offers a retry when its stored part fails to load.
* 🧾 fix: Key Hydrated Parts by Preview Revision and Call Identity
A fetched part is now cached under the preview's revision and replaces
only the fields the server shortened, so a call whose stored output
changes later (a harvested background result) is fetched again rather
than rolled back. Part lookups carry the run-step and agent identity and
refuse an ambiguous fallback, since provider tool-call ids can repeat
within one response. A subagent that finished without final text has
its transcript omitted like any other settled call, and JSON nested past
a fixed depth falls back to a text preview; a call whose preview fails
is sent whole instead of failing the conversation load.
* 🧾 fix: Release Hydrated Parts With Their History and Bound JSON Work
Full tool-call parts fetched for a conversation are removed when its
message history is released or cleared, so they cannot outlive it under
their own key. The structure-preserving JSON preview now bails out before
cloning when the value has more nodes or strings than could ever fit,
keeps a __proto__ key as ordinary data, and the part endpoint accepts any
safe-integer index instead of an arbitrary ceiling.
* 🧾 fix: Count Property Names Before Cloning a JSON Preview
Property names are never shortened, so the pre-check now adds their
length to its budget and falls back to the text preview before any
cloning when they alone could not fit.
* 🧾 fix: Preview Artifact and Branch Responses and Rehydrate Subagent Prompts
Artifact edits and parallel-response branches merge the message the
server returns into the conversation cache, so both requests now ask
for previews and their routes honor it. The subagent panel reads the
prompt from the stored arguments once they load, and the part endpoint
no longer caps identifier length, so any previewed call can be fetched.
* 🧾 fix: Preview Only Tool Calls That Can Be Fetched Back by Identity
A call without an id has nothing but its position to name it, and the
position can shift on the client, so it is left whole instead of being
previewed. The part endpoint now requires a tool-call id, so an indexed
lookup always confirms the call it returns.
* 🧾 fix: Fetch Parts by Exact Identity and Preview Only Unique Ones
The part endpoint now finds a call by its exact identity (provider id,
run-step id, agent) instead of trusting the client's index, and the
preview pass only shortens calls whose identity is unique in their
message, so every preview names exactly one stored part. Legacy
web-search failures that carry their error phrase mid-output go whole,
since the collapsed card reads that phrase anywhere.
* 🧾 fix: Bound the JSON Fit Walk Before Queueing and Normalize Empty Identities
The structure check now counts an array's or object's children against
the node budget before queueing them, so a very wide value is refused
without building a work list its size. An empty run-step or agent id is
treated as absent by the part lookup, matching how the preview pass and
the client already treat it.
* 🧾 fix: Key Fetched Parts to the Stored Version and Hydrate Search Details
Each preview now carries `previewRevision`, when its message last
changed, and the client keys fetched parts to that plus a fingerprint of
the whole preview, so any change to the stored call is fetched again.
The web-search details card asks for the stored call when it opens, so
its query is never left shortened.
* 🧾 fix: Cache Fetched Parts by Identity and Hold Copy Until Hydrated
The part query key drops the client-side index, which only rides along in the request; the server locates the call by message and exact identity, so a shifted index serves the cached copy instead of downloading it again. Copy controls inside a previewed part are disabled until the stored content arrives, so a slow or failed fetch cannot export shortened text.
* 🧾 fix: Shape Shared Forks With the Recipient's Bounds and Keep JSON Numbers Exact
A shared-link fork resolves the share owner's config for its content checks, but the forked conversation belongs to the requester, so its preview bounds now come from the requester's tenant and role (prepareResultToolCallPreviews). A structure-preserving JSON preview now requires every number in the text to survive a parse and re-serialization as the same value; an integer past 2^53, an out-of-range exponent or an over-precise decimal falls back to the text preview (or the whole output for parsed-output tools) instead of showing a changed value.
interface.runningChatRename now defaults to true, so a running chat or a placeholder-title chat can be renamed without a librechat.yaml override. Set it to false during a rolling upgrade from a version without title ownership.
* 💳 feat: Show Balance in the Context Gauge as Credits, Currency, or Percent
Move the balance out of the account menu into the composer's context gauge,
below the context window, and add `balance.display` (credits | currency |
percent, default credits) to choose how it reads. Currency reuses
`interface.currency` at 1,000,000 credits per USD; percent shows only the
share of the period's allotment spent.
Settings > Account > Billing renders the same summary from the same hook, so
both surfaces show identical figures, bar and refill timing in every mode.
* 🧭 fix: Normalize the Balance Display Mode and Reuse a Fresh Reading on Hover
Admin overrides reach the client without schema validation, so an unknown
`balance.display` now reads as credits instead of being typed as a mode it is
not. Hovering the gauge mounts the balance reader each time the card opens; a
30 s stale window stops every hover from refetching, while the explicit
refetch after each turn still bypasses it.
* 🩹 fix: Restore Gauge Popover Fixes and Tighten Balance States
The popover extraction was written from a pre-sync read of TokenUsage, so it
dropped dev's viewport caps and scrolling, the hideOnInteractOutside close fix,
the Tailwind v4 outline-hidden rename, and the card's max-w-full; restore them.
Refill copy now says when a refill becomes available rather than promising a
deposit, since one lands only once the interval has passed and a charge would
exhaust the balance. An empty balance reads as fully used even without an
allotment, percent mode without one says usage is unavailable instead of
leaving the figure blank, the balance-only ring takes the balance tone (amber
until empty) and is a meter only once it has a value.
* 🪙 fix: Read a Non-Positive Refill Amount as No Auto-Refill in Settings
The server never refills when the amount is not positive, and the balance
summary already says so; Settings showed its load error instead.
* 💸 fix: Show the Insufficient-Funds Error in the Balance Display Mode
The token-balance error still printed raw credit figures, so `percent` leaked
the numbers it hides and `currency` mixed units with the gauge. It now reads
the same display mode and formatter as the balance summary: credits as before,
money in currency mode, no figures in percent mode.
The auto-refill settings row also renders its own loading and failure states,
since settings search can show it without the balance row beside it.
* 🎚️ fix: Keep Fractional Credits and Drop the Moved Popover's Suppression
Credit amounts keep up to two decimals, so an insufficient-funds message no
longer reads 100.4 against 100.3 as 100 against 100; whole amounts still print
without decimals.
The design-rule backlog may not follow code into a new file, so the extracted
popover uses the standard `transition` utility instead of the arbitrary
`transition-[opacity,transform]` (which also misses Tailwind v4's separate
`translate` and `scale` properties) and its suppression is removed. The
composer geometry spec now reads the classes from `Popover.tsx`, where the
gauge button lives.
* 🧬 fix: Default Subagents to Their Parent's Code Machine and Workspace
A subagent resolved its code machine from its own saved fields only, so
when a chat routed the parent to an allowlisted machine the subagent fell
back to its own default and whatever workspace the conversation had
selected there, or failed the parent's whole turn when none existed.
Subagents now inherit the parent's resolved attached machine when it is
their own default or on their allowlist where per-chat choice applies,
the principal can use it, the sealed decision already selected it, and no
selection names the subagent as an explicit owner. Inheritance is derived
per request from the sealed decision and current agent configuration and
fed to every routing site; it is never persisted, so existing chats and
older clients get it without a decision change. The composer mirrors it.
A subagent whose machine has no usable workspace is advertised to the
parent as unavailable instead of failing the turn; a locked decision
stays fatal.
* fix: Inherit Across Every Spawning Path, Graph Members and Deferred Code Tools
A subagent now inherits only when every agent that can spawn it, at any
depth, runs on the same machine; spawn cycles keep their own routes.
Subagent graph members inherit like explicit subagents. The deferred
execute_code loader passes inheritance to its fallback resolver. Subagent
reads and VIEW checks move to a packages/api loader shared by inheritance,
lazy descriptors and graph members. The composer lets a draft's subagent
follow its parent's machine before a workspace is picked, and keeps an
inheriting subagent's former selection without asking for a move.
* fix: Prune Spawn Back-Edges, Gate the Composer on an Inheritance Capability
Spawning parents follow the run's path semantics, so a back-edge the
descriptor tree prunes no longer blocks inheritance, and agents that spawn
each other follow their single outside parent machine when it routes them
all there. Only admitted subagents count toward the walk's node limit.
Graph members re-read and re-check VIEW when they initialize. The composer
echoes an inheriting subagent's former selection without gating on that
machine, and mirrors inheritance only when the API advertises
codeWorkspaceInheritanceVersion; approval modes keep intersecting every
machine an agent could use.
* fix: Settle Each Mutually Spawning Group on Its Own
Independent spawn cycles no longer merge into one group, so a pair under
one parent follows that parent even when another pair follows a different
machine. Also types the data-provider spec for its ES5 target.
* fix: Bound the Inheritance Walk, Normalize Parallel Roots, Move Subagent Availability to TS
The walk reads in batches no larger than the remaining node budget, stops
once the limit is reached, and runs through the run's subagent load limiter.
Roots are keyed by saved agent ID, so a parallel root such as id____1 can
never receive an inheritance entry. Resolving a lazy subagent's code route,
reporting it unavailable, and guarding its descriptor now live in
packages/api (resolveSubagentCodeAvailability, guardUnavailableSubagent).
* fix: Keep Missing Subagent Loads Parallel Near the Node Limit
Batches never shrink below eight IDs, so missing or unviewable subagents
near the limit still load in parallel under the injected limiter, and at
most a handful of reads land past the limit.
* 🔗 feat(agents): use LibreChat prompt groups as agent instructions
Agents can link a prompt group revision or Production as their instructions. The link resolves at the start of each turn through a cached resolver. The cache clears on promote and delete. Editors without VIEW on the group see a restricted placeholder.
* fix: remove duplicate logger import from agent initialization tests
* fix: honor prompt management capabilities for linked agent instructions
* test: seed prompt manager capabilities in authorization fixtures
* fix: clear acknowledged linked prompt edits before version restore
* test: adapt merged chain coverage to prompt-aware payload helper
---------
Co-authored-by: Lia <lia@librechat.ai>
* perf: Async Local File Saves and Compile Hot-Path Regexes Once
* perf: Check Closing Code Fences Without a Per-Length Regex Cache
* test: Build the Delivery Route Config Before Routing Instead of Mutating It
mergeFileConfig now memoizes by config identity, so the CSV fallback tests
must set textFallbackWithoutTools when they build the request config rather
than mutate the object after the agent's routing already merged it.
* fix: Write Local Buffers Atomically So Concurrent Saves Cannot Interleave
Async writeFile calls to one deterministic path (OpenID and SAML avatars)
could truncate and interleave each other. Write through a temp file and a
rename instead, and add scenario specs for local saves and longer closing
fences.
* refactor: Move Local Save Logic Into packages/api
saveLocalBuffer, the temp-upload move and the atomic directory writes now live
in packages/api/src/storage/local.ts and receive their paths from the caller;
the Local strategy in /api keeps its logging and calls through. The traversal
check now runs before any directory is created.
* fix: Copy Moved Uploads Through a Temp File and Rename Into Place
Concurrent async copies to one destination could interleave just like direct
writes, so moveLocalFile now fills a sibling temp file and renames it.
* fix: Contain Every Local Write and Move Inside Its Target Directory
The traversal check that guarded saveLocalBuffer now runs in writeLocalFile
and moveLocalFile too, before any directory is created, and the buffer
save accepts only the images and uploads base paths.
* test: Define the Success Assertion Inside the Local File Saves Scenario
* fix: Give Atomic Write Temp Files a Fixed-Length Name So Long Targets Still Fit
* test: Send Image Dimensions and Read the Message Array in the Local Saves Scenarios
* feat: Return a Navigable Progress Tree When Checking a Running Subagent
check_background_task on a running or finished-but-undelivered subagent now
returns an activity digest: the child's turns, tool calls, and replies folded
to one line each and addressed by stable positional paths. Callers expand one
node or range with expand, and page with since against a settled-node cursor.
The owning process folds the child's update stream into a bounded tree that
keeps only tool names, the model-authored intent label, the tool-authored
outcome label, statuses, timings, and sizes. Routed claims carry the tree to a
poll on any replica, lists carry counts and the node in flight, and a finished
child whose owner is gone is rebuilt from its durable public projection.
The background-task card renders the digest as a foldable tree and links the
existing subagent activity panel.
* fix: Tighten Progress Digest Verdicts, Overflow Bounds, and Rebuilt Trees
Failed reply steps and schema-rejected calls now record as errors, and an
overflowed call is counted once without retaining it in the lookup maps.
A tree rebuilt from the durable projection re-checks completed calls with the
shared failure verdict, carries the projection's truncation, and tells the
caller its paths are a reconstruction. The card localizes folded summaries
instead of rendering the server's English tally.
* fix: Measure Single-Part Message Deltas in the Progress Digest
* fix: Scope Nested Progress Ownership by Run and Count Overflow Once
Nested runs now attach to the call recorded by their own spawning run, since
provider call ids repeat across runs. Only the step that announces a call can
count it as overflow, so later sightings of an unretained or evicted call never
re-count it or reopen history. A zero-valued since cursor is rejected, and the
card labels MCP tools with the configured server names.
* 🫗 perf: Release Message Histories of Conversations the User Has Left
Long agent conversations hold 12-18 MB of message JSON each in the React Query cache, and the default 5-minute cacheTime kept every conversation visited in that window. Switching between a few of them on mobile Safari grew the JS heap past 300 MB and crashed the tab.
retainMessages tracks when each per-conversation history loses its last observer and releases it once it has no observers, is not fetching, is not pinned, and is either older than 60 s or beyond the single most recently left conversation. The routed conversation, conversations with a running job, and conversations awaiting an approval decision stay pinned; releases wait while any mutation is pending. Returning to a released conversation refetches its history.
* 🫗 fix: Own History Collection, Configure the Grace, and Pin by Server State
Per-conversation histories get an infinite cacheTime while retention runs, so React Query's own five-minute collection can no longer drop a history a running job still pins; newly seeded histories schedule a pass; the grace and recent count come from interface.historyCacheTtlMs and interface.historyCacheRecent; the approval pin is replaced by the active-jobs set, which already lists jobs paused for a live approval; and Assistants histories stay pinned because deletion reads their thread id from the cache.
* 🫗 fix: Re-arm Collection for Histories Already Counting Down and Recheck Pins Promptly
A history left before retention started still had React Query's five-minute GC timer; a momentary observer now re-arms it under the infinite cacheTime. Histories kept only because they are pinned or fetching are judged again after 5 s instead of a full TTL, so a run that ends releases its transcript promptly.
* 🫗 fix: Exempt Assistants Histories Without Polling and Leave Fetching Histories Alone
Assistants histories are now exempt rather than pinned, so they are kept without a recurring recheck timer. The startup re-arm skips histories with a fetch in flight, since detaching a momentary last observer would cancel the request; settling the fetch re-arms collection on its own.
* 🔭 feat: Recover Stale Chunks Without the Error Page and Ship Client Logs to RUM
Stale chunks: a tab left open across a deploy that opens a code-split panel
requests a hashed chunk the new deploy removed. Vite's preload handler hands
the failure to the stale-asset recovery, which reloads, but the import then
resolves to `undefined` and `React.lazy` throws a TypeError into the route
error boundary, so the error page flashes before the reload. Lazy imports now
go through `lazyWithRecovery`/`importWithRecovery`, which turn that result into
a `ChunkLoadError`; the route boundary recognizes chunk failures (and any error
while a recovery reload is underway), asks the page recovery once, and renders
a localized "Updating to the latest version…" status. When the loop guard
declines, the normal error page with its reload action shows instead. The
page recovery is now idempotent within a page, so concurrent callers join the
in-flight reload rather than tripping the guard.
Client logs: with RUM in proxy mode, the client logger's warn/error calls,
error-boundary catches and stale-asset recovery events are exported as OTLP
log records through the authenticated `/api/rum/v1/logs` proxy. Records carry
allowlisted, scrubbed fields only, follow RUM session sampling, dedupe repeats
with a count, are budgeted per minute and per page, batch with backoff, flush
with keepalive on page hide, and stop after persistent failures. The proxy
now refuses non-OTLP content types and applies a per-user rate limit.
`RUM_CLIENT_LOGS=false` turns the export off.
* 🔒 fix: Keep Client Logs Opt-In and Drop Application Error Messages
- RUM_CLIENT_LOGS now defaults to off, like console capture, so enabling
RUM proxy mode never starts a new log stream on its own.
- Error messages are exported only for engine, browser and library
generated types (TypeError, SyntaxError, DOMException, AxiosError,
chunk failures); application errors keep type, status and stack only,
since their messages can echo prompt or response text. All quoted
fragments are now redacted.
- Batches are measured in encoded UTF-8 bytes of the exact request body,
and page hide drains every queued record that fits the keepalive quota.
- Queued stale-asset events are delivered as soon as the log exporter
starts, independent of the RUM SDK loading, and marked so they are
never logged twice.
* 🔒 fix: Export Only Known Generated Error Messages and Ack Queued Events
- Error messages are exported only when the whole text matches a known
engine, browser or library message shape (property access on
undefined, "x is not a function", fetch/abort/axios status, chunk and
CSS preload failures). The error class alone no longer qualifies, since
any code can throw a TypeError carrying arbitrary text.
- Queued stale-asset events are marked logged only after the collector
accepts the record carrying them, so an undelivered event replays on the
next page; in-flight events are skipped by the SDK path.
- A fractional RUM_PROXY_USER_MAX below one falls back to the default
instead of flooring to a limit of zero.
* 🔒 fix: Hold Unacknowledged Asset Events, Re-send In-Flight Logs on Hide
- The RUM SDK flush no longer drops queued stale-asset events whose client
log record is still unacknowledged: they stay queued and persisted,
flagged so their SDK action is not repeated, and leave the queue once
the collector accepts the record.
- Page hide re-sends the records of an unanswered regular request with
keepalive; each record belongs to the latest request carrying it, so a
late response to the original request neither marks nor requeues it.
- Client-log export stops when the authenticated layout unmounts.
- The proxy refuses /v1/logs while client logs, console capture and replay
are all off, so turning RUM_CLIENT_LOGS off also stops tabs that still
hold an older startup config.
* 🔒 fix: Export Only Complete Stack Frames, Never the Message Header
Stack reduction now strips the V8 `name: message` header (including every
line of a multi-line message) and keeps only lines with a complete V8,
Gecko or WebKit frame shape that ends in a URL or absolute path with a
line number. A message ending in a source-position-like suffix can no
longer pass as a frame.
* fix: centralize RUM delivery and asset recovery lifecycle
* fix: preserve RUM page lifetime and collector acknowledgements
* fix: retain page transport quotas and recover functional chunks
* fix: scope RUM client sessions to authenticated identity
---------
Co-authored-by: Lia <lia@librechat.ai>