* 🔑 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. |
||
|---|---|---|
| .claude/skills | ||
| .devcontainer | ||
| .github | ||
| .husky | ||
| .oss-scanner | ||
| .vscode | ||
| api | ||
| client | ||
| config | ||
| docs | ||
| e2e | ||
| helm | ||
| otel/langfuse-fanout | ||
| packages | ||
| redis-config | ||
| scripts | ||
| search | ||
| skill | ||
| utils | ||
| vendor/code | ||
| .bun-version | ||
| .codex | ||
| .dockerignore | ||
| .env.example | ||
| .gitattributes | ||
| .gitignore | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| AGENTS.md | ||
| bun.lock | ||
| CONTEXT.md | ||
| deploy-compose.langfuse-fanout.yml | ||
| deploy-compose.yml | ||
| docker-compose.channels-build.yml | ||
| docker-compose.channels.yml | ||
| docker-compose.langfuse-fanout.yml | ||
| docker-compose.mongo-replica.yml | ||
| docker-compose.override.yml.example | ||
| docker-compose.slack-workspaces.yml | ||
| docker-compose.yml | ||
| Dockerfile | ||
| Dockerfile.multi | ||
| eslint-suppressions.json | ||
| eslint.config.mjs | ||
| librechat.example.yaml | ||
| LICENSE | ||
| package-lock.json | ||
| package.json | ||
| prep-stream-dev-restack | ||
| rag.yml | ||
| README.md | ||
| README.zh.md | ||
| tool-intent-spec.md | ||
| turbo.json | ||
| UPGRADING.md | ||
LibreChat
English · 中文
🚀 What's New in v0.8.8
- 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. Public OpenAPI and Swagger UI cover inference, events, Agent management, and Skill management.
- 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 and GPT-6.1 Sol, 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: Inspect ordered model conversations, tool rounds, and costs in the Trace Viewer; 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 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 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/LibreChat-AI/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.