* feat: Add Gemini Hydrogen Model Support
* fix: Restore Google History For Reachable Agents
* fix: Preserve Mixed Google Signature History
* refactor: Inject Google billing configuration at application boundary
* fix: Preserve Call Signatures From Unsupported Google Output
* chore: Use Released Agents SDK 4.2.5
---------
Co-authored-by: Lia <lia@librechat.ai>
* 🧽 fix: Replace an Abandoned Summary Attempt's Text When Its Retry Streams
Summary deltas append to the in-flight summary part. Once the agents SDK
streams them while the provider is still responding, an attempt that is
then abandoned (a retry, a fallback provider) has already put text in the
part, and the next attempt's deltas would follow it until the completion
event replaced the lot.
A delta may now carry `reset`: the part's content is replaced instead of
extended, and a reset with no content empties it. The part keeps its slot
and stays in flight. Deltas without the field behave as before, so this
is inert until the SDK sends it.
* 🦿 chore: Bump Agents SDK to 4.2.3
4.2.3 dispatches each summary delta while the provider is still responding
and marks the first delta after an abandoned attempt `reset`, which the
chat reducer now honors. It also stops sending reasoning as summary text,
which is where the `incoming.content is not iterable` handler errors
during compaction came from.
The release changed only the SDK's own dev dependencies and overrides, so
the lockfile moves the package's version, URL and integrity and nothing
else.
* 🦠 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>
* chore: Update package dependencies across multiple modules
- Upgraded `@azure/identity` to version 4.14.0 in package.json files.
- Updated `multer` to version 2.5.0 and `nodemailer` to version 10.2.1.
- Incremented `undici` to version 7.30.1.
- Updated `@happy-dom/jest-environment` to version 21.0.4.
- Incremented `qs` to version 6.16.1 and `fast-uri` to version 3.1.9.
- Updated `serialize-javascript` to version 7.1.4.
- Updated `zod` to version 4.6.7 in multiple modules.
These updates ensure compatibility with the latest features and security improvements.
* chore: update bun.lock file
* chore: Update dompurify to version 3.4.17 across all package files
- Bumped dompurify version from 3.4.16 to 3.4.17 in package.json, package-lock.json, and relevant sub-packages.
- Ensured consistency in dependency versions across the project.
* chore: Update ip-address package to version 10.7.4 in package.json and package-lock.json
- Bumped ip-address version from 10.5.1 to 10.7.4 in package.json.
- Updated package-lock.json to reflect the new version and integrity hash.
* 🔧 chore: Update sanitize-html and related dependencies in package-lock.json and package.json
- Upgrade sanitize-html from ^2.17.7 to ^2.18.1 across multiple package.json files.
- Update dayjs from 1.11.21 to 1.11.23 in package-lock.json.
- Upgrade is-plain-object from 5.0.0 to 5.1.0 in package-lock.json.
- Upgrade launder from 1.7.1 to 1.7.2 in package-lock.json.
- Update postcss from ^8.3.11 to ^8.5.27 in package-lock.json.
* 🔧 chore: Upgrade mongodb-memory-server to version 11.3.0 across package-lock.json and multiple package.json files
- Update mongodb-memory-server from ^11.0.1 to ^11.3.0 in package-lock.json.
- Reflect the same version change in api/package.json and packages/data-schemas/package.json.
* 🔧 chore: Upgrade hono to version 4.13.13 in package.json and package-lock.json
- Update hono from ^4.13.7 to ^4.13.13 in package.json.
- Reflect the same version change in package-lock.json.
* 🔧 chore: Upgrade follow-redirects to version 1.16.1 in package-lock.json
- Update follow-redirects from 1.16.0 to 1.16.1 in package-lock.json.
* 🧵 test: Cover Harmony Headers in Text Attachments Sent to OpenAI Models on Bedrock
A pasted text/plain attachment is sent inline as file context, so a harmony header such as `<|channel|>analysis` inside it reaches every later turn. OpenAI models on Bedrock answer that request with an event stream that closes before any event, which crashed the turn in @librechat/agents 4.0.4 with `Cannot use 'in' operator to search for 'tool_calls' in undefined`.
Drive LibreChat's own file-context formatting through the SDK's Bedrock model with a recorded response and assert the header reaches an OpenAI model neutralized and other model families unchanged.
* 📦 chore: Bump @librechat/agents to v4.0.5
* 📦 chore: Regenerate the Lockfile with npm 11 to Keep libc Constraints
Bump @modelcontextprotocol/sdk from ^1.30.0 to ^1.32.1 in api and
packages/api. 1.31.0 binds stored OAuth credentials to the issuing
authorization server; LibreChat does not use the affected auth()/
authProvider path and already pins refreshes to the stored token endpoint.
1.32.0 makes the client transports follow same-origin redirects
themselves, which would re-issue requests the connection fetch declined
(hop cap, reauthorized tools/call). Set redirectPolicy: 'follow' so
redirects stay with the connection fetch, and cover both transports with
real-SDK tests.
Update package repository and bugs URLs, GitHub links in docs, templates and comments, and image references (compose files, deployed-update, Helm values and renovate hints) from danny-avila to LibreChat-AI / librechat-ai. Covers the rag-api repository and its images, which moved to the organization. Sponsor links and the sealed star-history chart are unchanged.
* 🔌 feat: OpenAPI spec and docs for the public Agents API
* 🔧 fix: address review on Agents API OpenAPI spec and docs:
- adapter: mark JSON request bodies as required
- openapi.js: move gate, config read and spec serving into packages/api
as an injected router factory; leave /api as wiring only
- docs: compute URLs in-browser and use a relative servers url so docs
work under a base path (e.g. /chat)
- build: copy the generated spec into dist so the multi-stage image ships it
- agents: reuse the enforced list envelope for the docs so the AgentList
schema cannot drift from the runtime cursor and strictness
* 🔧 fix: align Agents API OpenAPI contract with enforced runtime
Second review round on the public Agents API spec. Three cases where the
published contract described something the server does not do, so generated
clients would fail against the live API:
- Upload form: document the `purpose` field (enum: file_search, execute_code,
context) that POST /agents/{id}/files actually requires, instead of the
internal-only `tool_resource`; requests following the old form were rejected
with 400 because `purpose` was absent.
- Auth: drop the `apiKeyBearer` scheme from the management and skill endpoints.
They gate on OIDC/M2M via requireAgentManagementAuth and deliberately reject
the API-key fallback; the API key belongs to the out-of-scope
OpenAI-compatible endpoints and returns when those are documented.
- Skill update: document the 409 conflict PATCH /skills/{id} returns on a stale
expectedVersion. The agent update path collapses its internal 409 to 400, so
it correctly keeps no 409.
* 🔧 fix: serve docs on experimental server and document the 401
Third review round on the public Agents API spec.
- Experimental server: mount routes.openapi in api/server/experimental.js before its /api 404 handler. Without it, npm run backend:experimental returns 404 for /api/docs and /api/openapi.json even when openapi.enabled is true, because that server never mounted the router.
- Auth failure: document the 401 that requireAgentManagementAuth returns on a missing, expired, malformed, or unbound token. Its body is { "error": "Unauthorized" }, a flatter shape than the management error schema, so add a dedicated UnauthorizedError schema and a shared 401 response to the agent and skill contracts rather than reusing the standard error schema.
* 🔧 fix: document skill-update, auth-conflict, upload-limit, and watch-copy gaps
* 🔧 fix: added error shapes for permission denied and internal server errors in API responses docs
* fix: cover the auth-layer 500 shape and pin the account-deletion code
* fix: update OpenApiRouterDeps documentation and simplify request handling in isEnabled function
* 🔧 fix: gate the Swagger asset mount behind the OpenAPI toggle
* 🔧 fix: accept the malformed-JSON 400 envelope in the contract
* fix: accept the tenant-isolation 403 envelope in the contract
* fix: add description for content property in SkillFileUpdateRequest to clarify byte limit
* feat: add run-scoped file sharing for subagents
Delegate current-message files through authorized execution catalogs and publish selected immutable code-output versions through the existing file pipeline.
Requires the companion agents SDK context adapter before the dependency can be released and pinned.
* fix: preserve child tool artifacts and verify file-sharing lifecycle
Keep citations and other non-sandbox artifacts on their existing delivery path while retaining private code outputs and inspected images until publication.
Cover native and text delivery, nested and sibling authorization, concurrent runs, cancellation cleanup, and checkpoint recovery through the browser harness.
* test: align file-sharing fixtures and integration cleanup
* test: repair LibreOffice conversion fixtures
* test: verify deployment skill bytes across checkout formats
* fix: align subagent file budgets and refresh boundaries
* chore: update agents SDK to 3.8.6
* refactor: move code output processing into API workspace
* fix: enforce shared file budgets for parents and teams
* fix: declare the shared file encoder interface
* chore: bump agents sdk to v3.8.5
* chore: bump nodemailer to v10.0.1
* chore: bump sharp to v0.35.4
* chore: bump js-yaml to v4.3.2
* chore: bump hono to v4.13.7 and @hono/node-server to v2.1.1
* 🗜️ feat: Manual Context Compaction as a Summarize-Only Turn
Adds a user-triggered "Compact context" action that summarizes the active
branch on demand. The compaction is an ordinary agent turn: the client
submits it through the normal chat pipeline with `compact: true`, the
controller hangs it off the branch's leaf instead of creating a user
message, and the agent client runs the graph summarize-only (the SDK's new
`summarizeOnly` input), so the summary streams into the response
placeholder under the leaf exactly like the automatic detour's and is
persisted as the boundary every later turn starts from.
Nothing new is needed for job registration, billing, abort, persistence,
or the usage snapshot: the run emits the same summary step and post-summary
context snapshot the automatic path already emits, and the response message
carries the summary part plus the `summaryUsedTokens` baseline the gauge
reads. The controller validates the request (existing conversation, a real
leaf, summarization enabled, no edit/regenerate/continue combination) and
answers 409 when the leaf is already a bare summary.
Client-side the submission borrows the regenerate shape — no new user
bubble, the placeholder parents onto the leaf — while the wire payload
drops `isRegenerate` so the server never treats it as a regenerated user
turn. The action sits in the context-usage popover, gated by the same
`summarization.enabled` switch as the automatic detour.
* 🗜️ fix: Localize a Compaction That Cannot Run
A compaction the graph could not attempt (summarization disabled, the
instructions already exceeding the budget, or an explicit recency window
covering the whole conversation) rejects with the SDK's
`ManualSummarizationSkippedError`, which rendered as the generic admin
error. It now maps to a typed `compaction_skipped` payload with the reason,
and a run that ends with neither a summary nor a recorded error fails as
`compaction_failed`; the Error component localizes both. A run that already
recorded why it stopped keeps that error part instead of failing twice.
* 🗜️ fix: Anchor a Compaction on the Leaf Everywhere It Is Read
Review round 1.
- The client sent the leaf's parent as `parentMessageId`, which the
controller treats as the anchor, so the summary would have skipped the
latest reply and landed as its sibling. The leaf's own id is now both the
placeholder's parent and the server-side anchor.
- A compaction has no user message of its own, and every consumer of the
job's user-message slot now knows it: the error path parents its row on
the loaded anchor and never upserts the leaf, and the job records the
regenerate shape so a reconnecting client rebuilds the turn under the
leaf instead of recreating it as a user message.
- The controller no longer reads the anchor before the branch is loaded;
`BaseClient` validates it against the history it loads anyway and
answers 404 for a missing leaf or a typed `nothing_to_summarize` for a
finished compaction. That predicate is shared through the data provider
and ignores a summary still streaming or one that failed, so an
interrupted compaction can be retried.
- A compaction never consumes files staged in the composer, the action is
shown only when the server advertises `compactionEnabled`, and the
in-flight marker is feature-local Jotai state rather than a read of the
Recoil submission store.
* 🗜️ fix: Keep a Compaction Turn to Its Summary
Review round 2, plus the class it belongs to. A compaction submits no user
turn, so nothing that keys off one may run: the memory pass no longer runs
over the history (it would have spent a model call and could repeat memory
writes), and skill primes are no longer injected into the transcript the
run is about to summarize.
The client's in-flight marker is also reconciled on mount: a compaction
that finished while the view was away left the marker set, and the next
ordinary turn in that conversation would have shown as compacting.
* 🧹 chore: Sort Imports in the Compaction Hook Spec
* 🔧 chore: Update @librechat/agents dependency to version 3.8.1 in package-lock.json and package.json files
* 🪪 feat: Configurable Langfuse Trace User Identity and Metadata
* 🪪 fix: Prefer createRun's conversationId and warn once on an unset userIdField
* 🪪 fix: Validate Langfuse trace field names at the point of use
* 🧹 chore: Sort identity imports
* 🪪 fix: Source the trace model label from the initializer, not a prompt-affecting option
* 🧪 fix: Build the trace context without a prototype so partial client contexts resume
* 📦 chore: Bump `@librechat/agents` to v3.8.0 for the Langfuse trace userId override