Commit graph

1853 commits

Author SHA1 Message Date
lia-by-librechat[bot]
3376942149
🛒 fix: Correct Agent Admission and Failed-Run Billing (#18157)
Co-authored-by: Lia <lia@librechat.ai>
2026-11-14 12:20:51 -05:00
lia-by-librechat[bot]
f2b4a58b0e
🔦 fix: Skip Unselected Tool Schemas Under Legacy PII (#18158)
Co-authored-by: Lia <lia@librechat.ai>
2026-11-14 12:20:16 -05:00
lia-by-librechat[bot]
e7669c147b
🐹 fix: Bound In-Memory Configuration Cache Retention (#18156)
* 🐹 fix: Bound In-Memory Configuration Cache Retention

* test: Require User Principal in Config Retention Fixture

---------

Co-authored-by: Lia <lia@librechat.ai>
2026-11-14 12:19:58 -05:00
lia-by-librechat[bot]
8ed7a7d3d7
🍂 fix: Emit Persisted Agent IDs in Attribution Headers (#18151)
Co-authored-by: Lia <lia@librechat.ai>
2026-11-14 12:15:33 -05:00
lia-by-librechat[bot]
4074c2a279
🦑 chore: Upgrade OpenTelemetry HTTP Instrumentation to 0.222.0 (#18152)
Co-authored-by: Lia <lia@librechat.ai>
2026-11-14 12:14:49 -05:00
Danny Avila
4c6da07a7a
🚠 feat: Bridge Registered SDK Agents to Remote Runtimes (#18150)
* feat: bridge registered SDK agents to remote runtimes

* docs: make remote runtime parity gates explicit

* fix: bound runtime authorization admission and shutdown

* fix: reject unresolved runtime secrets and preserve checkpoint queries

* fix: order remote policy hooks after preceding events
2026-11-14 10:56:05 -05:00
lia-by-librechat[bot]
59cf1af4b7
🦠 fix: Patch Vulnerable Database and Transport Dependencies (#18124)
Co-authored-by: Lia <lia@librechat.ai>
2026-11-14 09:14:34 -05:00
Marco Beretta
4a13f26651
🧽 fix: Guard Remaining Mongo Cleanup In Post-Audit Tests (#18132)
* fix: Guard Remaining Mongo Cleanup In Post-Audit Tests
2026-11-14 15:08:10 +01:00
Danny Avila
fad2c51da4
🏇 feat: Register SDK-Backed Agents for Native Chat (#18114)
Some checks are pending
Docker Dev Images Build / publish (push) Waiting to run
Sync Helm Chart Tags / Ignore non-main push (push) Waiting to run
Sync Helm Chart Tags / Sync chart tags (push) Waiting to run
* feat: register SDK-backed agents through agent management

* fix: gate SDK binding writes and preserve native lifecycle
2026-11-13 13:02:53 -05:00
Danny Avila
fb3b299de6
🪪 feat: Add Agent Identity to Provider and MCP Header Templates (#18113)
* feat: resolve executing agent ids in MCP header templates

* test: preserve MCP config source literal types

* 🪪 feat: Forward the Active Agent Id in Request Header Placeholders

A gateway in front of LibreChat sees the user, the conversation and the
message, but not which agent is running — so it cannot attribute spend per
agent, apply per-agent limits, or tell agent traffic from plain chat. Adds
`{{LIBRECHAT_AGENT_ID}}` as its own namespace beside the user / body / OpenID
ones, resolving wherever the existing request placeholders already work.

The value is the primary agent's, derived once per run, so subagent steps and
auxiliary calls (summarization, titles, activity labels, memory extraction)
forward the id of the turn they belong to rather than their own. Only
persisted agents resolve: ephemeral ids embed user-authored preset text that
is unsafe in a header value, so ephemeral runs and non-agent requests resolve
to an empty value rather than forwarding literal template text.

No behaviour change unless the placeholder is configured. The MCP surface
(#14303) is not covered — its connection classification derives from
`ALLOWED_BODY_FIELDS`, so a new namespace needs a follow-up.

(cherry picked from commit 8a3f1016f0)

* test: cover shared provider and MCP agent header resolution

* docs: clarify absent agent placeholder resolution

* fix: preserve agent header boundaries across transport lifecycles

* fix: retain Google header provenance during agent resolution

---------

Co-authored-by: Jiří Krejčí <51734696+krejcji@users.noreply.github.com>
2026-11-13 13:02:39 -05:00
Marco Beretta
fbca86bba9
⚙️ fix: Guard Mongo Cleanup In Package Service Tests (#17992)
* fix: Guard Mongo Cleanup In Package Services Tests
* fix: Guard Mongo Cleanup In Agents Precedence And Promotion Tests
2026-11-13 18:18:17 +01:00
Marco Beretta
8c569a15ac
🤖 fix: Guard Mongo Cleanup And Await ACL Test Cleanup (#17991)
* fix: Guard Mongo Cleanup In Package Agents Tests
* fix: Await Actual ACL Cleanup In Shared Link Tests
2026-11-13 17:49:53 +01:00
Marco Beretta
24da3c92ed
🪨 fix: Supply Nonempty MCP Tool Descriptions for Bedrock
Supply nonempty MCP tool descriptions for Bedrock while preserving existing descriptions and approval identities.

Fixes #18013
2026-11-13 17:22:15 +01:00
Marco Beretta
ddbff5ac81
🪶 perf: Load Math, Highlighting, Side Panels and RE2 Only When Needed (#18108)
- perf: Stop Shipping the Node Crypto Polyfill to the Browser
- perf: Keep the Query Devtools Out of the Boot Chunks
- perf: Load Side Panel Tabs When They Open
- perf: Keep the RE2 Engine Out of the Browser Bundle
- perf: Load KaTeX and highlight.js Only for Math and Code
- test: Cover Code That Loads on First Need
- fix: Apply Loaded Math and Highlighting Whatever the Load Trigger Matched
- test: Assert Rendered Formulas Without Assuming Display Math
- fix: Retry a Failed Math and Highlighting Load While Mounted
- fix: Always Load Highlighting Where the Language Is Guessed
- fix: Register the PII Sizer Wherever Config Loads
- fix: Load Preview Math From the Filled-In Prompt and Keep Dollar Signs Literal
- test: Register the PII Sizer Where the Filter Harness Validates Config
- test: Preserve Side Panel Layout During Lazy Loading
2026-11-13 17:21:50 +01:00
lia-by-librechat[bot]
8246e2191f
🚋 fix: Isolate Sentinel-Aware Config Cache Entries (#18097)
Co-authored-by: Lia <lia@librechat.ai>
2026-11-12 21:59:37 -05:00
lia-by-librechat[bot]
31b5d8d1c1
🥚 fix: Wait for Initialized Skill Metadata Across Replicas (#18094)
Some checks are pending
Backend Unit Tests / Tests: @librechat/api (shard 4/4) (push) Blocked by required conditions
Backend Unit Tests / backend (push) Blocked by required conditions
Codegraph E2E Vote Gate / Gate (push) Waiting to run
Codegraph E2E Votes / vote (shard 1/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 10/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 2/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 3/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 4/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 5/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 6/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 7/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 8/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 9/10) (push) Waiting to run
Docker Dev Branch Images Build / publish (push) Waiting to run
Frontend Unit Tests / Client build recovery regression (push) Waiting to run
Frontend Unit Tests / Codegraph select (push) Waiting to run
Frontend Unit Tests / Build packages (push) Waiting to run
Frontend Unit Tests / TypeScript type checks (client) (push) Blocked by required conditions
Frontend Unit Tests / Tests: @librechat/chat (push) Blocked by required conditions
Frontend Unit Tests / Tests: @librechat/client (push) Blocked by required conditions
Frontend Unit Tests / Tests: Ubuntu (shard 1/2) (push) Blocked by required conditions
Frontend Unit Tests / Tests: Ubuntu (shard 2/2) (push) Blocked by required conditions
Frontend Unit Tests / Vite build verification (push) Blocked by required conditions
Frontend Unit Tests / frontend (push) Blocked by required conditions
Playwright E2E Tests / Codegraph select (push) Waiting to run
Playwright E2E Tests / e2e () (push) Blocked by required conditions
Playwright E2E Tests / MCP list_changed (replica count 1) (push) Blocked by required conditions
Playwright E2E Tests / MCP list_changed (replica count 2) (push) Blocked by required conditions
Playwright E2E Tests / MCP Apps (browser and server) (push) Waiting to run
Playwright E2E Tests / e2e (push) Blocked by required conditions
* 🥚 fix: Wait for Initialized Skill Metadata Across Replicas

* fix: Preserve Initialization OAuth During Resume

---------

Co-authored-by: Lia <lia@librechat.ai>
2026-11-12 21:00:01 -05:00
Danny Avila
cbd4cbb5fb
🧲 fix: Settle Fast Pinned Drops, Defer the Hidden Mobile Header Menu, and Close Untraced E2E Races (#18087)
* 🧪 test: Read the Artifact Scrim's Blur From the Persistent Scrim

"a small blur surface still blurs by four pixels" read the backdrop filter
of `#artifact-viewer [role="status"]`.first() once, with a single evaluate.

The artifact panel's lazy tabs also render a `role="status"` loading
placeholder until their chunk arrives, and the panel re-renders while it
opens. A one-shot read that resolves the wrong status, or a node React has
just replaced, gets the computed style of a detached element: an empty
string instead of `blur(4px)`.

Select the always-mounted refresh scrim, the only status that carries
`aria-hidden`, and assert its filter with `toHaveCSS`, which re-resolves and
retries until the value settles.

Untraced, on two CPUs: 11 of 20 runs failed with `Received: ""` before,
20 of 20 pass after.

* ⚡ perf: Mount the Mobile Header Menu Only Once a Phone Layout Has Shown It

The chat header rendered both of its action surfaces on every load: the
desktop buttons and the mobile overflow menu, hidden with `className="hidden"`
on wide screens. The hidden menu still mounted its whole tree on desktop,
with its bookmark, export, share, temporary-chat and pull-request hooks and
its dialog providers.

Mount the overflow menu only while the drawer viewport is active, and keep
it mounted once it has been shown, so resizing back to desktop does not drop
a dialog opened from it.

Measured with a React DevTools hook counting component renders over a cold
desktop load of a saved conversation (7 warm navigations each, production
build): 1,313 component mounts before and 1,242 after, the overflow trigger
no longer in the DOM, and the median component re-renders over the load
5,835 before and 5,682 after.

`dropped-classes.spec.ts` read the overflow trigger's size on a desktop
viewport, where it was only attached; it now reads it at phone width, where
the trigger is visible.

* 🧲 fix: Settle a Pinned Row's Position on Drop, Not Only on Hover

A pinned row reorders in its `hover` callback, which judges the pointer
against the hovered row's midpoint using the offset react-dnd last recorded.
The HTML5 backend delivers hover once per animation frame, so a release that
lands in the same frame as the move across the midpoint is judged against the
offset from before it: the swap is refused and the drop keeps the old order.
A quick, deliberate drag is discarded.

The drop handler now runs the same placement against the final pointer offset
before returning its result, so `end` commits the order the pointer actually
ended on. Hovering is unchanged.

The new regression holds the hover frame and fires dragover/drop at a point
past the midpoint and at one short of it. On the previous handler the first
case keeps the old order; with this change both cases match the pointer.

In a real browser, with a drag that releases without waiting for a hover
frame: "a pinned chat cannot be dragged through a pinned model" kept the old
order in 4 of 15 untraced runs on the previous handler and 0 of 15 with this
one.

* 🧲 test: Release a Pinned Drag Without Waiting for a Hover Frame

The pinned drag helper waited for an animation frame after each settling
move, so react-dnd had delivered a hover at the final position before the
release. That kept the reorder scenario green while a release landing in the
same frame as its last move was discarded by the app.

The drop handler now settles the final pointer position itself, so that wait
no longer stands between the scenario and a failure; it only hides the
fast-release path. Release straight after the settling moves again, so the
scenario covers it.

Untraced, on two CPUs, with this helper: "a pinned chat cannot be dragged
through a pinned model" failed 4 of 15 runs against the previous drop handler
and passed 15 of 15 with the settled drop; the whole pinned-drag-rules file
passed 30 of 30.

* 🧪 test: Publish the Reaper Fixture's PID Only After It Is Written

Two reaper tests wait for a PID file to exist and then read it. The shell
creates the file when it opens the redirection and writes the PID a moment
later, so a read in between gets an empty file. `Number('')` is 0, and
`isGone(0)` reports true because there is no `/proc/0`: "escalates to
SIGKILL when the tree ignores SIGTERM" and "sweep reaps a group that
outlived a clean root exit" then fail their "still running" assertion.

Write the PID to a temporary file and rename it into place, so the file
appears only with its content. With a 0.3 s pause forced between the
redirection and the write, both tests fail on the old fixture and pass on
this one.

Also kill each spawned process group after every test, so a failing test
does not leave its trap-protected `sleep 30` behind, and read the process
state with `ps` where `/proc` does not exist.

* 🔦 test: Keep a Measured Trace and a Startup Profile When Lighthouse Fails

When the serial-latency audit fails a budget, the uploaded `.lighthouse/`
holds the JSON and HTML reports only. They name the slow metric but not the
main-thread work behind it, so a total-blocking-time failure cannot be traced
to the code that blocked without reproducing it locally.

- Run Lighthouse with `--save-assets`, keeping each run's measured
  `lhr-*-0.trace.json` for Chrome's Performance panel. Its raw DevTools
  network log is deleted; the trace is parsed and every string value has the
  session cookie values redacted, so numeric timings and JSON structure
  survive even for short cookie values. A trace that does not parse (an
  interrupted run) is deleted rather than uploaded raw.
- After a failed audit, navigate once more with the CDP profiler running and
  save `.lighthouse/startup.cpuprofile`, including three seconds after the
  transcript appears so late catalog callbacks are sampled. This runs after
  the measured audits, so it cannot change their numbers, and a profiling
  error never replaces the original failure.

Budgets, runs and the workflow are unchanged; the workflow already uploads
`.lighthouse/`.

* 🔦 test: Keep Lighthouse Traces Only When the Audit Fails

Each saved trace is about 45 MB, so keeping all three on every run turned the
always-uploaded `lighthouse` artifact from about 2 MB into about 137 MB for
runs that pass and need no diagnosis. Delete the traces once the test's last
assertion has passed; a failing run still uploads them with its reports.

* 🧪 test: Read the Streaming Shimmer From the Live Footer

"an in-flight label sweeps, and high contrast holds both stops opaque" read
the stream-elapsed label's styles once through `locator.evaluate`. The label
lives in the streaming footer, which re-renders while the reply streams; when
the node the locator resolved was replaced before the evaluate ran, the read
came from a detached element or failed.

Assert the animation name and background clip with `toHaveCSS`, which
re-resolves and retries, and read the shimmer's dip alpha by querying the
current node inside the evaluate, polling until it settles.

Untraced, on two CPUs: 4 of 20 runs failed with `Received: ""` before,
20 of 20 pass after.

* 🧪 test: Click the Drawer's New Chat Link, Not Whichever One Is Exposed

"returns focus after right-clicking an unopened running menu on a small
screen" opens the mobile drawer and clicks
`getByRole('link', { name: 'New chat', exact: true })`. On a saved chat the
header row also offers a New chat link, and it hides only when the sidebar's
expanded state commits. On mobile that commit is deferred: the drawer starts
sliding first and the state flips a few frames later inside a transition,
which a streaming run keeps pushing back. The drawer's Close button is
already visible during the slide, so the test reaches the click while both
links are exposed and fails with a strict mode violation.

Scope the locator to `#mobile-drawer`, the link the test means.

Untraced, on two CPUs: 20 of 20 runs failed on the previous locator and 20
of 20 pass with this one.

---------

Co-authored-by: Dustin Healy <54083382+dustinhealy@users.noreply.github.com>
2026-11-12 09:47:46 -05:00
dwaddle
40671fd88c
🐑 fix: Avoid Per-User Copies of Base App Config (#18057) 2026-11-12 07:25:14 -05:00
Danny Avila
4b024ffd21
🎯 fix: Match the GPT-6 Cyber API Mode to an Exact Endpoint URL (#18071)
* 🚇 fix: Preserve Exact Cyber Endpoint API Contracts

* refactor: Name the Exact Chat Completions Check

Move the exact-URL test into `isExactChatCompletionsURL`, which states the
rule once and tolerates an unparseable URL on its own rather than relying
on the native-host classification having parsed it first.

Keep the summary's custom endpoint lookup inside the native Cyber branch,
where it was, and pass `directEndpoint` to the request shaping from there,
so a gateway summary does not resolve endpoint secrets it never uses.

Collect the request URL in the SDK test and assert it afterwards: an
assertion thrown inside the transport callback reaches the SDK as a
connection error. Cover the default for exact `/responses` URLs, base URLs
and paths that only contain `/chat/completions`, and an OpenRouter exact
URL.

* fix: Keep an Endpoint's Responses API Drop for Cross-Provider Cyber Summaries

A summary that targets another custom endpoint resolves that endpoint
through `getOpenAIConfig`, which applies a `useResponsesApi` drop by
removing the field. The native Cyber shaping that follows read the missing
field as "unset" and defaulted to the Responses API again, unless the
summary ran on the agent's own provider. An Anthropic agent summarizing
with GPT-6 Cyber on an exact Chat Completions endpoint that also drops
`useResponsesApi` therefore still sent a Responses body to that URL.

Record the drop as an explicit `false` on the resolved overrides. An
explicit `useResponsesApi` in the summary's own parameters still wins.

Cover summaries from an Anthropic agent, a built-in OpenAI agent and the
endpoint's own agent, with and without the drop, and with the summary
provider inferred from the agent.

---------

Co-authored-by: Lia <lia@librechat.ai>
2026-11-12 07:20:00 -05:00
Danny Avila
06c58c5fc1
🚪 fix: Refuse Interactive MCP Sign-in on Remote Agent API Runs (#18058)
Some checks are pending
Backend Unit Tests / TypeScript type checks (push) Blocked by required conditions
Backend Unit Tests / Circular dependency checks (push) Waiting to run
Backend Unit Tests / Tests: api (shard 1/3) (push) Blocked by required conditions
Backend Unit Tests / Tests: api (shard 2/3) (push) Blocked by required conditions
Backend Unit Tests / Tests: api (shard 3/3) (push) Blocked by required conditions
Backend Unit Tests / Tests: data-provider (push) Blocked by required conditions
Backend Unit Tests / Tests: data-schemas (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 1/4) (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 2/4) (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 3/4) (push) Blocked by required conditions
Backend Unit Tests / Tests: @librechat/api (shard 4/4) (push) Blocked by required conditions
Backend Unit Tests / backend (push) Blocked by required conditions
Codegraph E2E Vote Gate / Gate (push) Waiting to run
Codegraph E2E Votes / vote (shard 1/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 10/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 2/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 3/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 4/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 5/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 6/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 7/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 8/10) (push) Waiting to run
Codegraph E2E Votes / vote (shard 9/10) (push) Waiting to run
Docker Dev Branch Images Build / publish (push) Waiting to run
Playwright E2E Tests / Codegraph select (push) Waiting to run
Playwright E2E Tests / e2e () (push) Blocked by required conditions
Playwright E2E Tests / MCP list_changed (replica count 1) (push) Blocked by required conditions
Playwright E2E Tests / MCP list_changed (replica count 2) (push) Blocked by required conditions
Playwright E2E Tests / MCP Apps (browser and server) (push) Waiting to run
Playwright E2E Tests / e2e (push) Blocked by required conditions
* 🚪 fix: Refuse Interactive MCP Sign-in on Remote Agent API Runs

A run started through the remote agent API (API key or OIDC bearer) has no
signed-in browser reading its response. When one of the agent's MCP servers
needed OAuth, the run still published LibreChat's sign-in prompt into the
OpenAI-compatible response and waited up to two minutes for a sign-in the
caller could not complete.

The remote auth middleware now marks the response it admits. The prompt
emitters refuse to write to a marked response, and tool loading skips the
turn-start wait when no reader exists. Background Responses keep their
prompts: those go to the generation stream the owner follows in LibreChat.

* 🧭 refactor: Pass the Unattended Fact Explicitly and Release Unattended Callers From Shared Sign-in

Review feedback on the first commit:

- The response registry coupled the auth middleware to MCP through module
  state. The remote controllers now supply `unattended` as an argument
  (chat completions always; Responses through the runtime's tool context,
  foreground only) and it is passed through tool loading to the manager and
  the prompt transports. The registry and the middleware side effect are gone.

- A remote run that reached a server while its owner had a sign-in open in a
  browser joined that recovery and waited for the person. The manager now
  guards an unattended caller at its two entry points: the first sign-in
  prompt, from the caller's own flow or from a recovery it waits on, ends that
  caller's wait with a typed error and leaves a shared recovery running for
  its other waiters. A recovery announces a sign-in request so waiters that
  registered no prompt handler are released too.

* 🧪 test: Cover Unattended Sign-in Through the Real MCP SDK

The shared-sign-in tests replaced the production OAuth handler with a
synthetic listener, so they did not exercise the SDK lifecycle whose
cancellation and shared-recovery behaviour the change depends on.

They now run against the real Streamable HTTP test server, the real
connection factory handler and the real flow manager: an unattended tool
call alone, alongside the owner's open sign-in, joining a recovery that
then stops being silent, recovering through a silent refresh, and opening
a connection that needs sign-in. The synthetic-handler versions are removed.
2026-11-11 20:56:17 -05:00
lia-by-librechat[bot]
d434417089
🦠 chore: Upgrade Node.js and Undici to Security Releases (#18066)
* 🦠 chore: Upgrade Node.js and Undici to Security Releases

* test: Wait for Restored Composer Readiness and Reuse Wrapping Config

---------

Co-authored-by: Lia <lia@librechat.ai>
2026-11-11 19:17:04 -05:00
lia-by-librechat[bot]
79e209030c
🦂 feat: Add GPT-6 Cyber Support (#18023)
* 🦂 feat: Add GPT-6 Cyber Support

* fix: Isolate Cyber Summaries and Account for Cache TTLs

* fix: Complete Cyber Cache Accounting With Agents 4.2.2

* test: Use the Typed SDK AI Message Guard

* test: Narrow SDK Callback Messages Safely

* fix: Shape Cyber Summary Targets With Authenticated Identity

* test: Type Summary SDK Fixtures Consistently

* fix: Enforce Cyber Identity After Final Summary Merging

* fix: Resolve SDK URL Defaults Before Cyber Shaping

* fix: Preserve Cyber Summary Endpoint Routing Policy

---------

Co-authored-by: Lia <lia@librechat.ai>
2026-11-11 16:50:26 -05:00
Danny Avila
5ca49b5f4e
🪢 fix: Resolve the Races Behind Four Intermittent Session and Scenario E2E Tests (#18061)
* 🔑 fix: Replay a Request Rejected for a Superseded Bearer Instead of Refreshing Again

A burst of requests leaves with one bearer. The first 401 starts a refresh and the
rest share it only while it is in flight: a 401 delivered after the refresh settled
found no recovery running and started a second one, although the session had already
recovered and the response described a bearer that was no longer in use.

Compare the bearer the rejected request carried with the current one. When it has
been replaced and no recovery is running, replay the request with the current
bearer. A replay that is rejected again carries the current bearer, so it takes the
ordinary refresh path. The fetch transport follows the same rule.

This is what failed "recovers from an expired bearer during app bootstrap without
redirect looping": 9 of the 21 bootstrap 401s were delivered after the first
recovery finished, so the test counted a third refresh and a second recovery cycle.

* 🔊 test: Play Decodable Audio and Hold the Reply's Button in the Read-Aloud Replay Scenario

The fixture answered the speech request with four bytes the MP3 parser rejects, so
every playback failed. A failed playback cancels its request, and the audio is
cached only once the response has been read to the end, so the replay was served
from memory only when the response finished before the decoder gave up. When the
decoder won, the replay issued the second request the scenario forbids.

The test also located the button by its name. While a message is read aloud its
button is named "Stop", so the locator resolved to the user message's read-aloud
button: the wait for playback to end passed at once, and the second click could
land on a different message.

Serve a third of a second of silent MPEG frames so playback succeeds and ends on
its own, and locate the reply's button by its test id so the wait and the replay
address the same control.

* 📅 test: Wait for the Schedule Save to Land Before Reloading

The edit scenario clicked Save and reloaded the page in the next step. A reload
discards requests still in flight, so when it won the race the PATCH was cancelled
before the server answered and the edited schedule never appeared. Await the PATCH
response, and require it to succeed, before reloading.

* 🔗 fix: Grant a Legacy Shared Link's Permissions Once When Its First Views Race

The share page requests a link's config and its messages together, and each request
migrates a legacy link on the way in. Both find no grant and both write one. The
grant is an upsert matched on the principal and resource, which no unique index
covers, so the two writes inserted two rows: a second public entry, a second owner
entry, or both.

`grantPermission` now accepts the `_id` to give the entry if the grant creates it.
The migration derives that id from the link and the principal, so the second insert
collides on `_id` and is replayed as an update of the first entry. It holds across
processes because the database enforces it. Grants that pass no id are unchanged.

"manages a shared-link snapshot and preserves legacy public links through runtime
migration" asserts one public entry and saw two.

* 🔑 fix: Refresh When a Replayed Fetch Is Rejected With the Current Bearer

The fetch transport replayed a request whose bearer had been superseded and
returned whatever came back. A second 401 there means the current bearer is not
accepted either, which is the case the refresh exists for, and the axios path
already handles it that way. Replay first, then fall through to the ordinary
recovery when the replay is rejected too.

* 🔗 refactor: Derive a Unique Grant's Entry Id in the Data Layer

`AccessControlService.grantPermission` took the entry's `_id` as a Mongoose
`ObjectId`, which put a storage type in an exported `packages/api` signature. The
service now takes `uniqueEntry: true`, and `grantPermission` in data-schemas
derives the id from the principal and resource it already matches on. A caller can
no longer pass an id that names a different grant.
2026-11-11 16:22:39 -05:00
lia-by-librechat[bot]
1ef7d244b5
🌄 fix: Show Skill Pills When a Turn Starts (#18036)
Co-authored-by: Lia <lia@librechat.ai>
2026-11-11 12:49:50 -05:00
Danny Avila
6c479ef244
🏧 fix: Initialize Debit-Created Balances With Configured Allowances (#18056)
* fix: initialize debit-created balances from configured allowances

* style: sort balance initialization imports
2026-11-11 12:49:34 -05:00
lia-by-librechat[bot]
4da2b9d2a3
🪚 refactor: Separate Checkpoint Storage From Graph Runtime (#18029)
* refactor: Separate Checkpoint Storage From Graph Runtime

* fix: Preserve Checkpoint Index Retry Guard

* test: initialize checkpoint identity within test lifecycle

* test: Register Persistence Boot Spec With Source Guards

---------

Co-authored-by: Lia <lia@librechat.ai>
2026-11-11 12:49:10 -05:00
lia-by-librechat[bot]
42219ec8e9
🚜 feat: Support Native PostgreSQL Tool Favorites (#18032)
* 🚜 feat: Support Native PostgreSQL Tool Favorites

* fix: Guard PostgreSQL Reconciliation and Connection Leases

* fix: Scope Favorites Erasure Fences to Deletion Attempts

* fix: Preserve Account Erasure Ownership Until Cancellation Completes

* fix: Reject Unsupported PostgreSQL Command Flags Before Connecting

* fix: Keep Command Validation Compatible With the TypeScript Target

* fix: Keep Migration Previews Read-Only and Preserve Erasure Recovery Identity

* fix: Fence Erasure Recovery Across Tenant and Ownership Changes

* fix: Isolate Migration Dependencies and Keep Mongo Scans Outside Transactions

* fix: Inject PostgreSQL Backend Factories at Composition Roots

* ci: Shard Complete Mutation Work Without Relaxing the Aggregate Gate

---------

Co-authored-by: Lia <lia@librechat.ai>
2026-11-11 12:07:07 -05:00
lia-by-librechat[bot]
dbe9f16a20
🖨️ feat: Add OpenTelemetry Tool Execution Logs (#18035)
Co-authored-by: Lia <lia@librechat.ai>
2026-11-11 12:06:56 -05:00
Dustin Healy
21c286346b
🔗 fix: Update Slack Account Linking in Place (#18039)
* fix: Advance Slack Account Linking in Place

* fix: Narrow Slack Reply Transport Contract

* fix: Make Slack Link Reply Updates Monotonic

* fix: Clear Invalidated Slack Link Cards After Delayed Writes
2026-11-10 21:04:12 -08:00
Dustin Healy
9bdf0bf334
✨ feat: Polish Slack App and Agent Setup (#17982)
* ✨ feat: Polish Slack App and Agent Setup

* 🐛 fix: Restore Slack Search Retry and Align Browser Coverage

* 🐛 fix: Preserve Slack Manager Search and Connection Reactivation
2026-11-10 21:04:12 -08:00
Dustin Healy
67fd560fac
🔐 feat: Add Admin-Assigned Slack Bot Managers (#17836)
* feat: add admin-assigned Slack bot managers

* fix: align revoked bot access messaging with manager grants

* chore: refresh pull request synchronization

* fix: authorize Slack bot manager search through workspace capabilities

* fix: preserve administrator authority during bot grant changes

* test: Observe and Drain Concurrent Fixture Work
2026-11-10 21:04:12 -08:00
Dustin Healy
3e19ef42fe
👥 fix: Let Members Connect Agents to Slack Workspaces (#17835)
* fix: allow members to connect agents to installed Slack workspaces

* fix: clarify Slack destination assignment actions

* fix: align Slack assignment status with destination heading

* fix: explain Slack agent assignments in terms of the connected bot

* fix: separate Slack connection setup, management and confirmation

* fix: name replaced agents only when the member can view them

* perf: avoid redundant Slack assignment identity lookups
2026-11-10 21:04:11 -08:00
Dustin Healy
567aeefe93
🧹 fix: Remove Disconnected Slack Workspaces (#17834)
* fix: Allow Admins to Remove Disconnected Slack Workspaces

* fix: Use Workspace Status Chips and One Confirmation Action

* fix: Confirm Workspace Removal in a Stacked Dialog

* fix: Align Confirmation Cancel Action to the Left
2026-11-10 21:04:11 -08:00
Dustin Healy
fdf75e0174
🔧 fix: Fence Channel Startup and Transaction Capability (#17831)
* 🔧 fix: Fence Channel Startup and Transaction Capability

* 🔧 fix: Gate Clustered Workers Until Startup Completes
2026-11-10 21:04:10 -08:00
Dustin Healy
1f27f5848a
📦 feat: Package Shared Slack Workspace Deployments (#17815)
* feat: Package Shared Slack Workspace Deployments

* fix: Require Explicit Shared Slack Deployment Prerequisites

* fix: Validate Public Slack Deployment Origins

* fix: Keep Shared Slack App Setup in Organization Administration

* 🔧 fix: Validate Shared Gateway Deployment Prerequisites
2026-11-10 21:04:10 -08:00
Dustin Healy
cd4652279c
🌐 feat: Connect Organization Slack Workspaces to Agents (#17811)
* feat: Route shared Slack installations through durable channel workers

* fix: Retain workspace metadata projection after helper cleanup

* fix: Honor configured proxy for Slack credential verification

* feat: Complete Shared Slack Workspace Setup and Routing

* fix: Integrate Shared Routing Retirement and Helm Startup

* fix: Cache Gateway Preparation and Recover OAuth Notifications

* fix: Route Organization-Owned Slack Apps Through the Shared Gateway

* 🔒 fix: Close Shared Slack Lifecycle and Retry Boundaries

* test: Isolate Channel Policy Route From Workspace Startup
2026-11-10 21:04:10 -08:00
Dustin Healy
f5ac244781
🔌 feat: Add Tenant-Owned Slack Installation Storage and OAuth (#17810)
* 🔌 feat: Connect Organization Slack Workspaces

* 🔒 fix: Protect Deployment Slack App Configuration

* fix: Make Slack install callbacks terminal and defer setup UI

* fix: Store Organization-Owned Slack App Credentials

* 🔒 fix: Recheck Slack Installation Authority at Callback Boundaries
2026-11-10 21:04:09 -08:00
Dustin Healy
0b1185b214
🐳 feat: Add Optional Transactional Gateway Docker Setup (#17776)
* feat: add optional transactional gateway Docker setup

* docs: move channel gateway guide to documentation site
2026-11-10 21:04:08 -08:00
Dustin Healy
b83bcdc572
🗄️ fix: Restore Transaction Capability Detection (#17735)
* fix: restore transaction capability detection

* fix: keep authorization and response reads on the primary
2026-11-10 21:04:07 -08:00
Dustin Healy
f70aff8420
🧹 refactor: Consolidate Channel and Response Contracts (#17705)
* refactor: consolidate unreleased channel and response contracts

* test: align gateway process smoke with current bundle

* fix: retain dispatch acknowledgement identity across pauses

* test: align remaining fixtures with initial channel contracts

* test: align admin integration fixture lifecycles
2026-11-10 21:04:06 -08:00
Dustin Healy
4398b61950
🚀 feat: Run the Standalone Slack Channel Gateway (#17618)
* 🚀 feat: Run the Standalone Slack Channel Gateway

* fix: Preserve Gateway Recovery and Optional Delivery Boundaries

* Document Verified Channel Delivery Reconciliation

* test: Expect Transport Credential Rejection Before Execution

* fix: Bind Gateway Runtime to Authoritative Channel Policy

* fix: Share Truthful Gateway Readiness Across Probes

* docs: Describe Runtime Bundle and Adapter Boundaries

* fix: Pin Runtime Readiness to the Socket App Binding

* fix: supervise gateway socket reconnect and shutdown

* fix: pass server delivery budget to gateway worker

* fix: bind Socket hello authority to the current handshake

* refactor: use client-owned branding in gateway review adapter
2026-11-10 21:04:06 -08:00
Dustin Healy
b422b6802b
🎨 feat: Render Slack Replies and Private Review Controls (#17617)
* 🎨 feat: Render Slack Replies and Private Review Controls

* fix: Preserve Literal Content and Bound Gateway Review Views

* test: Use Shared Gateway Policy in Interaction Fixtures

* docs: Make Native Adapter Runtime Dependency Explicit

* fix: align Slack presentation with delivery and review contracts

* test: retain narrowed question across modal fixture callback

* fix: centralize bounded Slack presentation and identity outcomes

* fix: preserve frozen v5 content across renderer upgrade

* fix: validate every Slack presentation fallback consistently

* fix: preserve source atom identity through Slack formatting

* Use the shared GFM grammar for Slack presentation

* test: Resolve State Colours From Theme Roles
2026-11-10 21:04:05 -08:00
Dustin Healy
5081850280
🛠️ feat: Add Slack Gateway Transport Adapters (#17616)
* 🛠️ feat: Add Slack Gateway Transport Adapters

* fix: Share Gateway Execution Wire Contracts and Preserve Stop Scope

* fix: Align Gateway Transport and Installation Contracts

* fix: Centralize Gateway Policy and Durable Stop Observations

* docs: Clarify Transport Adapter and Runtime Ownership

* fix: Separate Stop Event Identity From Execution Authority

* build: align gateway lock with current workspace toolchain

* 🛠️ fix: Cache Gateway Dependencies Across Shared CI Jobs
2026-11-10 21:04:05 -08:00
Dustin Healy
0c6c223cdd
⏯️ feat: Review and Stop Background Responses (#17613)
* ⏯️ feat: Review and Stop Background Responses

* fix(responses): activate browser review with its owner page

* fix: Preserve Queued Responses Across Interactive Activation

* fix: Use Shared Lifecycle For Owner Review Submission

* fix: Own Interactive Response Composition and Absolute Deadlines
2026-11-10 21:04:04 -08:00
Dustin Healy
8596615d1d
🌐 feat: Wire Responses and Channel Lifecycle APIs (#17611)
* 🌐 feat: Wire Responses and Channel Lifecycle APIs

* fix: Align Channel Application Policy and Source Authority

* fix: Preserve Configured App Budgets in Canonical Response Commits

* Expose Fenced Channel Receipt Reconciliation Routes

* fix: Keep Ordinary Chat Capture In Its Existing Owner

* fix(channels): scope worker authority and defer browser activation

* fix(responses): gate admission on canonical queue readiness

* fix: Recover Durable Response Dispatch Across Queue Shutdown

* fix: Preserve Upstream Endpoint Config Insertions

* test: Align Channel Runtime Configuration Contract
2026-11-10 21:04:03 -08:00
Dustin Healy
9f975970de
👍 feat: Record Feedback on Delivered Channel Responses (#17610)
* 👍 feat: Record Feedback on Delivered Channel Responses

* fix: Fence Channel Feedback Persistence and Export Ownership

* fix: align feedback storage with database and cleanup contracts

* Require Shared Server-Authored Provenance for Channel Feedback

* Recover Channel Feedback Initialization After Failed Startup

* Own Channel Feedback Retention and Retry Lifecycle

* Rotate Deferred Feedback Recovery Fairly

* fix: Preserve Feedback Trace Provenance And Receipt Checkpoints

* test: Observe and Drain Concurrent Fixture Work
2026-11-10 21:04:02 -08:00
Dustin Healy
c907dbf346
📨 feat: Coordinate Channel Delivery Through Responses (#17609)
* 📨 feat: Coordinate Channel Delivery Through Responses

* fix: Enforce Channel Credential Retirement and Live Trace Delivery

* test: derive artifact policy fixtures from validated schema

* Enforce Current Channel Credentials and Recover Worker Initialization

* Complete Channel Capability and Durable Reconciliation Boundaries
2026-11-10 21:04:02 -08:00
Dustin Healy
aae13f6817
📎 feat: Resolve Channel Attachments and Usage Summaries (#17608)
* 📎 feat: Resolve Channel Attachments and Usage Summaries

* fix: Bound Response Artifact Catalogs and Reauthorize Trace Disclosure

* fix: unify channel artifact budgets and generated provenance
2026-11-10 21:04:02 -08:00
Dustin Healy
7593a5c14a
🔗 feat: Configure Channels and Link Participant Accounts (#17607)
* 🔗 feat: Configure Channels and Link Participant Accounts

* fix: centralize channel eligibility and consent lifecycle

* test: preserve account erasure privacy across cleanup retries

* test: Observe and Drain Concurrent Fixture Work
2026-11-10 21:04:01 -08:00
Dustin Healy
59f54d982f
🧩 feat: Compose the Background Responses Host (#17606)
* 🧩 feat: Compose the Background Responses Host

* fix: reconcile background response host boundaries

* test: Exercise Canonical Response Input History Through HTTP

* fix: Keep Background Retrieval Journal-Owned

* test: load compiled response host before timed assertions
2026-11-10 21:04:01 -08:00