Back Home

GitHub Repo

LocalAI 5.0 Moves Agent Conversations to the Server; Legacy Management APIs Return 404 After Upgrade

Released on November 18, LocalAI 5.0 keeps conversations running after the browser closes and adds file operations and a Linux sandbox. The new version overhauls the agent management interface, so existing integrations should check API paths, data conversion, and connector enablement.

Mikhail Evstafiev · CC BY-SA 3.0 · Image source
zh-Hant

LocalAI released version 5.0 on November 18, moving chat and agent execution to the server and adding Projects, a desktop application, and a file workspace. For teams self-hosting open models, the key change is that the server now stores and runs conversations: tasks can continue after users close the tab, and messages sent during execution are queued for the model to process in the next step. Release notes

The new execution flow supports subagents, long-conversation compaction, and persistent goals. File operations are integrated into the same history, allowing users to undo model changes. Projects keep materials, tool presets, and memory notes in one folder. Changes to notes proposed by the model must be confirmed before they are saved. However, the official announcement makes clear that Projects are only an organizational feature: conversations outside a project may still read these files from the user's home directory, so this should not be taken to mean access is isolated. Official announcement

The main upgrade risk is the management interface. Legacy paths such as /api/agents and /api/conversations return 404; integrations must switch to /api/chats/agents and /api/chats. On first startup, existing data is converted to the new format while the old data is retained. Triggers, connectors, and bindings in the converted data are disabled by default. Chat history stored only in the browser is not migrated automatically and must be imported separately. Operators can use /api/chats/conversion to check for failed or skipped conversions and discarded settings. Migration documentation

Code execution is provided by the Sandbox add-on, which mounts files in an isolated environment using KVM or gVisor. It has no network access by default, and this release provides a production-ready version for Linux only. Other add-ons still run under LocalAI's operating system account, so the same isolation assumptions do not apply. Engineering teams should next validate legacy agent conversion, scheduler recovery, file permissions, and the undo workflow in a test environment. Although /v1/chat/completions remains unchanged, that does not mean surrounding agent management integrations can be reused without changes. Release notes and limitations

Sources

  1. LocalAI v5.0.0 release
  2. LocalAI 5.0: your AI does the work, you keep the files
  3. Chats: moving from the old chat, agents and skills