Jan v0.8.5: Fixes-Only Release, Key Backend and CLI Changes
Jan version 0.8.5 is a maintenance release with critical backend, API, and platform compatibility updates but no new end-user features. Developers should evaluate their CLI workflows, local model compatibility, and update automation in light of bundling changes and security tightening.
What changed?
Jan v0.8.5 introduces several non-feature changes: the llama.cpp backend (v0.5.0) is now bundled with the app, removing the need for separate first-run downloads or engine updates. Local models will no longer run on Intel Macs, as the engine is built for Apple Silicon only. The jan CLI is no longer bundled with the desktop app and must be installed separately. The desktop executable is now named Jan-Desktop, changing executable paths. The Local API Server now enforces a Trusted Hosts allowlist when bound to 0.0.0.0, rejecting connections that do not match the configured list.
Additional changes include renaming the agent's bash tool to shell (running PowerShell on Windows), changes in backend selection for CUDA-incompatible GPUs (falling back to Vulkan), and new defaults for session memory and prompt caching. Known limitations involve CLI removal workflow, PowerShell and AppArmor restrictions on sandboxed tools, and Intel Mac incompatibility.
Why does it matter to an everyday developer?
Developers using Jan for local model work need to confirm their hardware: Intel Macs will no longer support local llama.cpp models and must remain on v0.8.4 for that functionality. The switch to a bundled engine simplifies deployment and version management but removes the ability to choose alternate backend versions for specific GPU support. Improvements in API binding security (Trusted Hosts enforcement) reduce risk when exposing Jan's API server beyond localhost.
Workflows depending on the jan CLI being available from the desktop install must now install the CLI separately. Scripts or automations that launch Jan via the old executable name or rely on CLI invocation paths require updates. Tool definitions referencing bash must be updated to shell. On some systems, limitations in PowerShell or AppArmor policies will affect shell-related features.
