* 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
* test: Pin the Bundled Theme Resolver Output to the Cache Epoch
* test: Pin the Resolver Fallbacks of an Empty Theme Definition
* test: Pin Only the Themes That Can Enter the Cache
* test: Pin an Inline Theme With Role Overrides
* test: Pin the Resolver Output by Role Fixtures and Role Fingerprint
* test: Pin the Persisted Cache Output Per Role and Mode Scope
* test: Generate the Cache Pin Fixtures From the Resolver
* test: Refresh the Cache Pin for the Promoted Stylesheet Roles
* test: Pin Fixture Inputs Apart From Resolver Output, Sort by Code Point
* test: Keep Sample-Independent Output Pinned When Fixture Inputs Move
* test: Pin the Accepted Appearance Values With the Resolver Output
* refactor: Use Spinner Tones, Label Variants and Shared Button Props in Remaining Components
Replaces text colour, round shape and size overrides with the primitives' own tone, variant, shape and size props where the merged classes are identical, drops redundant field overrides, and removes the prose and arbitrary transition classes that generated no CSS or have a token form.
* test: Cover the Quiet Ink of the Marketplace Search Clear Button
* test: Assert the Clear Button Hover Ink Only Where Hover Exists
* refactor: Replace Inline Styles With Classes Outside Chat and the Side Panel
Moves display, overflow, user-select, outline, will-change, backdrop and mask styling onto utility classes and CSS custom properties across Agents, Artifacts, Audio, Bookmarks, Plugins, Projects, Share, routes and the shared client components, and drops the recorded no-inline-styles suppressions they cleared.
* test: Cover Marketplace Grid Columns Driven by the Columns Variable
* test: Pick a Single-File Directory for the Moved-File Prune Fixture
* refactor: Give InputNumber an Option Variant for Setting Values
* fix: Ship the Option InputNumber Reset With the Package Stylesheet
* refactor: Prune the Setting Value Suppressions After Rebase
* refactor: Use Existing Variants and Drop Redundant Overrides in Nav, Skills, Prompts and Endpoints
* test: Cover the Header Menu Trigger in the Default Theme
* chore: Prune Design Suppressions After the Rebase
* 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
* a11y: Ring Tabs, Table, Dropdown and Menu Items in the Focus Control Role
* test: Tag the Focus Primitives Scenarios Literally
* test: Match the Dark Focus Rule That Yields to Outline Utilities
* refactor: Keep Menu Items and Table Rows on Their Existing Focus Treatment
* refactor: Leave Tabs and Dropdown on the Global Focus Outline
* test: Assert Both Outline Utility Exclusions in the Dark Focus Rule
* refactor: Clear Chat Input Design Suppressions Through Existing Variants
* test: Cover the Chat Composer Send Path After the Suppression Cleanup
* refactor: Keep the FileUpload Action on Its Ghost Pressed Fill
* refactor: Clear Raw-Color, Unknown-Class and Arbitrary-Value Suppressions in Auth, Nav and Endpoints
* refactor: Use the Registry Type Steps in the Nav Shortcut Chrome
* refactor: Prune Recorded Suppressions the Registry Type Steps Clear
* fix: Polish the Pull Request Chip and Card Header
Shrink the GitHub link icon and keep its hover on the icon only, drop the agent avatar from the chip so only the pull request icon remains, and open the hover card below the chip.
* fix: Scale the GitHub Icon With a viewBox and Rebase the Card Placement onto the Shared Panel
* refactor: Route Stylesheet Colours Through Theme Variables and Gate CSS Literals
* fix: Run the Colour Check Through Its Own Script
* fix: Read Numeric Fallbacks Inside Colour Function var() in the Colour Literal Check
* 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
* fix: Keep Chrome Surfaces and Destructive Confirms Legible in a Quiet-Chrome Theme
* fix: Soften Remaining Inline Destructive Triggers and Canonicalize Zero Chrome Alpha
* fix: Keep Pressed Feedback on the Quiet-Chrome Floating Control and Cover the Quiet Surfaces
* test: Scope the Quiet Surface Scenarios to the Header
* fix: Keep the Two-Factor Disable Trigger on the Soft Destructive Variant
* 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
* refactor: Give Sign-In Controls Button, Input and Alert Variants
* fix: Load the Field Stylesheet From SecretInput
* fix: Default the Floating Fields to the Placeholder Sentinel
* test: Cover the Sign-In Control Roles in the Default Theme
* test: Wait for the Floating Label Transition Before Reading It
* test: Read the Floating Label Scale Property
* fix: Keep Button Heights on Theme Roles and Honor Reduced Motion in Floating Fields
* refactor: Clear the Raw-Color and Unknown-Class Design Suppressions
* fix: Keep the Prose Classes style.css Still Reads
* fix: Keep the split-parent Marker the Screenshot Spec Waits On
* chore: Prune the Recorded Suppressions the Rebase Cleared
* refactor: Mark Message Text Containers With a Data Attribute
* test: Tag the Private Text Spec as a Scenario
* test: Cover Message Text Containers in a Mobile-Safe Scenario
* fix: Dim a Disabled InputNumber Through Its Nested Input
* test: Cover the Disabled InputNumber Wrapper in the Browser
* test: Tag the InputNumber Scenarios Literally
* fix: Make DataTable Row Estimates Breakpoint- and Leaf-Column-Aware
* test: Cover the Compact Row Estimate Against the Rendered Cell
* test: Tag the Row Estimate Scenarios Literally
* 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.
* fix: Reconcile stopped generations before detaching the stream
* test: Cover immediate Stop and delayed terminal reconciliation
* test: Accept both terminal outcomes of an immediate Stop
---------
Co-authored-by: Lia <lia@librechat.ai>
* 🏝️ fix: Apply the No-Workspace Decision Wherever an Agent's Code Route Resolves
A conversation set to run without attached workspaces failed mid-turn with
"Choose an attached workspace before using this agent." when its agent's
default machine was attached and the turn loaded a skill or another tool at
execution time. Request-start initialization honoured the decision, but the
execution-time tool loader re-resolved the agent's attached default and then
demanded a workspace selection the conversation intentionally never made.
The per-agent code rule now lives in one typed function,
resolveAgentCodeExecution (packages/api/src/code/agent.ts): it applies the
conversation's no-workspace opt-out, the run-code grant, the stateful
capability and the stateful environment policy, then resolves the base route.
Request-start initialization, lazy subagent metadata and graph members, the
execution-time and definition tool loaders, and the legacy execute_code
loader all go through it, so an opted-out agent lands on the managed default
route with no code tools at every site. Per-call subagent machine choices
offer and accept no attached machine in such a conversation, and a source
invariant test keeps new resolver call sites on the shared rule.
* fix: Pass the Implicit Stateful Route Rollout Into the Shared Code Rule
The per-agent code rule read the implicit stateful route rollout from the environment itself. It now takes it as a parameter, and the request boundaries (initializeAgent and withRequestCodeInputs) resolve it from the deployment configuration, so the rule stays a pure function of its inputs.
* fix: Carry the Initializer's Code Opt-Out Into Tool Definition Loading
initializeAgent hands the tool loaders a partial agent record (id, tools, provider, model) together with the code route it already resolved. Without the agent's route fields the definition loaders could not see a no-workspace opt-out and recomputed code execution as enabled, so tool classification could advertise the programmatic bash tool that execution then refuses. initializeAgent now passes attachedEnvironmentOptOut through every tool loader, and the shared rule keeps an opt-out its caller already decided.