|
Some checks are pending
Backend Unit Tests / Build packages (push) Waiting to run
Backend Unit Tests / Codegraph select (push) Waiting to run
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
Codegraph E2E Votes / vote (full suite) (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/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
Sync Locize Translations & Create Translation PR / Sync Translation Keys with Locize (push) Waiting to run
Sync Locize Translations & Create Translation PR / Create Translation PR on Version Published (push) Blocked by required conditions
* fix: route Azure Astra through Responses API * fix: keep Azure Astra deployment alias out of summarizer overrides The Azure deployment alias in `modelKwargs.model` is spread after `model` by langchain, so the SDK's same-provider summarizer, which copies the agent's client options and overrides only `model`, still reached the Astra deployment when configured with a different model. Hand the summarizer the agent's kwargs without the alias whenever its model differs. Also derive the Astra routing decision once, reuse the first-party OpenAI predicate in the GPT-5.6 rule, pin the opt-out shape in the Azure spec, and expect `firstPartyEndpoint` for canonical Azure hosts in the backward-compat spec. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * fix: resolve Azure request URLs and summarizer deployments * fix: honor explicit OpenAI summarization for Azure agents * 🧭 fix: Degrade Unresolvable Azure Summarizers Without Failing the Run Summarization target resolution for Azure agents threw inside createRun, so a summarization setting that could not be resolved failed every agent run before any model call, not just compaction. The documented `summarization.provider: openAI` block with the `.env.example` default `OPENAI_API_KEY=user_provided` broke all Azure agents, and a summary model missing from the Azure configuration did the same. - An explicit OpenAI summarizer without server credentials now disables summarization for that Azure agent with a one-time warning instead of throwing; the agent's own client is not a fallback because Azure Responses shares the `openAI` provider. - A summary model the Azure configuration cannot resolve warns once and keeps the agent's client, as before this branch. - A summary group without a base URL no longer inherits the agent group's `azureOpenAIBasePath`, which sent the summary key and deployment to the agent's resource. - Serverless summary groups without a version send no empty `api-version`. * 🧪 test: Assert No Summary Request Leaves a Disabled OpenAI Summarizer * 🧯 fix: Disable Summaries Whose Azure Deployment Cannot Be Resolved When the Azure configuration could not resolve a summary model, the summarizer fell back to the agent's own client. On an Azure Responses agent that stripped the deployment alias and sent the logical model name where Azure expects a deployment, so every compaction failed; on a chat agent the URL-pinned deployment silently served a different model than the one configured. An unresolvable Azure summary target now disables summarization for that agent with a one-time warning, matching the unreachable OpenAI target: the run proceeds on context pruning and no summary request is sent. * 🔑 fix: Treat an Empty Azure Summary Key as Unavailable `azureBaseSchema` accepts `apiKey: ''`, and `mapModelToAzureConfig` passes it through, so a summary group with an empty key kept summarization enabled and built a client with no credential. The agent flow already rejects an empty Azure key during initialization; the summary resolver now disables summarization for that target with the same one-time warning as a user-provided key or base URL. * 🧭 fix: Resolve Azure Summaries From Every Supported Azure Configuration Three Azure configuration shapes the summary resolver and URL builders did not cover: - Legacy `AZURE_*` environment credentials: without an `azureOpenAI` block the resolver skipped Azure, so an Astra agent's summarizer reused the agent's Responses client and sent the logical summary model where a deployment belongs. The target now resolves from the environment the way `initializeOpenAI` does (including `AZURE_USE_MODEL_AS_DEPLOYMENT_NAME`) and is disabled when those credentials are user-provided or missing. - `summarization.parameters` `baseURL` and `apiKey` overrides now apply to Azure summary targets, as they already did for explicit OpenAI targets, through one shared helper. - A full Azure hostname used as the instance name (as `genAzureEndpoint` accepts) is used as the host for both the default Responses URL and the chat deployments path, instead of being suffixed into `<host>.openai.azure.com`. * 🔐 fix: Expand Summarizer Credential Placeholders and Bound Warnings Admin-authored `summarization.parameters` `apiKey` and `baseURL` values were forwarded verbatim, so `${SUMMARY_KEY}` reached the client as a literal key while Azure groups and custom endpoints expand the same syntax. They are now expanded once through `extractEnvVariable` (keeping its sensitive-variable denylist) before resolution and before the parameters are layered over the client, and a credential or base URL that still holds an unresolved placeholder disables summarization like a missing one. Azure base URL templates (`${INSTANCE_NAME}`, `${DEPLOYMENT_NAME}`) are not treated as unresolved. The one-time warning set is now keyed per tenant, so one tenant's report no longer hides another's, and resets after 256 distinct entries so changing configurations cannot grow it without bound. * 🧩 fix: Keep Azure URL Templates Out of Summarizer Env Expansion Expanding `summarization.parameters.baseURL` through `extractEnvVariable` also replaced Azure's reserved `${INSTANCE_NAME}` and `${DEPLOYMENT_NAME}` templates whenever the host environment happened to define those names, so a template override could route compaction to the host's instance or deployment instead of the summary group's. Expansion now skips those two templates and leaves them for `constructAzureURL`, and the unresolved-placeholder check reads the same segments. The warning deduplication set now evicts the least recently seen entry at its bound instead of clearing, so warnings for problems that are still recurring are not all logged again at once. * 🔀 fix: Reset Inherited API Mode for Custom-Endpoint Summarizers A custom OpenAI-compatible summarization endpoint resolves to the same `openAI` provider as an Azure Responses agent, so the SDK layered its overrides over the agent's client options and kept the agent's `useResponsesApi`, `firstPartyEndpoint`, reasoning and request kwargs. An Azure Astra agent therefore sent its compaction to the gateway's `/responses` with Astra shaping. When the resolved custom provider matches the agent's, those fields are now replaced from the target's own configuration, and explicit summarization parameters can still opt back in. Azure's reserved `${INSTANCE_NAME}`/`${DEPLOYMENT_NAME}` URL templates are now preserved only for Azure summarization targets, so an OpenAI or custom base URL can reference environment variables with those names. * fix: Resolve Azure Summary Identity, Transport, and Token Limits 🧭 * fix: Resolve Headers Before Building Summary Clients 📨 --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> Co-authored-by: Danny Avila <danny@librechat.ai> |
||
|---|---|---|
| .claude/skills | ||
| .devcontainer | ||
| .github | ||
| .husky | ||
| .vscode | ||
| api | ||
| client | ||
| config | ||
| docs | ||
| e2e | ||
| helm | ||
| otel/langfuse-fanout | ||
| packages | ||
| redis-config | ||
| scripts | ||
| search | ||
| skill | ||
| src/tests | ||
| utils | ||
| .codex | ||
| .dockerignore | ||
| .env.example | ||
| .gitattributes | ||
| .gitignore | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierrc | ||
| AGENTS.md | ||
| bun.lock | ||
| CLAUDE.md | ||
| CONTEXT.md | ||
| deploy-compose.langfuse-fanout.yml | ||
| deploy-compose.yml | ||
| docker-compose.langfuse-fanout.yml | ||
| docker-compose.override.yml.example | ||
| docker-compose.yml | ||
| Dockerfile | ||
| Dockerfile.multi | ||
| eslint.config.mjs | ||
| librechat.example.yaml | ||
| LICENSE | ||
| package-lock.json | ||
| package.json | ||
| rag.yml | ||
| README.md | ||
| README.zh.md | ||
| tool-intent-spec.md | ||
| turbo.json | ||
| UPGRADING.md | ||
LibreChat
English · 中文
🚀 What's New in v0.8.8-rc3
- Agent Management API (beta): Create, discover, update, and delete Agents; manage Agent files and Skills; and authenticate machine clients through deployment-bound OIDC identities while preserving existing role and Agent access controls.
- Attached workspaces (highly experimental): Select or save a per-Agent default workspace for each managed or personal code worker, then let Agents inspect trees, read and search files, author changes, and run Bash with bounded timeouts. Personal workers support bounded self-service enrollment, readiness status, and per-Agent Git identity.
- Background tool controls: Optionally cancel ordinary background tools, including attached Bash, while keeping detached Subagent execution independent.
- Code approval controls: Choose Ask, Allow, or Deny for file writes and command execution where administrators permit it, including a Full access mode for trusted attached environments. File Search and Run Code also honor role grants.
- Manual context compaction: Start a summarize-only turn before the context window fills while preserving recent conversation content according to the deployment's summarization policy.
- Context Usage: Inspect dialogue, retained tool traffic, Agent instructions, cache, cost, and runway pressure without double-counting category subsets.
- Unified attachments: Upload once and let LibreChat route content to the model or extracted text, then provision File Search and Code tools only when needed.
- Models: Added GPT-6 Astra for the OpenAI and Agents endpoints, with Responses API routing and tool-call support.
- Agent and chat UI: Unified tool activity, reasoning, search, and Agent workflows; added one draggable Pinned section for chats and favorites, morphing state icons, high-contrast themes, rich-text message copying, clearer sidebar titles, and refined live phase layouts.
- Observability: Export correlated application logs through OpenTelemetry, configure allowlisted Langfuse trace identity and metadata, tag browser diagnostics with client build IDs, and scope Insights to authorized Agents.
- Reliability and security: Strengthened Agent continuation and checkpoint recovery, Redis liveness detection, DocumentDB coordination, OpenID and MCP OAuth sessions, shared-link throttling, tenant isolation, attachment bounds, and upload error handling.
Read the full v0.8.8-rc3 changelog.
✨ Features
-
🖥️ UI & Experience inspired by ChatGPT with enhanced design and features
-
🤖 AI Model Selection:
- Anthropic (Claude), AWS Bedrock, OpenAI, Azure OpenAI, Google, Vertex AI, OpenAI Responses API (incl. Azure)
- Custom Endpoints: Use any OpenAI-compatible API with LibreChat, no proxy required
- Compatible with Local & Remote AI Providers:
- Ollama, AMD Lemonade, groq, Cohere, Mistral AI, Apple MLX, koboldcpp, together.ai,
- OpenRouter, Helicone, Perplexity, ShuttleAI, Deepseek, Qwen, and more
-
- Secure, Sandboxed Execution in Python, Node.js (JS/TS), Go, C/C++, Java, PHP, Rust, and Fortran
- Seamless File Handling: Upload, process, and download files directly
- No Privacy Concerns: Fully isolated and secure execution
- Open-Source & Self-Hostable: powered by ClickHouse/code-interpreter
-
🔦 Agents & Tools Integration:
- LibreChat Agents:
- No-Code Custom Assistants: Build specialized, AI-driven helpers
- Agent Marketplace: Discover and deploy community-built agents
- Collaborative Sharing: Share agents with specific users and groups
- Flexible & Extensible: Use MCP Servers, tools, file search, code execution, and more
- Skills: Create reusable
SKILL.mdinstruction bundles for manual, automatic, or always-on agent workflows - Agent Plugins: Experimentally bundle deployment Skills and MCP servers into startup-loaded packages
- Subagents: Delegate focused work to isolated child agent runs with their own context windows
- Agent Management API: Automate Agent, file, and Skill management with deployment-bound OIDC clients
- Attached Code Workspaces: Let Agents inspect, search, edit, and run commands in managed or personal workspaces (highly experimental)
- Compatible with Custom Endpoints, OpenAI, Azure, Anthropic, AWS Bedrock, Google, Vertex AI, Responses API, and more
- Model Context Protocol (MCP) Support for Tools
- LibreChat Agents:
-
🔍 Web Search:
- Search the internet and retrieve relevant information to enhance your AI context
- Combines search providers, content scrapers, and result rerankers for optimal results
- Customizable Jina Reranking: Configure custom Jina API URLs for reranking services
- Learn More →
-
🪄 Generative UI with Code Artifacts:
- Code Artifacts create React, HTML, and Mermaid content directly in chat
- Open previews fullscreen and export Mermaid diagrams as SVG or PNG
-
🎨 Image Generation & Editing
- Text-to-image and image-to-image with GPT-Image-1
- Text-to-image with DALL-E (3/2), Stable Diffusion, Flux, or any MCP server
- Produce stunning visuals from prompts or refine existing images with a single instruction
-
💾 Presets & Context Management:
- Create, Save, & Share Custom Presets
- Switch between AI Endpoints and Presets mid-chat
- Edit, Resubmit, and Continue Messages with Conversation branching
- Create and share prompts with specific users and groups
- Fork Messages & Conversations for Advanced Context control
- Compact long conversations on demand while preserving recent context
-
💬 Multimodal & File Interactions:
- Upload and analyze images with Claude 3, GPT-4.5, GPT-4o, o1, Llama-Vision, and Gemini 📸
- Chat with Files using Custom Endpoints, OpenAI, Azure, Anthropic, AWS Bedrock, & Google 🗃️
- Copy messages as formatted rich text for documents, email, and collaboration apps
-
🌎 Multilingual UI:
- English, 中文 (简体), 中文 (繁體), العربية, Deutsch, Español, Français, Italiano
- Polski, Português (PT), Português (BR), Русский, 日本語, Svenska, 한국어, Tiếng Việt
- Türkçe, Nederlands, עברית, Català, Čeština, Dansk, Eesti, فارسی
- Suomi, Magyar, Հայերեն, Bahasa Indonesia, ქართული, Latviešu, ไทย, ئۇيغۇرچە
-
🧠 Reasoning UI:
- Dynamic Reasoning UI for Chain-of-Thought/Reasoning AI models like DeepSeek-R1
-
🎨 Customizable Interface:
- Customizable Dropdown & Interface that adapts to both power users and newcomers
- Light, dark, system, and high-contrast appearance modes
-
📈 Observability:
- Export traces and logs with OpenTelemetry and connect Langfuse for Agent and model insights
-
- Never lose a response: AI responses automatically reconnect and resume if your connection drops
- Multi-Tab & Multi-Device Sync: Open the same chat in multiple tabs or pick up on another device
- Production-Ready: Works from single-server setups to horizontally scaled deployments with Redis
-
🗣️ Speech & Audio:
- Chat hands-free with Speech-to-Text and Text-to-Speech
- Automatically send and play Audio
- Supports OpenAI, Azure OpenAI, and Elevenlabs
-
📥 Import & Export Conversations:
- Import Conversations from LibreChat, ChatGPT, Chatbot UI
- Export conversations as screenshots, markdown, text, json
-
🔍 Search & Discovery:
- Search all messages/conversations
-
👥 Multi-User & Secure Access:
- Multi-User, Secure Authentication with OAuth2, LDAP, & Email Login Support
- Built-in Moderation, and Token spend tools
-
🎛️ Admin Panel:
- Browser-based UI to manage users, groups, roles, and configuration overrides
- Edit settings and per-role/group permissions live, without redeploying
- Bundled with the Docker Compose stacks for one-command setup
-
⚙️ Configuration & Deployment:
- Configure Proxy, Reverse Proxy, Docker, & many Deployment options
- Use S3 with CloudFront for stable media links, edge delivery, signed cookies, and secured downloads
- Use completely local or deploy on the cloud
-
📖 Open-Source & Community:
- Completely Open-Source & Built in Public
- Community-driven development, support, and feedback
For a thorough review of our features, see our docs here 📚
🪶 All-In-One AI Conversations with LibreChat
LibreChat is a self-hosted AI chat platform that unifies all major AI providers in a single, privacy-focused interface.
Beyond chat, LibreChat provides AI Agents, Model Context Protocol (MCP) support, Artifacts, Code Interpreter, custom actions, conversation search, and enterprise-ready multi-user authentication.
Open source, actively developed, and built for anyone who values control over their AI infrastructure.
🌐 Resources
GitHub Repo:
- RAG API: github.com/danny-avila/rag_api
- Website: github.com/LibreChat-AI/librechat.ai
Other:
- Website: librechat.ai
- Documentation: librechat.ai/docs
- Blog: librechat.ai/blog
📝 Changelog
Keep up with the latest updates by visiting the releases page and notes:
⚠️ Please consult the changelog for breaking changes before updating.
⭐ Star History
✨ Contributions
Contributions, suggestions, bug reports and fixes are welcome!
For new features, components, or extensions, please open an issue and discuss before sending a PR.
If you'd like to help translate LibreChat into your language, we'd love your contribution! Improving our translations not only makes LibreChat more accessible to users around the world but also enhances the overall user experience. Please check out our Translation Guide.
💖 This project exists in its current state thanks to all the people who contribute
🎉 Special Thanks
We thank Locize for their translation management tools that support multiple languages in LibreChat.