infochanged

Workers AI - Introducing Clef: Cloudflare's first open-source decision models, now on Workers AI

Announced: 2026-10-01
Tags: Workers-AI
Severity: info, set by reef/rss-rule-v1
Source: https://developers.cloudflare.com/changelog/post/2026-10-01-clef-workers-ai/

Meet <a href="https://developers.cloudflare.com/workers-ai/models/clef/"><code>@cf/cloudflare/clef</code></a> and <a href="https://developers.cloudflare.com/workers-ai/models/clef-flash/"><code>@cf/cloudflare/clef-flash</code></a>, the first models trained by the Cloudflare Workers AI team, available on Workers AI today. Clef is a decision model, in the same family as <a href="https://typesafe.ai/blog/introducing-system-one-models-and-jev" target="_blank" rel="noopener">Typesafe's Jev ↗︎</a>. Instead of generating text, it reads an input state and a set of typed questions, then returns a probability for every allowed answer. Your agent gets a structured decision it can act on immediately, for example: route the ticket, block the request, or escalate to a human. There is no free-form output to parse and no reasoning tokens to wait for. Both models are hosted on Workers AI as <a href="https://developers.cloudflare.com/workers-ai/models/clef/">Clef</a> and <a href="https://developers.cloudflare.com/workers-ai/models/clef-flash/">Clef-flash</a>. We are also open-sourcing the weights under the Apache 2.0 license on Hugging Face: <a href="https://huggingface.co/Cloudflare/clef" target="_blank" rel="noopener">Clef ↗︎</a> and <a href="https://huggingface.co/Cloudflare/clef-flash" target="_blank" rel="noopener">Clef-flash ↗︎</a>. Read the <a href="https://blog.cloudflare.com/clef-decision-models/" target="_blank" rel="noopener">launch blog post ↗︎</a> for the full story, including how we trained them. We are also launching a reinforcement learning (RL) fine-tuning service to help you tune Clef for your own workloads. <a href="https://www.cloudflare.com/resource/clef-rl-interest" target="_blank" rel="noopener">Sign up to work with us as a design partner ↗︎</a>. <div tabindex="-1" class="heading-wrapper level-h4"><h4 id="built-for-the-hot-path">Built for the hot path</h4><a class="anchor-link" href="#built-for-the-hot-path"><svg width="16" height="16" viewBox="0 0 24 24"><path fill="currentcolor" d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z"></path></svg></a></div> Clef is designed to be fast so decisions come back in milliseconds. Across our 43 benchmark runs, we achieved speeds where Clef is 2.5x faster than Jev at the median, and Clef-flash 13x faster. <div class="table-scroll" tabindex="0" role="region" aria-label="Table"><table> <thead> <tr> <th>Latency</th> <th>Clef</th> <th>Clef-flash</th> <th>Jev</th> </tr> </thead> <tbody> <tr> <td>Median</td> <td>209.3 ms</td> <td>38.8 ms</td> <td>524.1 ms</td> </tr> <tr> <td>p95</td> <td>238.6 ms</td> <td>122.4 ms</td> <td>536.0 ms</td> </tr> </tbody> </table></div> Hosting on Workers AI adds to that speed. Requests run on GPUs across Cloudflare's network, running close to your users, so the network round trip stays short. You can put Clef directly in the request path of your agent, then hand off to an LLM on Workers AI to take action. <div tabindex="-1" class="heading-wrapper level-h4"><h4 id="leading-the-benchmarks">Leading the benchmarks</h4><a class="anchor-link" href="#leading-the-benchmarks"><svg width="16" height="16" viewBox="0 0 24 24"><path fill="currentcolor" d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z"></path></svg></a></div> Across 10 decision benchmarks, a Clef model scores highest on 7, ahead of Jev and other open decision models. A few highlights: <div class="table-scroll" tabindex="0" role="region" aria-label="Table"><table> <thead> <tr> <th>Benchmark</th> <th>Clef</th> <th>Clef-flash</th> <th>Jev</th> </tr> </thead> <tbody> <tr> <td>BFCL (case exact)</td> <td>98.47</td> <td>98.76</td> <td>95.75</td> </tr> <tr> <td>BANKING77 (macro-F1)</td> <td>94.20</td> <td>90.93</td> <td>79.74</td> </tr> <tr> <td>CLINC150+OOS (macro-F1)</td> <td>97.43</td> <td>66.77</td> <td>89.27</td> </tr> <tr> <td>Home appliances (case exact)</td> <td>82.95</td> <td>97.73</td> <td>52.27</td> </tr> </tbody> </table></div> On Typesafe's own workflow evals, Clef beats Jev in 3 of 4 areas: invoice processing, customer service, and security incidents. The full results are on the <a href="https://huggingface.co/Cloudflare/clef" target="_blank" rel="noopener">Hugging Face model card ↗︎</a>. <div tabindex="-1" class="heading-wrapper level-h4"><h4 id="drop-in-compatible-with-jev">Drop-in compatible with Jev</h4><a class="anchor-link" href="#drop-in-compatible-with-jev"><svg width="16" height="16" viewBox="0 0 24 24"><path fill="currentcolor" d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z"></path></svg></a></div> <div class="table-scroll" tabindex="0" role="region" aria-label="Table"><table> <thead> <tr> <th>Model</th> <th>Size</th> <th>Best for</th> <th>Context window</th> </tr> </thead> <tbody> <tr> <td><a href="https://developers.cloudflare.com/workers-ai/models/clef/"><code>@cf/cloudflare/clef</code></a></td> <td>27B</td> <td>Highest-precision decisions</td> <td>64K tokens</td> </tr> <tr> <td><a href="https://developers.cloudflare.com/workers-ai/models/clef-flash/"><code>@cf/cloudflare/clef-flash</code></a></td> <td>9B</td> <td>Latency-critical, hot-path decisions</td> <td>64K tokens</td> </tr> </tbody> </table></div> Clef follows the System One API, so you can switch an existing Jev integration to Clef by changing the endpoint and model. Ask up to 64 questions per request, in three types: <ul> <li><code>noul</code>: A yes/no question. Returns the probability that the answer is yes.</li> <li><code>choice</code>: Pick one option from a set you define. Returns the chosen option, a probability per option, and a confidence value.</li> <li><code>score</code>: Rate against an ordered rubric. Returns a probability-weighted score and a probability per level.</li> </ul> <div><div data-nb-tabs data-nb-sync-key="workersExamples" class><div class="relative flex border-b border-border" role="tablist" data-nb-tabs-list></div><div class="mt-3"><div role="tabpanel" data-nb-tabs-content data-nb-tab-label="JavaScript" class><figure class="nb-code-figure" data-nb-lang="js"><pre class="astro-code astro-code-themes github-light github-dark nb-shiki-c6xiwz" tabindex="0" data-language="js" data-nb-lang="js"><code>const response = await env.AI.run("@cf/cloudflare/clef", { model: "clef", state: "Checkout has been failing for every customer for the last hour.", questions: { urgent: { type: "noul", instructions: "Is this support request urgent?", }, team: { type: "choice", instructions: "Which team should handle this request?", criteria: { billing: "Payments, invoices, and refunds", technical: "Outages, errors, and configuration", sales: "Plans and upgrades", }, }, }, }); // response.answers.urgent.noul -> probability the request is urgent // response.answers.team.choice -> highest-probability team</code></pre></figure></div><div role="tabpanel" data-nb-tabs-content data-nb-tab-label="TypeScript" class><figure class="nb-code-figure" data-nb-lang="ts"><pre class="astro-code astro-code-themes github-light github-dark nb-shiki-c6xiwz" tabindex="0" data-language="ts" data-nb-lang="ts"><code>const response = await env.AI.run("@cf/cloudflare/clef", { model: "clef", state: "Checkout has been failing for every customer for the last hour.", questions: { urgent: { type: "noul", instructions: "Is this support request urgent?", }, team: { type: "choice", instructions: "Which team should handle this request?", criteria: { billing: "Payments, invoices, and refunds", technical: "Outages, errors, and configuration", sales: "Plans and upgrades", }, }, }, }); // response.answers.urgent.noul -> probability the request is urgent // response.answers.team.choice -> highest-probability team</code></pre></figure></div></div></div><script type="module" src="https://developers.cloudflare.com/home/runner/work/cloudflare-docs/cloudflare-docs/src/components/ui/tabs/Tabs.astro?astro&type=script&index=0&lang.ts"></script></div> <div tabindex="-1" class="heading-wrapper level-h4"><h4 id="what-you-can-build-with-decision-models">What you can build with decision models</h4><a class="anchor-link" href="#what-you-can-build-with-decision-models"><svg width="16" height="16" viewBox="0 0 24 24"><path fill="currentcolor" d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z"></path></svg></a></div> <ul> <li>Support triage: Decide whether a ticket is urgent and which team owns it, then route it without a human in the loop.</li> <li>Threat intelligence: Classify a website by category. Paired with <a href="https://developers.cloudflare.com/browser-run/">Browser Run</a>, Clef fetched, rendered, and classified a domain in 2.2 seconds, compared to 4.7 seconds for <code>gpt-oss-120b</code> in the same workflow.</li> <li>Trust and safety: Score user submissions against your own policy rubric and act on the probability.</li> <li>Agent guardrails: Let an agent check "should I take this action?" in tens of milliseconds before calling a tool.</li> <li>Visual classification: Pass up to four images alongside the state. Unlike text-only decision models, Clef has a vision encoder.</li> </ul> <div tabindex="-1" class="heading-wrapper level-h4"><h4 id="get-started">Get started</h4><a class="anchor-link" href="#get-started"><svg width="16" height="16" viewBox="0 0 24 24"><path fill="currentcolor" d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 0 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 1 0-1.42-1.42Zm8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 0 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 1 0 1.42 1.42l3.88-3.89a4.49 4.49 0 0 0 0-6.33ZM8.83 15.17a1 1 0 0 0 1.1.22 1 1 0 0 0 .32-.22l4.92-4.92a1 1 0 0 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42Z"></path></svg></a></div> Use Clef through the <a href="https://developers.cloudflare.com/workers-ai/configuration/bindings/">Workers AI binding</a> (<code>env.AI.run()</code>) or the REST API at <code>/ai/run</code>. You can also use <a href="https://developers.cloudflare.com/ai-gateway/">AI Gateway</a> with these endpoints. For more information, refer to the <a href="https://developers.cloudflare.com/workers-ai/models/clef/">Clef model page</a>, the <a href="https://developers.cloudflare.com/workers-ai/models/clef-flash/">Clef-flash model page</a>, and <a href="https://developers.cloudflare.com/workers-ai/platform/pricing/">pricing</a>.

The text above is the source's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.