* perf: Trim Per-Token and Per-Render Work in Streaming and Lists
* test: Assert Rendered Diff Rows Alongside Render Counts
* refactor: Read the Active Sidebar Row Through the Existing Index Selector
Drops the new Recoil selector: conversationIdByIndex(0) already yields a primitive id, so rows still skip re-renders on every conversation write. The DiffView row test keeps the real cn behind a spy and derives the per-row cost from the first render.
* test: Cover the Sidebar Active Row Across Chat Switches and New Chat
The Settings dialog is a Headless UI panel at z-50, not an OGDialog, so it set no dialog depth and its Select lists kept their z-40 layer, opening invisibly behind the panel. A new DialogLayer counts it as one dialog level, so popovers inside it take the depth-aware z-index they get inside an OGDialog.
* feat: Size Roles for the Select List
The Select list drew a fixed max-h-96 and min-w-[8rem], the last hard-coded sizes among the ten shared primitives. They are now the listMaxHeight and listMinWidth appearance roles, defaulting to 24rem and 8rem. The ClickHouse theme sizes the list by its trigger and keeps the 24rem cap, since Click UI caps it only at the viewport's available height.
* test: Resize the Select List From a Reference Theme
* fix: persist approval provenance in the resume claim and publish the pre-claim paths from any unapplied abort
The claim CAS now records the provenance it replaces. An abort that lands
before the resumed provider crosses its start CAS publishes those paths, so
schedule deletion, account deletion and user stops no longer label
model-authored chunks as user-submitted.
* test: add approval provenance scenario on the shared approval e2e helpers
* test: seed an earlier started segment before the unapplied abort case
* fix: label abort provenance by the published content and persist the same selection
A path the approval claim added is user-authored only once its tool call
carries output in the abort content, so an abort between the provider
start CAS and the resumed tool keeps the pre-claim labels, and an ask
answer stamped by the abort route keeps its own. AbortResult.jobData
carries the selection so the persisted row matches the final event.
* fix: keep claimed non-tool provenance paths on an abort
Only tool-call paths wait for their resumed call to complete; a steer the
claim already found in the seed content needs no decision to apply.
* fix: count a completed tool call with an empty output as applied in abort provenance
* fix: check abort provenance on the unfiltered content and remap it onto the published parts
* test: type the abort provenance overrides with the job store field names
* test: assert the preserved paths when an unanswered ask aborts
* refactor: Move Select and Menu Pointer Events to Classes
DropdownPopup and SelectContent re-enabled pointer events inside modal dialogs through inline style, which kept a no-inline-styles suppression on both primitives. Both now apply pointer-events-auto as a class and keep only the runtime z-index inline. The Select item indicator box takes the icon size role instead of a fixed h-3.5 w-3.5.
* test: Cover Popover Picks Inside Modal Dialogs
* test: Open Settings From the Drawer and Tag Indicator Scenarios
* test: Let Each Verify Project Set the Color Mode
* test: Measure the Select Indicator After the List Settles
* test: Drop the Settings Select Pick That Never Reached a Dialog
* fix: Read Theme Roles for the Last Artifact and Agent Chip Colours
The artifact mobile backdrop now reads surface-overlay like the dialog scrims, the refresh overlay over the rendered preview reads surface-media-overlay, and the agent builder's provider chip reads surface-primary and text-primary like the conversation icon chip. Monaco's built-in vs-dark canvas joins the third-party surfaces allowlist entry, and the allowlist no longer points at a closed sweep issue.
* test: Cover Theme Roles on the Provider Chip and Artifact Overlays
* 📍 feat: Show the Current Text Where a Missing Workspace Edit Belongs
Render the current-text excerpt that LibreChat-AI/code-interpreter#300 workers append to a missing edit's EDIT_CONFLICT diagnosis: a strict parse keeps it only when every row is well formed (contiguous numbers matching the stated range, a known mark, a bounded single line), and LibreChat renders it as a numbered block under its edit with a summary of which lines differ. The excerpt passes the file-content policy like a read_file result and reaches only the model; logs keep the excerpt-free message.
Also stop rendering every 409 as a text mismatch: a Code API rejection such as WORKSPACE_QUARANTINED now passes through with its own reason, and the worker's repetitive-candidate refusal is recognized.
* 🔒 fix: Name Other Attached Edit 409s by Code Instead of Forwarding Their Body
A 409 whose code is not EDIT_CONFLICT (a quarantined workspace) now gets a host-worded message naming only its validated code, with recovery guidance for WORKSPACE_QUARANTINED, and logs keep a body of just that code.
* 🧾 fix: Present Quoted Edit Excerpts as Partial Context, Not Text to Copy
A worker excerpt can window a long region and shorten wide lines with an ellipsis, so the guidance now asks the model to correct old_text against it and use read_file for lines it leaves out or shortens, here and in the attached edit_file descriptions.
* 🔐 fix: Quote Edit Excerpts Only Where the Workspace Allows read_file
A workspace that offers edit_file without read_file now never receives the worker's current-text excerpt, so a failing edit cannot read file content the operation policy withholds.
---------
Co-authored-by: Lia <lia@librechat.ai>
* feat: Remember Tool Approvals Per Conversation
Adds an opt-in "Always allow" choice to the tool approval card. When
endpoints.agents.toolApproval.allowAlways is true, the server marks eligible
paused calls with allow_always; approving with scope "session" stores that
exact tool name on the conversation, and later runs in the same conversation
fold the stored names into the policy as exact-name allow entries.
The server enforces every step: the resume route rejects a session scope the
pause did not offer, eligibility is rechecked against the live policy before
storing, the list is written only through an owner-scoped bounded method, and
generic saves and imports cannot set or clear it. Admin deny and ask rules and
programmatic hooks still win, stored names are ignored under dontAsk or when
the flag is off, and native code tools stay under the code approval picker.
The flag defaults to false, so existing deployments keep prompting.
* fix: Share the Effective Approval Policy and Persist Allows After Resume Fences
Offering, resume re-check, scheduled admission and createRun now read one
policy from buildEffectiveToolApprovalPolicy: endpoint rules healed against
MCP alias spellings, then the conversation's remembered tools. A call held by
a healed ask rule is no longer offered "Always allow", and a scheduled fire
whose known tools are all remembered is no longer rejected as pause capable.
The remembered-tools cap and name length cap move to
toolApproval.allowAlwaysMaxTools and allowAlwaysMaxToolNameLength (defaults
64 and 256). The card stops offering the choice for new tools once the cap is
reached instead of silently approving once.
The resume route stores remembered tools only after the schedule and project
context fences pass; a storage failure still approves the call once.
* fix: Offer Always Allow Only When It Will Hold
Offer allow_always only when storing the name would auto-approve the next
identical call on the run's own path: every MCP spelling of the tool passes
the healed static policy and no programmatic or plugin approval hook can
apply to it (the pause payload does not record which hook asked).
Remembered names now expand to every alias spelling of the same tool, and a
deny or ask on any spelling keeps the tool ineligible. A table-driven spec
walks the invariant through the real hook wiring.
* fix: Recheck Approval Hooks Before Remembering a Resumed Approval
The resume-time eligibility recheck now applies the same programmatic and
plugin PreToolUse hook check as marking, with a hook context built from the
resume request and the live plugin hook source. A hook registered after the
pause turns the choice into a one-time approval: nothing is stored and the
resume continues.
Document that toolApproval.allowAlways should be enabled only once every
replica supports it, since older replicas ignore the choice.
* fix: Judge Always Allow Offers Against the Run's Live Aliases and Active Cap
* fix: Charge Only New Tool Names Against the Remembered Approval Cap
* fix: Recheck Remembered Approvals Against the Paused Run's Aliases
* chore: Sort Imports in Agent Run After Rebase
* 📝 docs: Describe Attached-Workspace Lanes, Sandbox Scratch, and Skill Files in Tool Descriptions
- Lane-mode `cwd` now states that any call outside `.worktrees/<name>` (with or
without cwd, and file tools on such paths) is checkout-wide: it waits for
running worktree calls and blocks new ones until it finishes, so checkout-wide
calls are reserved for creating, pruning or removing worktrees.
- `command`/`cwd` state that the command starts in cwd, so the model does not
also cd into it; the lane-mode cd hint says the call ran checkout-wide.
- Workers advertising the native SRT sandbox profile (`anthropic-srt`,
`anthropic-srt:<preset>`) get a bash bullet that / and /tmp are read-only and
scratch files belong in $TMPDIR or the workspace. Carried as
`codeWorkspace.nativeSandbox` into tool definitions and the bash tool.
- The attached skill-aware `read_file` description says skill files are not on
the attached machine and must be written into the workspace to run there.
- Tightened the attached bash description so the native variant stays within
the 1024-character tool description limit.
* 📝 fix: Keep the Skill-Copy Warning on the Command-Only Workspace's Skill read_file
A workspace that offers execute_command but not read_file falls back to the
skill-only read_file definition. It now carries the same sentence as the
attached skill-aware definition, so the model knows bash_tool cannot reach
skill files by path there.
* 📝 fix: Name bash_tool in the Skill-File Warning Only When It Is Registered
The skill-copy sentence on attached read_file definitions now depends on the
attached bash_tool being registered beside it (includeBash and an advertised
execute_command), for the attached skill-aware definition, its custom
line-limit variant, and the skill-only fallback. Workspaces without commands
keep the plain skill description.
Attached workspace file tools now append a short, specific explanation when
the worker rejects a path with 422:
- NOT_FOUND from a current worker, or INVALID_PATH carrying its
"Workspace path does not exist" message through an older Code API, says
the path does not exist: wait for a command still writing it, or list the
directory to find the right path. For create_file it names the missing
parent directory.
- An older worker's bare INVALID_PATH on read_file, create_file or
edit_file, which it also returns for a missing file, lists the possible
causes: not written yet, a directory or symlink, or a missing parent
directory for create_file.
Other rejections are unchanged.
* 🍴 feat: Separate Machine, Workspace, and Git Controls
* fix: Preserve Recorded Checkout Status During Recovery
* fix: Preserve Keyboard Focus Across Machine and Workspace Menus
* fix: Align Linked Worktree Status with Checkout Selection
* fix: Reset Machine Browsing on Keyboard Workspace Opens
---------
Co-authored-by: Lia <lia@librechat.ai>
* 🏃 fix: List Every Running Chat in the Sidebar's Running Group
The Running group partitioned the Chats list's own rows, so a running chat
filed in a project, a pinned chat, or one past the loaded pages never
appeared in it. Running chats the loaded rows do not hold are now fetched
by id and merged in newest first, with a project badge on filed chats.
Narrowed lists (search, filters, facets, archive) keep only their own rows.
* fix: Keep Fetched Running Rows Current, Accessible, and Scoped
- Fetch only under the newest-first sort that shows the Running group.
- Re-ask within two seconds for a record not written yet, so a short
run is not missed; keep the 15-second refresh once it exists.
- Leave archived chats out of Running.
- Patch and clear the fetched rows through updateConvoInAllQueries and
removeConvoFromAllQueries, so renames, pins and removals show at once.
- Carry the shared-link state the list endpoints derive.
- Seed an empty conversation cache with the fetched record for navigation.
- Describe the focusable row with its project name.
* fix: Preserve Running Chat Cache Updates and Picker Keyboard Activation
* fix: Open the Assistant Picker Through Its Supported Keyboard Handler
* test: Keep SSE Cleanup Query Client Cancellation Compatible
* fix: Keep Temporary Chats Out of the Running Sidebar
* fix: Preserve Running Rows Across Initial Fetch Cancellation
* fix: Preserve Running Removal and Server Read Authority
* fix: Record Running Removal Before Query Creation
* test: Type Running Query Regression Props Explicitly
* fix: Keep Chat Settings Out of Running Sidebar Rows
---------
Co-authored-by: Lia <lia@librechat.ai>
A conditional generation create that loses its predecessor fence is an expected admission outcome: the store rejects before replacing anything, an automatic continuation defers without consuming an attempt, and a client restores its queued turn. Sibling background-tool wake-ups for one conversation race this fence by design, which logged every lost race as an initialization error with a stack.
Route the controller's initialization-failure log through a typed packages/api helper that logs a predecessor mismatch as a concise warning with the stream, conversation, continuation flag, and whether the current generation is active, and keeps every other failure at error level as redacted text.
* 🔐 fix: Authenticate Code Session Probes the Way Their Route Expects
The liveness probe for previously uploaded code-env files ran with no request from
agent initialization and no route identity, so against an attached or stateful
route it fell back to the managed X-API-Key, which a worker-bound route rejects
with 401. It now mints the bearer for the route's worker and sends the route's
profile and worker headers, exactly as that route's uploads and reads do. The
managed key is reserved for the default Code API and is not even loaded for other
routes; when a route needs a bearer that cannot be minted, its refs are left
unverified without sending a request.
* 🔐 fix: Gate the Session Probe on a Credential Source, Not the Global Auth Mode
* ✅ feat: Default Machine Selection and Linked-Worktree Lanes On
Per-chat machine choice from an agent's saved allowlist and linked-worktree
lane routing were both opt-in, so neither worked until a deployment found and
set its flag. Both are now on unless set to false: machine choice still only
applies to agents with a saved allowlist, and lanes still require a worker
that advertises git_linked_worktree. One helper per flag in data-provider
decides the default for every server reader and the advertised client config.
* feat: Advertise the Code Environment Decision Protocol by Default
Per-chat machine choice needs the conversation decision protocol, which the
client requires before offering allowlisted machines, but the protocol was
only advertised when CODE_ENVIRONMENT_DECISION_VERSION=1. With selection on
by default, authors could save an allowlist the composer never offered.
An unset or blank value now advertises protocol v1; any other value, such as
0, keeps the legacy-safe path.
* fix: Turn Machine Choice Off With the Decision Protocol Opt-Out
CODE_ENVIRONMENT_DECISION_VERSION=0 stopped advertising the protocol but
routing still accepted a non-default machine, so a cached tab or a direct
client could persist a choice during a mixed-version rollout. Machine choice
is recorded through that protocol, so isCodeEnvironmentSelectionEnabled now
requires both, for routing and for the advertised endpoints config. The
protocol resolver moves to code/protocol.ts (re-exported from code/config)
so execution and endpoints can use it without an import cycle.
* style: Format checkout routing regression cases
---------
Co-authored-by: Lia <lia@librechat.ai>
* feat: Give the Mobile Drawer Edge a Role and Move the Last Page Colours Onto Roles
The mobile drawer drew its edge with dark-only border utilities, the web source caption with gray-900 and white, the prompt panel's mobile backdrop with black at 20%, and the Insights agent picker popover with a dark-only override, so no theme could reach them.
drawer-edge paints the drawer's trailing edge: the drawer's own fill in light, where the scrim already separates it, and border-xheavy in dark, so dark mode keeps today's edge; a theme that sets only those two roles keeps the edge its mode drew. The source caption reads the media overlay roles, the prompt panel backdrop takes the page scrim the mobile drawer uses, and MultiSelect gains a widget surface that the Insights picker uses in place of its dark override.
* test: Pin the Drawer Edge Role in Both Modes and Under a Theme
* test: Write the Drawer Edge Scenario Tags Out Whole
* fix: Type the Drawer Edge Fallback So the Theme Resolver Stays Checkable
resolveTheme spreads every role fallback into one object literal, and each untyped conditional spread doubles the union the checker builds. One more pushed tsc for packages/client past CI's 6 GB heap. Typing the fallback as Partial<IThemeRGB> keeps it from adding to that union; a full check now peaks at about 4 GB.
* feat: Edit Projects in a Dialog and Match the Landing Background
* fix: No Fill on the Edit Project Description Field
* feat: Choose Project Files in the Your Files Dialog
* fix: Filtered Empty State and a Page Retry in the Project File Picker
* test: Scenarios for Project Dialogs and the File Picker
* fix: Retry the Failed Page or the Listed Files, Whichever Failed
* fix: Forget a Picker Page Failure Once the Query Recovers
* fix: Show the Picker Loading While a Further Page Loads
* test: Follow the Picker's Your Files Markup and Its Focus Return
* fix: Apply a Picker Page Result Only to the Query That Requested It
* fix: Hold the Edit Project Dialog Through a Save and Keep Page Failures per Search
* test: Match the Visible Rename Failure Toast
* fix: Refuse to Dismiss Edit Project From the Moment a Save Is Submitted
* fix: Announce the File Grid Result Count to Screen Readers
* fix: No Pressed Fill on the Thoughts Header
* fix: Even Thoughts Padding and Show the Floating Bar Only When the Header Is Off Screen
* fix: Re-measure the Thoughts Header on Every Visibility Notification
* test: Scenarios for the Thoughts Floating Bar
* test: Keep the Thoughts Scenarios to the Floating Bar
* feat: Refine the Ask Question Surfaces and Drop the Stop Shortcut Hint
* feat: Smooth Step Changes in Batched Questions With Numbered Option Rows
* fix: Swap Batched Question Answers Instantly While the Height Eases
* fix: Keep the Batch Card's Place in the Thread and the Answer Placeholder While Locked
* feat: Instant Option Row Hover and Typed Answers Replace Choices
* style: Fade Option Rows Slowly When They Lock
* feat: Swap Batched Questions Instantly While Only the Height Eases
* fix: Ease the Batch Status Lines and Keep Question Controls Unselectable
* fix: Stop the Batch Answer Area From Showing a Scrollbar
* fix: Keep the Locked Composer Placeholder Out of Text Selection
* feat: Check Mark on a Chosen Single-Select Answer
* feat: Turn the Question Move Chevron During the Composer and Chat Morph
* fix: Ease Only the Batch Card's Outer Height When Switching Questions
* fix: Pin the Batch Header and Buttons to the Card Edges While Its Height Eases
* fix: Confirm Batch Answers on Enter, Bound Long Prompts, and Keep the Form on Jotai
* test: Scenarios for Batched Ask Question Answers
* test: Pause the Fake Model on a Real Question Batch for the Ask Scenarios
* test: Run the Ask Scenarios in a Desktop Context
* fix: Cap the Batch Question Popover to the Viewport
* fix: Scroll the Capped Batch Card, Guard IME Enter, and Keep Focus on the Next Question
* 🛖 fix: Scope OAuth Binding Cookies to the Public API Path
* fix: Canonicalize OAuth Callback and Cookie Paths Together
---------
Co-authored-by: Lia <lia@librechat.ai>
* perf: Virtualize the My Files Table
* fix: Even Bottom Spacing Under the Compact Context Button
* feat: Overlay Tool Output Copy Actions and Show Full Output
* fix: Scroll the Virtualized My Files Table Itself and Expose Row Positions
* test: Scenarios for Tool Output Copy Reveal and Full Output
* test: Tab Through the Output Box to Reach the Copy Action
* fix: Open Terminal Output on Its Last Lines
* fix: Follow Streamed Terminal Output Only While the Reader Is at the Bottom
workflowSelectsWhatItFilters() split .github/workflows/static-checks.yml
with $-anchored multiline patterns, so on a Windows checkout with
core.autocrlf the trailing \r kept every pattern from matching and the
Design-rule suppressions gate failed every commit.
Parse through workflowFilters(), which normalizes line endings first, and
check in-script that the CRLF rendering reads the same lists, so CI on an
LF checkout catches a parser that only reads LF.
* ♻️ refactor: Native prompts behind a shared service and adapter
* test: Bound Slow Mongo Fixture Startup and Guard Cleanup
---------
Co-authored-by: Lia <lia@librechat.ai>
The SMTP transport options set `requireTls`, but nodemailer only reads
`requireTLS`, so the key was ignored. With EMAIL_ENCRYPTION=starttls,
a server that does not offer STARTTLS received the message over an
unencrypted connection instead of the send being refused.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: Size roles for the shared primitives
Button's xs, lg and icon squares, the large title input, the checkbox, menu, select and dialog icons and the switch's hit area read new size roles whose defaults are the fixed sizes they drew, and the menu row corner reads radiusLg. The ClickHouse theme takes Click UI's single button size, its small icon button and its checkbox and icon sizes. A spec pins the strict count of theme-driven primitives at eight of ten and what the other two still hard-code.
* fix: Hold the switch hit area to the target minimum in width and scan stylesheet colors
* test: Read every raw palette hue in the primitive guard
* test: Exempt only theme role fallbacks in the primitive guard
* feat: Tab minimum width role and a wider fixed-size guard
The primitive guard now also reads absolute arbitrary sizes, ring-offset palettes and 4 and 8 digit hex colors. The Tabs trigger's 100px minimum becomes the tabMinWidth role, which the ClickHouse theme sets to 0 so tabs size by their label as in Click UI.
* fix: Keep app icon buttons and their companions on the button size role
The passkey rename input keeps the field height, and the agent builder panel headers size their back button and balancing spacer from size-theme-button, so a theme that changes the button height keeps those rows aligned.
* fix: Size menu glyphs from the icon role and floor touch targets at the minimum target size
* fix: Let menu glyphs fill their slot and keep the dialog close target at the minimum size
* test: Probe the menu glyph inside a flex row, as DropdownPopup renders it
* fix: Hold icon button squares to the minimum target size
* fix: Bound the icon and checkbox size roles to the room their layouts leave
iconSize takes 0.75 to 1.25rem, iconSizeLg 1 to 2rem and checkboxSize 1 to 1.5rem, so a theme can retune them without shrinking a checkbox below the box it was or pushing an icon past the inset it sits in.
* fix: Hold the icon-only Dropdown and header spacers to the minimum target size
* fix: Floor the button size roles at the target minimum and let callers replace the control height
* test: Move the unknown appearance markers off the new title field height
* fix: Size the compact step, the exported Dialog and the combobox icons from roles
The Button and Dropdown compact recipes read a buttonHeightCompact role, the exported Dialog's action buttons and close glyph read buttonHeight and a bounded iconSizeMd, Combobox icons follow iconSize, and the checkbox callers drop their fixed sizes so checkboxSize reaches them. minTargetSize may no longer exceed buttonHeight or fieldHeight, so the target floor never pulls icon buttons out of line with the fields beside them.
* fix: Size the collapsed Combobox square from the control height role
* fix: Hold every Button size and the collapsed Combobox to the target minimum
* fix: Let section header buttons keep their own text height
* test: Treat a zero size as a reset in the primitive guard
* fix: Enforce the target size at the roles instead of on every Button
A minimum height on every Button size grew callers that draw a smaller control on purpose, such as the sortable table header (h-auto) and the 20px artifact and attachment row actions. The floors come off the Button sizes and icon squares; a theme that sets minTargetSize may instead not size any button or field below it, and the new Button size roles keep their 24px floor.
* fix: Check the control and large field heights against the target floor
* fix: Hold the target floor at a fixed 24px and floor the large field height
* fix: Keep the passkey rename field on the button height and drop the fixed MCP checkbox size
* fix: Size the Combobox check glyph from the icon role and scope the README floor claim
* 🪢 feat: Collapse Activity Folds From Their Rails
Hovering an open fold's rail lights the line and swaps the header's glyph for a collapse knob; clicking the rail collapses that fold and brings its header back into view.
* fix: Stabilize Fold Rail Hover and Header Reveal
* fix: Reserve the Chat Toolbar When Revealing Folds
---------
Co-authored-by: Lia <lia@librechat.ai>
* feat: Serve Built-In Endpoint Model Lists From Config So Principal Overrides Can Narrow Them
OpenAI, Google and Anthropic model lists came only from *_MODELS env vars,
which are global, so a role or group override could not narrow them. A
configured endpoints.<name>.models list now replaces the env list and is read
from the per-request config, matching Bedrock.
* fix: Skip OpenAI and Anthropic Model Discovery When a List Is Configured
* feat: enforce required two-factor authentication
Require local and LDAP accounts to enroll in TOTP before they can use the
app when ENFORCE_TWO_FACTOR_AUTHENTICATION is set. Sign-in, refresh, bearer
verification, optional share auth and image authorization all route an
unenrolled account into a staged setup flow, and every bearer credential
minted before enrollment or a password reset is retired.
Password reset retirement uses the existing credentialsChangedAt stamp, and
commitPasswordReset clears any staged enrollment in the same write. Passkey
sign-in follows the same enrollment gate as password sign-in.
* test: cover passkey sign-in handing off to required enrollment
* refactor: keep Mongoose user types out of two-factor auth contracts
* fix: withdraw a minted session when its retirement recheck fails
* fix: hold Agent API keys and the reset CLI to the required two-factor policy
* fix: adopt a setup token handed off after the setup screen mounted
* fix: move every tab that receives an enrollment hand-off into setup
* fix: read the enrollment gate's retirement cutoff in system scope
* fix: clear minted session cookies before the fallible session deletion
* fix: adopt a setup token persisted before the setup screen subscribed