LocalAI 5.0.0 was published on November 18, 2026 at 17:00 UTC. Its release notes move chats to server execution, allowing work to continue after the browser tab closes. The change makes migration an execution-policy decision as well as a conversation-history decision.
Persistence and sandboxing have different boundaries
The release adds projects, file history and a sandbox. The sandbox is Linux-only in this version; it attempts KVM with Cloud Hypervisor, then gVisor, and disables network access by default. Administrator-controlled proxy access is described in the sandbox documentation. These are documented project behaviors, not safety guarantees tested for this digest.
Migrated automation starts disabled
The migration guide says conversion preserves old data while creating new objects. Converted triggers, MCP connectors and connector bindings start disabled. Browser-only conversations need explicit import, and a migration report identifies failed items and settings that were dropped.
A useful migration review should inspect those unresolved items before treating the new environment as equivalent to the old one. Persistent execution, imported history and permission activation answer different questions.
A proposed check of the three boundaries
Original exercise, not executed: prepare a synthetic measurements CSV and a saved agent intended to work within one scratch folder. Close the browser during a task, reconnect and inspect execution and file history. Separately examine an imported trigger while it remains disabled.
Record whether the task retained its identity, which files it accessed and whether any automation became active. Enable nothing merely because an answer looks correct. These observations would test persistence and migration assumptions independently.
The tagged MIT license was checked. No upstream code is reproduced here.
Sources accessed November 21, 2026. Views are my own and do not represent any employer, past or present.
Sources and evidence
Review persistent execution, migrated data and automation permissions separately before enabling converted triggers or connectors.