* 🗓️ fix: Refresh the Sidebar When a Scheduled Run Fires or Settles An automatic occurrence is the one generation nothing in the client starts, so no submission, stream or event handler tells the sidebar its chat exists, and the conversation list's five-minute staleness leaves it out of a tab that stays focused. The schedules panel is already polling for its cards, and `lastRun` moves at exactly the two moments the list should be re-read — a fire adds a chat, a settlement retitles and reorders it — so read the refresh out of that poll rather than adding one. Only transitions refresh; a schedule first seen is recorded in silence, so a panel opened long after a run does not refetch a list that has held its chat all along. This also settles the row Run Now seeds: the schedule's own completion is what replaces the schedule name with the generated title. * 🗓️ fix: Name the Running Occurrence's Chat So the Sidebar Can Fetch It Four review rounds each found a new way the schedule projection diverges from the run it stands in for: `lastRun` is not written at fire, `nextRunAt` moves before the conversation exists, and an edit mid-flight fences the terminal write so `lastRun` never changes at settlement. Nothing on a schedule document means "this run's chat is listable now", so every signal read from one was too early or too late. Stop inferring. The list handler already reads the user's schedules and limits in parallel; read their active run rows alongside — one user-scoped query, joined by schedule id — and project the running occurrence's conversation id as `activeRun`. It comes from the run's own row, so the configRevision fence on the schedule projection cannot hide it, and it is absent until dispatch has actually reserved a conversation. The panel hook then hands every id the list names to the same admission watch Run Now uses, which probes until the server has the chat and adds the server's own row: one mechanism for both paths, idempotent per id. A run leaving the list has settled, and the list is re-read once for the order its settlement changed. * 🗓️ fix: Fetch Every Chat the Schedule List Names, and Scope the Run Read Three from codex on the rebuilt design. A run short enough to start and settle between two polls is never seen running, and most scheduled chats are short. The list also names the chat the last occurrence produced, so the panel now fetches every chat the list names that it has not seen — active or settled — through the same admission watch. The first observation still fetches only runs in flight: a panel opened long after a run must not go and fetch history. Project every running occurrence rather than the latest. A `requires_action` pause does not block the next occurrence, so a schedule can hold two, and reducing to one hid the pause's settlement. This also deletes the picker. The single-schedule route's run read started before ownership was known and was scoped only by schedule id. The response was gated, but a speculative read must stay scoped to the caller: use the user-bound query the list uses and narrow it, rather than touch rows the caller may not own. * 🗓️ fix: Let One Layer Decide What to Watch, and Say Which Runs Are Generating Two from codex on the previous round. The admission watch forgets a run whose delivery outlasted its budget so a later announcement can retry, but the panel kept its own permanent record of every id it had handed over and never announced one twice — so that retry could never happen. Drop the panel's record: every chat the list names is handed to the watch on every observation, and the watch is the one place that decides whether an id is landed, in flight, or worth trying again. The one thing the panel still must not do is fetch history. Opening it used to start a watch per active occurrence, and a run parked on an approval can sit there indefinitely and accumulate, its chat listed long ago. Carry each occurrence's status on the wire, and on the first observation treat only a generating occurrence as in flight; a settled one and a paused one are history, and a pause resolving later still re-reads the list. * 🗓️ fix: Read Only Generating Runs for the List, and Hand Over Only Those Three from codex, and this round removes more than it adds. The list's run read returned every paused row, unbounded, on each poll. `ScheduleRun` is indexed by status rather than by user, `requires_action` rows accumulate for as long as their approvals wait, and `started` rows are bounded globally by the capacity slots — so the read now asks for `started` alone, through an optional status narrowing on the existing method. A pause resolving is still seen through `lastRun`; what this gives up is only the corner where that projection is fenced by a mid-flight edit. A run that failed during initialization settles with its reserved id but never writes a conversation, so its route answers 404 for good — and handing settled ids to the watch meant re-probing it every poll, forever. The watch only ever needed generating runs: a settled one is already covered by the list re-read its settlement triggers, which brings the server's own row. A deleted schedule leaves the list, and comparing only the schedules still present missed the abort-and-settle that deletion performs on its run. A schedule vanishing now counts as its state moving. * 🗓️ fix: Compare a New Schedule Against Idle, and Bound the Landed-Run Record Two from codex on the head GitHub replayed onto dev. A schedule created in another tab can arrive in this client's list with its first run already settled, and a comparison that walks only the schedules seen before never looked at it. Compare a newcomer against the idle state: one that arrives with a run behind it is news the list should hear, one that arrives with no run yet is not. The watch remembers every run it landed so a later announcement is a no-op, and a panel that stays mounted sees a new id per occurrence for as long as schedules keep firing. Keep the most recent 256: a run is announced only while in flight, and none is still in flight by the time that many have started after it, so the oldest can go without a watch ever running twice. * 🗓️ fix: Re-read on First Sight Only When a Run Outran the Sidebar, and Never Evict a Live Watch Two from codex. "The first observation is silent" assumed the sidebar's lists had been read after any run they should hold, and that is not guaranteed: open the panel after a run fired and finished with it closed, and the card says the run succeeded while the sidebar was read before it ever fired. The first observation has no earlier one to compare against, so compare against the sidebar instead — re-read only if some run fired after the lists were last read, which is precisely the case where they lack its chat, and stay silent otherwise. The landed-run cap assumed fewer than 256 generations could be in flight at once, and the config schema bounds neither maxPerUser nor fireConcurrency. Keep in-flight watches in their own set, bounded by real concurrency and never evicted — a second watch for a run still being watched is the one thing that set exists to prevent — and cap only the landed record, where a forgotten id costs at most one extra probe. * 🗓️ fix: Re-read on First Sight When Anything Has Run, Release Runs the List Drops, Observe Every Poll Three from codex, each a defect in an earlier fix, and each answered by removing something. Comparing a run's fire time against the list cache's `dataUpdatedAt` was measuring cache writes, not server reads: a foreground chat inserted after the run advanced the stamp without adding the scheduled chat. There is no timestamp for "last read from the server", so stop guessing — the first observation re-reads if any schedule has run at all, and one refetch on opening the panel is the honest price. A run can be landed and still generating for minutes, announced on every poll; a count cap evicted it and restarted its probes. The hook is the one place that sees an occurrence leave the list, so it releases the id then, and the watch remembers a run exactly as long as something can announce it. No cap. React Query hands back the same array for a deep-equal poll, so an effect keyed on the data never ran again while a run stayed in flight — and a watch that gave up was never asked to try again. Key on the poll's timestamp. * fix: Release Scheduled Run Retention Across Admission and Unmount 🧹 |
||
|---|---|---|
| .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 | ||
| .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 | ||
LibreChat
English · 中文
🚀 What's New in v0.8.8-rc2
- Agent run control: Interrupt an Agent before visible answer text, steer runs with files and quoted excerpts, durably queue follow-ups, and recover saved partial work with Keep going or Answer now.
- Agent activity: Optional generated labels group reasoning and tool work, fold completed groups into live phase cards, keep generated files visible, summarize multi-step phases, and show the current reasoning direction.
- Human-in-the-loop Agents: Stream up to four related questions, pause for input or tool approval, and resume durably.
- Unified Agent Builder: Configure Skills, MCP, Code Interpreter, orchestration, Programmatic Tool Calling, model-spec controls, and per-tool background and intent settings in one Tools marketplace; Skills can be enabled for standalone runtime authoring without exposing the existing catalog.
- Durable Agent automation: Authenticated Agent Events support bound child actors, expected-action receipts, per-actor mailboxes, event batching, durable human pauses, and automatic detached Actions across built-in stream stores.
- Deeper Subagent history: Browse branch-aware child turns with bounded reasoning and stable live event views, load earlier activity, inspect event details, continue completed child chats, and automatically wake saved parent Agents when detached work settles.
- Background tools: Eligible Code Interpreter, MCP, Plugin, and Action tools can run while an Agent keeps working, with automatic delivery for supported completions and polling controls when needed.
- Code Interpreter workflows: Sandbox images return as viewable artifacts; highly experimental stateful sessions add scoped managed, attached, or personal environments, per-message file downloads, and guarded file-write and command permissions.
- Agent extensibility: Experimental Agent Plugins bundle deployment Skills, MCP servers, and opt-in command hooks; saved Agent teams run as isolated Subagent graphs.
- Scheduled Chats (experimental): Run saved Agents with presets or custom cron, selectable time zones, multi-day weekly cadence, and optional Chat Project destinations.
- Memory and context: Agents can use optionally isolated memory, preserve adaptive context fading across turns, and show categorized current-window usage, tokens, and optional cost.
- Editable long pastes: Long pasted text becomes an editable attachment that can be moved back into the composer; attachment-only turns and reliable Upload as Text downloads are also supported.
- Projects, settings, and navigation: Search conversation titles and message contents, manage project chats, use searchable settings and shortcuts, pin chats, choose clock/week conventions, and navigate faster on mobile.
- Sharing and artifacts: Stable shared links support personal copies; fullscreen previews, Mermaid export, PowerPoint templates, shell scripts, and original Office downloads expand file workflows.
- Web search: Keenable adds keyless search and page fetch, while SearXNG and Tavily gain richer controls and all web-tool egress uses stronger SSRF protection.
- Security and authentication: Default HTTP security headers, opt-in nonce CSP, authenticated local images, per-user Code Interpreter JWTs, stable SAML identity binding, live-session OpenID token refresh, and retired JWT-secret rejection harden deployments.
- Models and reasoning: Added GPT-5.6 with Responses reasoning controls, Claude Fable 5.1, Opus 5, and Sonnet 5, plus Gemini 3.8/3.7/3.6 Flash and Gemini 3.5 Flash-Lite.
- Langfuse observability: Configure encrypted in-app connections, tenant fanout, authenticated gateways, export-decision telemetry, and authorized session links in chats and shared views.
- Administration: Source-aware content filters can audit or block model-bound data, while tenant Insights, delegated configuration, encrypted secrets, and expiring violation scores improve operations.
- Streaming and reliability: Adaptive smoothing, Redis delta batching and failover recovery, automatic generation protocol v2, live MCP catalog refresh, Agent circuit breakers, and DocumentDB support improve long runs and scaled deployments.
Read the full v0.8.8-rc2 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
- 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
-
💬 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 🗃️
-
🌎 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
-
- 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.