* 🧪 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> |
||
|---|---|---|
| .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.