* 🦊 feat: Add Claude Fable 5.2 Support
* fix: Preserve Snapshot Version Boundaries in Model Matching
* test: Measure the Snapshot-Safe Token Matcher Search
---------
Co-authored-by: Lia <lia@librechat.ai>
* perf: Look Up MCP Server Catalogs Concurrently for Tool Definitions
* test: Cover MCP Sign-In Order for Concurrent Catalog Lookups
* docs: Widen the mcpCatalogLookups Comment in the Example Config
* test: Cover the Catalog Lookup Bound Passed to the Definitions Loader
* 📏 fix: Measure Usage Percent Against the Allowance Each Period Granted
Store the credits granted at the start of each balance period on the record and measure the usage percent against it, so changing refillAmount or startBalance no longer moves a user's percent until their next grant. Legacy records fall back to the configured amount.
* 🕰️ fix: Ignore a Stored Allotment a Later Refill Has Replaced
Stamp each stored allotment with the time of its grant and measure against it only while no refill is more recent, so a refill by a replica that predates the field falls back to the configured amount instead of reporting usage against the prior period's allowance.
* 🔒 fix: Write the Allotment Grant Atomically and Return Its Period Start
Insert lastRefill with the credit, allotment and grant time when a balance record is created, so a racing creator never moves another's period start past its grant. Return lastRefill even without auto-refill so the client can place a stored allotment in its period, and fall back when it cannot.
* fix: Keep the Projects Section Expanded by Default
* fix: Label the Streaming Dot With a Tooltip and an Accessible Name
* fix: Move the Welcome Screen Footer Directly Under the Composer
* fix: Drop the Agent Name From Responses When the Selector Already Shows It
* fix: Align the Sidebar Section Headings With the Date Labels
* feat: Make the Welcome Footer Placement and Response Author Configurable
* fix: Hide the Memories Panel on the Agents Route
* test: Cover the Launch QA Chat Chrome in E2E Scenarios
* test: Assert the Section Heading Padding Merge Without Mocking App Internals
* fix: Read the Response Author Setting Through the Messages Host
* test: Give the Consumer Spec's Messages Host the Author Setting
* fix: Let Native Azure Deployments Declare Their Reasoning Efforts
The composer effort control needs explicit capability evidence on Azure,
because a deployment name does not identify its model, but the native
Azure config had no way to supply any, so the control could never appear.
Add an optional per-model reasoningEfforts list to Azure groups. The
endpoints config serves only model names and efforts, and the composer,
the submit check and the server override validation all resolve them
through getReasoningParamDefinitions. Undeclared deployments stay without
a control and model spec locks still apply.
* test: Assert Auto as the Reset Button in the Azure Effort Scenario
* test: Ignore Looping Animations When the Memory Alert Settles
The spec waited for every animation in the document to finish. A looping one
never does, so it hung whenever earlier specs in its shard left a chat list
long enough to show pulsing skeleton rows. Adding any spec can move it there:
the shard planner places it in shard 9 instead of 6 with this branch.
* fix: Retire Credentials by Their Committing Write and on Opt-In 2FA
Re-date password reset and enrollment cutoffs once the write that set them commits, so a credential minted while the write is in flight is retired. Opt-in 2FA confirmation now stamps twoFactorEnrolledAt and rotates the session like required enrollment. OpenID refresh ends a session established before a reset or enrollment instead of spending its IdP grant.
* fix: Bind Opt-In 2FA Rotation to the Caller's Refresh Session
Confirmation now requires the refresh session the request was issued with, rotates it in place and revokes only the others, so an access token on its own cannot trade enrollment for a long-lived session. The OpenID retirement check moves into the refresh recovery service and ends the session through the existing session-missing path, leaving the CJS controller unchanged.
* fix: Clear a Retired OpenID Session Against the User It Was Checked For
* refactor: Inject the Refresh Secret Into OpenID Recovery
* fix: Report a Reset Whose Cutoff Could Not Be Re-Dated
A failed re-stamp now propagates as RETIREMENT_RESTAMP_FAILED. The reset controller still revokes sessions and passkeys and answers CREDENTIAL_RETIREMENT_INCOMPLETE; the CLI re-stamps after its revocations and exits non-zero; enrollment revokes sessions before the re-stamp and mints nothing when it fails.
* fix: Re-Date the Reset Cutoff Only After the Link Is Consumed
The web reset re-stamps credentialsChangedAt in the controller once resetPassword has committed, consumed the token and sent the notice, so a failed re-stamp can no longer leave the link replayable. Revocations still run and the response reports CREDENTIAL_RETIREMENT_INCOMPLETE.
* fix: Retire Credentials on Every Exit Path After a Reset Commits
resetPasswordWithToken owns the post-commit steps: deleting the link and sending the notice no longer throw, and a link issued before the account's last credentialsChangedAt is refused, so it is spent even when its deletion fails. The reset write is conditioned on the cutoff it read, so one link commits once. The controller re-dates the cutoff and revokes sessions and passkeys whenever the password changed, and answers CREDENTIAL_RETIREMENT_INCOMPLETE if any of that fails.
* fix: Spend Undated Reset Links and Move the Reset Notice Into TypeScript
* fix: Tell the User When a Reset Could Not Sign Out Every Session
The reset page now recognizes CREDENTIAL_RETIREMENT_INCOMPLETE, shared from librechat-data-provider, and shows a localized warning that the new password is active with a sign-in action, instead of reporting the spent link as invalid.
* perf: Re-Date the Reset Cutoff From the Committed Write
The committed reset hands its credentialsChangedAt back through PasswordResetResult, so the controller re-stamps without a second user read.
* fix: Retire Every Superseded Credential Before Minting on 2FA Enrollment
Opt-in confirmation and setup finalization now revoke sessions, re-date twoFactorEnrolledAt and wait for the auth cache to drop the pre-enrollment document, running every step even when one fails. If any step fails they mint nothing and answer CREDENTIAL_RETIREMENT_INCOMPLETE; the settings dialog keeps 2FA on with a warning and the setup screen sends the user back to sign in with the new factor.
* test: Cover the Settings Warning When 2FA Enrollment Leaves Sessions Behind
* fix: Send the User Back to Sign In After an Incomplete Opt-In Enrollment
Enrollment retires the confirming tab's bearer, and an incomplete retirement mints no replacement, so the settings dialog now shows the backup codes and then signs out to the login page, whether the user completes setup or closes the dialog.
* test: Run the Retirement Warning Scenarios Against Their Own Signed-Out or Fresh Accounts
* test: Open the Sidebar Drawer Before the Account Menu on Phones
* fix: Report a Committed Opt-In Enrollment When Rotating the Session Fails
Once 2FA is promoted, a later failure in confirm2FA withdraws whatever session it may have minted and answers CREDENTIAL_RETIREMENT_INCOMPLETE, so the settings dialog hands over the backup codes and signs the user in again instead of reporting an invalid code.
* test: Prove an Incomplete Reset Does Not Resume the Retired Session
The Sign in action sends a browser with a live session through /login for about 150 ms before it lands in chat, so the signed-in version of the warning scenario only passed when the URL check caught that window. The warning scenario runs signed out, and a new scenario holds a pre-reset session and asserts its refresh is refused and the user stays on the login page.
* fix: Settle the Auth Cache After the CLI Reset's Final Cutoff Write
* test: Require the Login Form After Signing In From a Signed-Out Reset
* fix: Explain an Incomplete Session Retirement Before Restarting Sign-In After Required 2FA Setup
* perf: Start the Opt-In Enrollment User and Session Reads Together
Seven settings are read only from librechat.yaml as loaded, from the
YAML-only base config, or once at startup, yet the admin config API
stored overrides for them as if they applied. List them in
DEPLOYMENT_ONLY_CONFIG_PATHS, so writes skip them (deployment_only_path),
the merge keeps the librechat.yaml value, and GET /meta reports them:
- clientLimits (operator): /api/config reads appConfig.config.clientLimits
- telemetry.rum (operator): /api/config and the RUM proxy read the raw
telemetry block, the proxy through a base-only req.config
- conversationList (operator): loadConversationListLimits reads the
base-only config
- fileConfig.skills.deletionCleanupConcurrency (operator): the skill
deletion service loads the base-only config
- endpoints.agents.managementApi (operator): the agent management M2M
auth reads the base-only config
- passwordHashing (startup): configureHashPool runs once in the startup
checks
- interface.colorModeFromUrl (startup): injected into the HTML shell at
boot
GET /api/files bounds an explicit limit with req.config.fileListLimit,
but AppService never copied fileListLimit into the app config, so the
librechat.yaml value never applied. AppService now copies it.
* 🔎 fix: Keep Scoped Package Frames Out of the Log Email Redactor
The log redactor read node_modules/@scope/pkg/... as an address and replaced
whole stack frame locations with [REDACTED_EMAIL], in file, console and
OpenTelemetry output alike. An @ between path separators now names a scoped
package; addresses beside such frames are still masked.
* 🪪 feat: Name the Build and Loaded Config on OpenTelemetry Records
service.version now defaults to the image's BUILD_COMMIT ahead of the npm
package version. Each successful librechat.yaml load records a short digest
of the parsed file, which exported log records and request spans carry as
librechat.config.digest, and applies telemetry.stackTraceLimit to
Error.stackTraceLimit; unset keeps the process default.
* fix: Publish telemetry settings with the accepted base config
* fix: Initialize process settings before adopting cached config
* fix: Preserve runtime settings when cache writes are refused
* fix: Keep telemetry identity local and propagate Redis write errors
* fix: Partition merged config caches by the local base
* fix: Keep config cache failures recoverable
* test: Verify cache recovery contracts with typed fixtures
---------
Co-authored-by: Lia <lia@librechat.ai>
- Let agents use Langfuse prompts by production label or pinned version,
with the existing permission and usage checks.
- Add a configuration switch, disabled by default. Preserve saved links
while disabled, without resolving them or falling back to inline text.
- Share source-specific production and exact selections across agent
links and the prompt service. Reject source mismatches.
- Add revision lists for the Agent Builder version picker. Resolve
Langfuse instructions on each initialization without caching.
- Improve disabled and unavailable states and test source changes,
revision loading, and permission failures.
* 🥐 chore: Standardize Bun-First Workspace Typechecks
* fix: Preserve Bun 1.4.3 Checker Compatibility
* chore: Pin Bun 1.4.4 for Local and CI Typechecks
---------
Co-authored-by: Lia <lia@librechat.ai>
* refactor: Move Subagent Progress State and Content Folding Into @librechat/chat
* refactor: Attach the Subagent Activity Feed Through the Chat Transport
* test: Tag the Subagent Activity Panel E2E Specs With Scenarios
* test: Pin Replay, Ready and Live Steer Ordering Across an Activity Reconnect
* fix: Stop the Subagent Activity Feed on Refusals and Bound Idle Reconnects
* fix: Keep Attaching the Subagent Feed While the Child Thread Is Still Reserved
* test: Read Steer Order the Same While the Child Turn Streams and Once It Settles
* fix: Fence Auth User Cache Writes After Eviction and Evict Favorite Holders
An eviction now leaves a per-user fence in the auth user cache that outlives
every document read before it. The reader skips a cached document while its
user is fenced, and a lookup slower than one cache TTL is not cached, so a
request that read the user before a change can no longer repopulate the cache
afterwards, and a document the reverse index lost is hidden as well. Role and
user methods share one bulk eviction helper, and the terms reset only waits
out the TTL when an eviction failed.
Deleting an agent, deleting a user's agents and removing an agent from
favorites now evict the cached auth documents of the users whose favorites
changed.
* fix: Anchor Cached Auth Document Expiry to the Lookup Start
A stalled reverse-index write could land a stale document after the eviction
fence expired, with a fresh TTL. The document now carries an expiry two cache
TTLs after its lookup began; its Redis TTL is computed after the index write
and the reader refuses it past that expiry.
* refactor: Time the Auth User Lookup in the API Package
The lookup start that anchors a cached document's lifetime is now stamped by
timeAuthUserLookup in packages/api, so the OpenID JWT strategy only wires the
lookup through it.
* fix: Wait Out the Full Cached Document Lifetime After Failed Eviction
A document read just before a change can live two cache TTLs from its lookup,
so a credential change or terms reset whose eviction failed now waits that
long before reporting success.
* fix: Recheck Cached Auth Document Expiry After the Fence Read
A fence read that stalls can return after both the fence and the document
expired, so the reader checks the document's expiry again before serving it.
* fix: Bound outbound HTTP calls that had no timeout
Add timeouts.toolsMs, speechMs and imageGenerationMs to the timeouts block and apply the
existing budgets to the RAG delete paths, built-in tool APIs, TTS/STT providers (TTS also
aborts when the client closes), Stable Diffusion, Firebase reads and Mailgun. Calls made
before app config exists (remote config, RAG health, service key URL, Google refresh) get a
fixed 10 second budget.
* fix: Honor configured budgets for RAG deletes and per-chunk TTS deadlines
* refactor: Share one budget helper between speech and image CJS callers
* test: Cover a stalled RAG delete with a mock scenario
* test: Wait for the RAG embed before stalling the delete
* test: Embed at upload so the stalled delete has a vector to remove
* fix: Close a started TTS response on a late chunk timeout and share the service budget helper
* fix: Fail startup when the remote config fetch times out
* perf: Parallelize Serial Lookups on Agent Load, Discovery, Skills, and Schedules
* fix: Address Review Findings on Parallel Lookups
Stage same-level discovery results before collecting edges so a shared sibling is initialized once, bound resume snapshot fetches to small chunks so over-budget graphs stop early, and surface the first ordered image failure without waiting on later reads. Update the skill name test for bounded concurrency.
* test: Tag Existing Mock Specs as Acceptance Scenarios for Parallel Lookups
* feat: Make Parallel Lookup Bounds Configurable
Add a concurrency section to librechat.yaml for MCP catalog, skill name, skill file and resume agent lookups. Defaults equal the previous hard-coded values.
* style: Sort Imports for Configurable Lookup Bounds
* test: Match Model Spec Skill Resolution Args With App Config
* test: Close the Builder Drawer Before Chatting on Narrow Viewports
* fix: Surface Fatal Discovery Errors Without Awaiting Later Siblings
* fix: Reject Discovery on the First Fatal Load Regardless of Queue Order
* fix: Keep Image Encoding Fail-Fast With Parallel Reads
* fix: Reject Resume Snapshot Lookups Without Waiting on the Whole Chunk
* feat: Make Connected Agent Discovery Concurrency Configurable
* perf: Index Hot Lookups and Make Message Cursor Pagination Stable
Add narrow indexes for session refresh-token deletes, user-only tool call deletes, queued-turn delivery and reconciliation claims, agent code environment references, and updatedAt message pages. Add a TTL index to the KeyvMongo collection. getMessagesByCursor now sorts and pages on a unique (sortField, _id) tiebreaker with a millisecond-precise cursor while still accepting legacy cursors, and GET /api/messages caps pageSize in a TypeScript helper.
* fix: Keep the Message Id for the Cursor Under the Client Projection
* fix: Declare select on the Message Cursor Method Type
* feat: Make the Message Page Size Ceiling Configurable
* fix: Clamp the Default Message Page Size to the Configured Ceiling
* test: Cover Message Cursor Paging and Page Size Cap End to End
* fix: Continue Message Cursors Whose Sort Value Is Empty
* fix: Include Missing Sort Values When Paging Messages Descending
* perf: Resolve the Message Page Ceiling Beside the Ownership Read
* fix: Observe the Ownership Read While the Page Size Resolves
* style: Sort Imports in the Message Page Module
* refactor: Move Page Size Read Observation Into the API Package
* fix: Keep Missing and Empty Sort Values Distinct in the Message Cursor
* fix: Page Past Messages With a Missing Timestamp
* fix: Honor Documented Azure Model Assistants and fileConfig.stt Keys
Read the model-level Azure assistants flag from the group's models entry,
validate and merge fileConfig.stt, drop two never-read image tool env vars
from .env.example and fix the SharePoint scope example.
* test: Cover Model-Level Azure Assistants Through Config Overrides
The mock harness runs without CONFIG_REDERIVE_ENDPOINTS, so override
groups are never resolved there; cover the override path in the
resolution spec instead of e2e.
* perf: Bound client hygiene paths (lodash imports, timeouts, listener cleanup, upload concurrency)
* feat: Make client request timeouts configurable
* test: Cover the configured refresh deadline end to end
* feat: Rename client timeouts to client limits and expose upload concurrency
* fix: Keep the published refresh deadline for the next page load
* fix: Harden Timer Sweeps, SSE Writes, and Violation Counters
Guard SSE writes against ended or destroyed responses through one helper, catch and single-flight the job store and TTL cache cleanup timers, serialize in-process counter updates, cap the violation log, prune stale OAuth failure records, batch the active-job lookup, and count Redis keys with DBSIZE.
* refactor: Drop the redundant violation log entry copy
* refactor: Log single-flight sweep failures from the API package
* test: Cover active generation listing and client disconnect mid-stream
* refactor: Configure violation log retention and move title timeout into the API package
* feat: Configure OAuth failure retention through mcpSettings
* fix: Prune OAuth failures promptly under short retention
* feat(prompts): sync Langfuse prompts into the catalog
* refactor(prompts): compose the Langfuse prompt sync runner outside the admin handler
Add createLangfusePromptSyncRunner, which binds the lock, the prompt-group
methods, the ACL grant and the Mongo error predicates once and returns a
runner that takes the per-request source, connection-bound listPrompts,
lock lease and page cap. The admin handler receives that runner as one
dependency instead of forwarding its parts, and its config method
signatures return a LangfuseAdminConfig interface in place of Mongoose
document types.
In api, api/cache/distributedLock.js creates the one DistributedLock for
the process and api/server/services/LangfusePromptSync.js composes the
runner once with it; the admin route imports the composed runner.
* fix(prompts): report incomplete Langfuse syncs and gate the sync action
- Refresh the prompt-group and effective-permission queries after a failed
sync too, because earlier imports can already be committed.
- Return `complete: false` when the page limit stops a sync before the last
upstream page, and show a warning instead of the success message.
- Show the Sync prompts action only to users with `manage:prompts`, the
capability the sync route requires. Resolve the Langfuse startup-config
capabilities in one batched lookup.
- Document that an interrupted import can leave a group without its initial
PUBLIC grant, and that a page in progress can outlast an expired lease.
---------
Co-authored-by: Rebase Probe <probe@example.com>
The prompt service dispatches resolvePrompt by group.source. A read-only
Langfuse adapter fetches the text prompt on each use, with no cache, after
a resolver checks the deployment gate, the tenant, prompt sync, the
connection and the stored source identity. GET
/api/prompts/groups/:groupId/resolve returns resolved content for native
and Langfuse groups, with a per-user limit set by rateLimits.promptResolve
(default 60 per minute). Agent-instruction links stay native only.
* feat(prompts): add source identity to prompt groups
Add source, sourcePromptName, sourceProjectId and sourceDestination to
PromptGroup. productionId is required only for native groups. A unique
partial index on the source identity covers only groups that have
sourcePromptName, so native groups need no migration.
The create path drops client-supplied source fields, and the native
create upsert does not match langfuse groups. Records map a missing
source to native.
* fix(prompts): centralize sources and restrict native group matching
* feat(langfuse): test prompt listing and resolution from settings
Add a dry-run dialog in Settings > Langfuse that lists Langfuse prompts
and resolves one text prompt (production label or an exact version)
through the tenant's Langfuse connection. Nothing is written. A tenant
user's prompt reads never use the central env keys, even while
TENANT_ISOLATION_STRICT is off.
DevOps makes the feature available with LANGFUSE_PROMPT_SYNC_AVAILABLE
(timeout LANGFUSE_PROMPT_SYNC_TIMEOUT_MS). The tenant admin turns it on
with langfuse.promptSync.enabled.
Related: Linear AI-2271, ClickHouse/ai#4032
* fix(langfuse): isolate prompt credentials and expose prompt settings
Use stored credentials with deployment headers for prompt reads.
Show the settings tab when connection editing or prompt sync is available.
Keep connection controls and trace links under their existing gates.
Audit prompt-sync updates and reuse shared prompt response types.
* 🧬 feat: Re-Derive Azure Groups, Vertex AI, Custom Parameters and Spec Defaults for Config Profiles
AppService derives part of the served config from librechat.yaml at startup, and config
profiles merged into that output without deriving it again. Azure `groups` now merge by `group`
like `endpoints.custom` by `name`: a profile's partial group merges over the group of that
name, groups it does not name stay, indexed writes are refused, change batches take entry ops
on them, and groups that do not resolve over librechat.yaml and Base (or whose written `${VAR}`
is not set) answer `invalid_azure_groups`. Each merged group keeps the key below it unless the
profile supplies one, so the rebinding guard drops a key a partial item moves and a key a lower
layer dropped stays dropped; Azure re-entry compares groups merged the same way.
With `CONFIG_REDERIVE_ENDPOINTS=true` (opt-in for this release), a profile's Azure `groups`
resolve into what the Azure clients read (unconditional before, now behind the switch so stored
group overrides do not go live on upgrade), a profile's `endpoints.anthropic.vertex` derives
`vertexConfig` and the Anthropic models it serves where librechat.yaml configures Vertex AI, and
the Azure Assistants endpoint follows a profile's `assistants`. Startup logs the documents that
hold such overrides, the groups that would not resolve over librechat.yaml and Base, and the
Vertex AI overrides that never apply. Always on: Vertex AI's key file and region are base-only,
a profile may turn Vertex AI on only where librechat.yaml configures it, its settings may
reference only librechat.yaml's own Vertex AI variables (reads return them resolved), a
profile's `vertexConfig` is never applied and writes skip it (`derived_path`,
`rules.derivedPaths`), a model's own `deploymentName` resolves its `${VAR}` like the default one,
the region, project ID and the deployment name each model's requests send (the model name where
the client sends it as written) must stay in their URL host label or path segment, a `${VAR}`
there is a whole `${NAME}` reference only, the Anthropic client refuses any other deployment name
before building a request, and an invalid setup answers `invalid_vertex_config`. The rebinding
guard no longer binds the derived Vertex AI region, which is librechat.yaml's.
Custom endpoint `customParams` are expanded by `expandCustomEndpoint` into the served copy, so
`appConfig.config` stays librechat.yaml as written, and each endpoint a profile writes is
expanded again from its merged form (a changed `defaultParamsEndpoint`, OpenRouter defaults
for a profile's own endpoint); invalid definitions answer `invalid_param_definitions`. After
tenant scoping, `getAppConfig` derives `modelSelect`, `parameters` and `presets` again for the
specs a principal is served where nothing sets them, the agents `memory` capability follows
the merged memory config, and a model spec naming an unconfigured endpoint answers
`unknown_spec_endpoint`. Meta flags: `azureGroupMergeKey`, `customParamsExpansion`,
`specInterfaceRederive` and `endpointRederive`.
* 🪜 fix: Judge Re-Derived Config on What Every Profile Layer Leaves
Two re-derivations decided whether a profile had set a field from whether any layer ever set
it, so a lower profile's value tombstoned by a higher one still counted as set.
- Vertex AI (CONFIG_REDERIVE_ENDPOINTS=true): the marker that keeps a profile's
`endpoints.anthropic.models` over Vertex AI's is cleared by a later tombstone of those
models (or of `endpoints.anthropic` or `endpoints`), and such a tombstone derives Vertex AI
again, so the Anthropic endpoint serves Vertex AI's models instead of none. A tombstone of
librechat.yaml's own models does the same.
- Spec-dependent controls: `modelSelect`, `parameters` and `presets` are derived again where
their served value differs from the base config's, not only where the librechat.yaml-shaped
value does, so a control one profile sets and a higher one tombstones, or a tombstone of one
librechat.yaml leaves unset, follows the specs served instead of being dropped.
The memory capability, Azure Assistants, Azure groups and custom parameters already derive
from the merged result; tests now cover each set in one layer and tombstoned in a higher one,
and the reverse.
* 🧮 fix: Derive Each Config Part From What the Layers Leave
A tombstone of an object above a derived part's inputs, alone or followed by a layer that
recreates part of that object, left the part without what startup derives it to:
- An Azure endpoint recreated after a tombstone of `endpoints.azureOpenAI` or `endpoints` had
no groupMap, modelGroupMap or model lists, so its model lists fell back to the environment's
default Azure models, which requests could not map to a group. It now serves no group, with or
without CONFIG_REDERIVE_ENDPOINTS (completeAzureResolution).
- A tombstone of the whole `interface` left modelSelect, parameters and presets out, which the
client reads as off. They are derived from the specs served into a new interface.
- A tombstone of `endpoints.agents` or `endpoints` left no agents endpoint, while a tombstone of
its capabilities served the defaults. The agents endpoint startup derives is served there.
- A tombstone of a Vertex AI setting that leaves the setup unable to load kept the vertexConfig
derived below it. Vertex AI is off there, with a warning.
A table in service.spec.ts runs every derived part against every way a layer changes its inputs
(set, unset, a tombstone of the path and of each object above it, a layer recreating after such
a tombstone, Base on either side, tenant scoping, the switch off) through getAppConfig, and
compares each cell with what startup derives from the librechat.yaml the layers leave.
* 🧭 fix: Serve Only Model Specs Whose Endpoint the Layers Leave
A tombstone of `endpoints.custom` or `endpoints` in a higher profile (or the Base profile)
left the model specs of the custom endpoints it removes served, librechat.yaml's or a lower
profile's: the spec list pointed at endpoints /api/endpoints no longer offers, with the model
selector, parameters and presets still off for them. The write check only ran when the write
held `modelSpecs.list`, and the merge served stored specs as they were.
After the last layer, the merge now serves only the specs whose endpoint is a built-in endpoint
or a custom endpoint the YAML-shaped config the layers leave defines, the rule startup skips
librechat.yaml's specs by (deriveServedSpecs). A removed endpoint hides its specs until a layer
defines it again; where no spec is left, none is served (as with a tenant-hidden endpoint) and
the spec-dependent controls come back on. Tombstones of a built-in endpoint's settings keep its
specs, as startup does, and `addedEndpoints` stays as merged. A stored spec for an endpoint that
is not configured is left out on its own instead of being served; writes of one still answer
400 unknown_spec_endpoint.
The derived-part table in service.spec.ts gains the model specs served (with addedEndpoints and
the controls they decide) against tombstones of `endpoints.custom`, `endpoints`, and each of
`endpoints.openAI`, `azureOpenAI` and `anthropic`: by a profile, by Base under a profile, a lower
profile under a higher one, recreated above or by the same layer, with no spec left, and with
the switch off.
* 🧩 fix: Reconcile Re-Derived Config With Dev's Keyed Tombstones, Write Report and Read APIs
- Keyed tombstones of Azure groups (endpoints.azureOpenAI.groups["g"], now merged by key)
resolve the groups left again where the merge resolves them, and stay inert without
CONFIG_REDERIVE_ENDPOINTS.
- Keyed tombstones count as touching endpoints.custom, so served specs and custom parameters
are derived again after one.
- The served-spec derivation keeps modelSpecs while added endpoints remain, as the hidden
endpoint scoping does; hidden endpoint names leave addedEndpoints.
- Derived paths join the held paths every write skips, built on first use.
- Tests follow the merged behaviour: Azure groups merge by group, the agents endpoint is
derived again below a tombstone.
* 🧾 feat: Admin Config Write Report, Structured Issues and Deployment-Only Paths
Admin config writes dropped what the API never stores (base-only sections, interface
permissions, dedicated sections) with a 200 and no word of it, stored values nothing reads
(boot-time and operator-only settings, overrides of MCP servers librechat.yaml runs as local
processes, tombstones inside arrays), answered most 4xx without a stable code, returned
validation issues without the bound or option that failed, and refused every admin write
once the terms-acceptance modal was on for an admin who had not accepted it, including the
write that turns it off.
PUT, PATCH /fields, POST /fields/tombstone and DELETE /fields now answer with `applied` and
`skipped` (with a reason per location); a whole `interface` PATCH keeps its UI fields;
base-only paths are skipped on every route. A new DEPLOYMENT_ONLY_CONFIG_PATHS list (rate
limits, CloudFront, permission leases, OpenAPI, skill deletion, the tool filters, the agents
and MCP boot settings, `cache`) is skipped on write, kept at librechat.yaml's value by the merge
and published in GET /meta. Writes and tombstones inside a librechat.yaml stdio MCP server
answer 400 PROCESS_MCP_SERVER_OVERRIDE, and a whole-section value leaves those servers out.
GET of a document lists what the merge leaves out of it (`ignored`, `ignoredBasis`).
Validation issues carry allowlisted `params`; each refused allowedAddresses entry is one issue
with a `reason`; agent recursion limits must be whole numbers of at least 1, and the runtime
ignores any other value. The config handlers' 4xx carry a `code`, the capability middleware adds
AUTH_REQUIRED/FORBIDDEN, and the admin config router opts out of the terms gate. PATCH checks a
section manager on every section it names, skipped entries included, as /changes does. New meta
flags: writeReport, issueParams, adminTermsExempt.
* 🧪 test: Expect Issue Params in the Whole-Document Override Validation Scenario
Validation issues now carry `params` (here the expected and received types), so the scenario that
asserts the exact issue list for a rejected PUT expects them too.
* 🧪 test: Cover Merged Read Codes, Tenant-Scoped Read Reports and Deployment-Only Resolution
* 🔭 feat: Admin Config Read APIs (Resolved and Effective Config, Scope Catalog, Env Status)
Admin clients could read one config document at a time, or the deployment's merged config,
but nothing showed what a profile or a user resolves to: a client had to re-implement the
merge (Base-first precedence, merge keys, tombstones, the interface permission filter,
base-only fields, runtime stops, secret rebinding, the env allowlist) to preview it, and had
no way to see why part of a profile is ignored. Endpoint, model and tool pickers came from the
end-user routes, called as the signed-in admin, so they showed the admin's own scope and keys
and needed a browser User-Agent.
The admin config API now has four read routes. GET /resolved/:principalType/:principalId and
GET /effective?userId= return librechat.yaml, the documents that merge over it in merge order,
each with the parts the merge does not apply and why, and the result, in librechat.yaml shape.
They come from resolveConfigLayers, which tracks the same fold the served merge runs and is
pinned to it by parity tests, and from the stored documents rather than the override cache.
GET /catalog lists the endpoints (with the reason one is not served), models (served,
configured and defaults), MCP servers and tools a scope serves, resolved for the scope rather
than the caller and never with a user's stored key; GET /env-status reports whether each env
name the config uses is set, never its value. Every read is filtered to the sections the caller
can read, redacted as reads redact, and scoped to the caller's tenant. The admin Langfuse routes
now say why a deployment offers no connection settings. Meta reports resolvedApi, catalogApi,
envStatus and limits.catalogModelsTtlMs.
* 🪞 fix: Report Duplicate Custom Endpoints from the Served Definition
When librechat.yaml defines a custom endpoint name twice, or both `Ollama` and `ollama`, the
catalog kept the first definition for a name's env names, reason and models, while
`loadCustomEndpointsConfig` serves the last servable one. An entry could pair the served config
of one definition with the env names of another.
`resolveServedCustomEndpoints` now holds the runtime rule (the last definition with a name, key,
base URL and models wins under its served name), and `loadCustomEndpointsConfig`,
`loadConfigModels` and the catalog all use it. A name with no servable definition is reported
from its last one.
* ⏱️ feat: Make the Admin Catalog Model-List Lifetime Configurable
`GET /api/admin/config/catalog` reused a scope's model lists for a fixed two minutes. The new
librechat.yaml field `endpoints.catalogModelsTtlMs` sets that lifetime (milliseconds, `0` to one
hour, two minutes by default); `0` resolves the lists on every read. It is a base-only path, so a
profile cannot change it and `GET /meta` reports one value, now read from the deployment's config
on each request as `limits.catalogModelsTtlMs`.