Urgent.News

What's breaking now, across thousands of outlets.

AI

Liquid AI's d1 Decision Models Went Open: Triage Support Tickets on a CPU With the 600M One (and Where It Fools You)

Attributed compile + one small real CPU run Primary sources (Liquid AI, 2026-10-07): Open d1: Edge decision models for text, vision, and audio (Liquid AI blog), Multimodal open d1 decision models for the edge (Hugging Face blog), and the model cards for d1-3B and d1-omni-600M Background: Introducing d1: The most capable decision model, now with vision (Liquid AI, 2026-10-05) All benchmark and…

Liquid AI recently made its d1 decision models open source, allowing users to run text, vision, and audio-based decision models on a single CPU. The company released two models: d1-3B (3.12B parameters, built on LFM2.5-VL-3B) and d1-omni-600M (350M bidirectional encoder plus vision and audio encoders). The d1 models return typed, calibrated answers in one forward pass, without generating any output tokens. This is useful for tasks such as ticket routing, intent classification, and moderation checks.

Liquid AI claims that the d1-3B model scores 48.57 on Decision Index v0.2.1, which is the best under 10B and on par with a 35B-A3B decision model. The d1-omni-600M model scores 15.95 on the same index and is described as an early research release, with no speed numbers provided. Both models support day-one transformers via trust_remote_code and have llama.cpp support. The 3B model is the one Liquid AI is pushing.

Liquid AI tested the 600M model by running 12 short support tickets through the system and measuring latency, accuracy, and batch performance. The results showed that the model could handle mixed tickets and flag high-risk cases with confidence scores. However, the model also incorrectly classified some non-ticket inputs as billing or technical issues. To address this, Liquid AI recommends adding a catch-all option and a separate noul gate to ensure more accurate classification.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

How to test whether coding agents discover the skills you need

A coding skill can be clear, correct, and still fail to help if an agent never finds it. Testing a skill by naming it directly only answers whether the agent can use it after it has been loaded.

  • Conduct task-based assessments for coding agents to gauge skill discovery.
  • Analyze execution traces to measure skill loading without explicit guidance.
  • Track three metrics: skill activation, utilization, and application performance.

The AI Co-Pilot Dilemma: Does Code Generation Stifle Authentic Programming Practice?

AI coding assistants now write boilerplate, suggest entire functions, and explain error messages in seconds. For many developers, that speed feels like a gift.

  • AI coding assistants generate code rapidly, raising concerns about authentic practice.
  • Removing friction from programming may hinder learning if solutions aren't understood.
  • Beginners should write their own versions of code to develop deeper comprehension.

Gemma 4 From E2B to 31B on an AMD MI300X: fp8 Overtakes bf16 From 12B Up

This article provides a step by step guide to serving every Gemma 4 size, E2B, E4B, 12B, 26B-A4B and 31B, on one AMD Instinct MI300X through vLLM in four weight formats, with each build timed across…

  • Gemma 4 models range from E2B to 31B size
  • fp8 format overtakes bf16 from 12B and larger
  • 4-bit models are 0.14x to 0.69x faster than bf16

WIldGuard AI

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 1: Touch Grass What I Built WildGuard AI — AI-Powered Wildlife Exploration WildGuard AI is an AI-powered wildlife application…

  • WildGuard AI is an AI-powered wildlife identification app
  • Open-source AI models enable local inference and offline identification

More from Friday 9 October →