Skip to content
AI NEWS JOURNAL
AI, IN PERSPECTIVE

Search AI news

Search headlines, summaries and articles to connect the dots.

Newest first

v0.13.3

Open WebUI v0.13.3 introduces agent-based automations with terminal and folder persistence, allows changing terminals and folders mid-chat, adds Brazilian Portuguese translations, and fixes issues including incorrect file tab behavior, agent visibility in model pickers, clipboard functionality over HTTP, DeepSeek reasoning mode compatibility, tool call labeling consistency, knowledge search punctuation handling, and Docker image build reliability.

v0.13.2

Open WebUI v0.13.2 resolves issues with loading chats and editing comments or Markdown files over plain HTTP, fixes the 'crypto.randomUUID is not a function' error, and makes the Side Chat permission switch visible independently of Temporary Chat settings.

b12101

The gguf writer now writes host-buffer tensor data directly to the file, skipping the temporary staging vector, which eliminates per-tensor allocation, zero-initialization, and memcpy operations.

v1.19.0 - Trace Your Workflows, Layer by Layer

Dify 1.19.0 enhances observability with nested workflow tracing, allowing users to follow execution steps inside Workflow Tools, inspect LLM calls, and maintain context across nested invocations. The release also enables portable app packages via App packages, improves Agent file uploads and previews, introduces Skill Hub automation through CLI commands, and upgrades the bundled plugin daemon to version 0.6.14-local. Key changes include support for format v2 app packages, enhanced security, improved editing workflows, and updated environment variables and API endpoints.

b11900

common: pin model resolution on real HF repo layouts (#30548) * tests: pin model resolution on real repo listings Extend test-model-resolution with 63 repo listings captured verbatim from the HF API, chosen to cover every file naming pattern found across 1237 GGUF repos of the major publishers and pruned to whole quant groups. Each repo pins its resolved plans and its cache listing. The expectations follow what each file really is per its GGUF header, not what the current resolver picks, so a mismatch is a resolution bug. Mismatches are collected and reported together before the test fails. * tests: leave the listing unchecked on paths the filesystem refuses Some real split names (DevQuasar's Model.Q2_K.gguf-00001-of-00012.gguf under a quant folder) exceed MAX_PATH once materialized in the

Timeline and related coverage