Alibaba launches Qwen4-Max, a new flagship model with 2.4 trillion parameters that activates only 71 billion per token. A hybrid architecture sharply cuts costs on long contexts. Qwen4-Max lands just behind Kimi K3.1 Pro on the Artificial Analysis Intelligence Index, and Alibaba plans to release smaller Qwen4 models as open source. The article Alibaba's Qwen4-Max takes on Opus 5.5, GPT-6, and Kimi K3.1 Pro at much lower prices appeared first on The Decoder.
Claude can now embed text, buttons, and other web elements into complex graphics and 3D effects. The article Claude now builds interactive websites inside canvas graphics, reviving the Flash era with real HTML appeared first on The Decoder.
Anthropic studied how Claude retains knowledge across sessions. Selective notes beat exhaustive archives by a wide margin. In a Pokémon Red test, the newer Claude Fable 5 got four times as far as the older Sonnet 3.7 by keeping just a handful of strategy files instead of more than 400. A "Dreaming" process retroactively corrects faulty memories. The article Anthropic says the key to agent memory is knowing what to forget, not how much to store appeared first on The Decoder.
Meta has moved Catching Just-in-Time Tests (JiTTests) from research prototype into its production infrastructure. Meta JiTTests is an LLM-based system that writes executable tests designed to fail on a risky code change. A failing test is concrete evidence that a diff changed behavior. Meta team reports that JiTTests caught 74 privacy SEVs at the diff stage in the first half of 2026. The method is described in the FSE 2026 research paper ‘Just-in-Time Catching Test Generation at Meta‘. TL;DR Scale: Runs on Meta backend code with hundreds of millions of lines. The research paper analyzes 22,126 generated tests. Runs on: Meta’s internal infrastructure, overnight on spare capacity. Judge models in the paper: Llama3.3-70B, Gemini 3 Pro, Claude Sonnet 4. Not publicly available. Performance: Engineers report a 60% true-positive rate at full scale (self-reported). Best: 74 privacy SEVs caught before landing in H1 2026; privacy SEV occurrence down 20%. Worst: The initial deployment confirmed only 8 of 41 reported catches (19.5%). Bottom line: Best: executable proof of a bug before merge. Worst: internal only, with self-reported numbers. What are Catching JiTTests? Catching JiTTests are LLM-generated tests that should fail when a diff introduces a bug. Traditional hardening tests pass when written and guard against future regressions. Catching tests target the change under review, before it lands. Meta formalized the details in its 2025 paper ‘Harden and Catch’. Most AI bug tools act like faster human reviewers. They read the diff and leave comments. JiTTests instead execute code and show a concrete behavioral difference. Meta team concedes this takes more computational steps. It argues the approach catches bug classes that LLM or agent review can miss. How does the JiTTests pipeline work? The production pipeline has 5 stages: Targeting: Runs overnight on spare capacity. It selects the previous day’s risky diffs, using a mechanism similar to Meta’s Diff Risk Score. Test generation: 2 diff-aware workflows produce candidate tests (explained below). LLM-as-Judge ensemble: Several LLMs score each failing test using the test code, failure trace, diff and inferred intent. RubFake: The Rule-Based False-Positive Killing Environment adds deterministic checks. Its rules flag patterns like reflection, broken mocks and not-implemented exceptions. Human-on-the-loop: The system decides whether to contact an engineer, based on the combined ranking. Dodgy diff vs intent-aware: what is the difference? The dodgy diff workflow assumes every diff is buggy. It treats the diff as a mutant of its parent and generates tests that tell them apart. The intent-aware workflow first infers what the diff should do from its code, title and summary. It lists risks, builds a mutant for each, and writes tests to kill them. Tests that then fail on the real diff become ‘weak catches.’ What do the benchmarks show? The research team analyzes 22,126 generated tests. Diff-aware methods produced 4x more candidate catches than hardening tests. They produced 20x more than tests that failed by coincidence. The intent-aware workflow produced weak catches in 6.4% of its tests and on 7.9% of diffs. Dodgy diff scored 2.5% and 4.0%. Meta’s earlier ACH mutation-guided hardening scored 0.8% and 1.6%. The rule-based and LLM assessors cut human review load by 70%. (function(){var f=document.getElementById("mtp-jit-frame");window.addEventListener("message",function(e){if(e.data&&e.data.mtpJitH&&f&&e.source===f.contentWindow){f.style.height=e.data.mtpJitH+"px"}})})(); *Figures from Table 1 of the JiTTests paper (self-reported, Meta codebase). TestGen-LLM row uses the “need not add coverage” setting. A weak catch is a candidate failure, not a confirmed bug. What changed at full scale? The initial deployment was modest. Meta reported 41 candidate catches to engineers. 8 were confirmed true positives, a 19.5% rate. 4 of those would have caused serious failures in production. The October 2026 engineering post reports much stronger production numbers: 589 engineers engaged with JiTTests, 64% of those contacted. Engineers reported a 60% true-positive rate. 74 privacy SEVs were caught at the diff stage in the first half of 2026. Overall privacy SEV occurrence fell 20% in the same period. What does human-on-the-loop mean? Human-in-the-loop means a person reviews every output. Human-on-the-loop means engineers set criteria and monitor results in aggregate. They intervene at the policy level, not on each test. Meta team rarely need to read test code. They only confirm whether an observed behavior change was intended. Can developers use JiTTests? The answer is No. JiTTests is internal Meta infrastructure. Meta has not released code, models or an API. Teams can still copy the pattern: diff-aware mutation-guided test generation, an LLM judge ensemble, deterministic filters and aggregate human oversight. Key Takeaways Meta’s JiTTests writes LLM tests meant to fail on buggy diffs. 74 privacy SEVs caught pre-merge in H1 2026; privacy SEVs down 20%. Engineers report a 60% true-positive rate, up from 19.5% in the paper. Intent-aware tests hit weak catches at 6.4%, vs 0.8% for ACH hardening. Internal only: no code, model or API released. Check out the engineering post, the FSE 2026 paper and Meta’s announcement on X. You can check the deployment options and specs here through our GPULeaderboard.com chrome extension. Also, feel free to follow us on Twitter and don’t forget to join our 150k+ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well. Need to partner with us for promoting your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar etc.? Connect with us The post Meet Meta’s JiTTests: LLM-Generated Tests Designed to Fail Before Risky Code Lands appeared first on MarkTechPost.
Alibaba’s Qwen team has released Qwen4-Max, the first model of its Qwen4 generation. Qwen4-Max is a proprietary sparse MoE model with a 2.4T-parameter backbone and 71B parameters active per token. It accepts text, images and video, and supports a 1M-token context window. Alibaba also cut API prices and reports a 62% drop in average cost per task. TL;DR Size: 2.4T backbone parameters, 71B active per token, plus 328B N-gram Embedding parameters. 1M context, 393K max output tokens. Runs on: Hosted only: QwenCloud API, Token Plan, Qwen Studio, QwenWork and Qoder. No open weights, so no self-hosting or quantized builds. Performance: A large jump over Qwen3.8-Max. Competitive with frontier models on agentic work, behind on hard coding and vision. Best: HLAB-Vals-1.1 (legal agent work): 21.3, versus 11.7 for Kimi K3.1, the next-best model. What is Qwen4-Max? Qwen4-Max is a multimodal MoE language model from Alibaba, built for long-horizon professional work. A Token Plan-only preview opened this month only. How does the Qwen4-Max architecture work? Qwen4 upgrades the sparse MoE design in 3 places: attention, residual connections and embeddings. GDN + Qwen Sparse Attention (QSA): Each QSA layer pairs with 3 Gated DeltaNet layers. These compress history into fixed-size states. QSA then uses a lightweight indexer to pick relevant context at micro-block granularity. This lowers attention and indexing cost on long sequences. Gated Residual (GR): 4 parallel residual branches use dynamic read and write gates. The aim is stronger information flow and better training stability. N-gram Embedding: 328B extra parameters provide lookups of local token patterns at layer 2. This adds capacity with little extra compute. Alibaba reports no loss spikes across the 2.4T-scale pre-training run. On in-house tests, Qwen4-Max-Base shows 5 to 13% lower bits per byte than Qwen3.8-Max-Base. It does this while activating 25% fewer parameters. How does Qwen4-Max perform on benchmarks? Alibaba’s comparison chart covers 16 benchmarks. Rivals are Qwen3.8-Max-0902, Claude Opus 5.5, GPT-6.1 Sol, GPT-6 Astra and Kimi K3.1. Several scores are cited from third-party leaderboards. None were independently reproduced at launch. Qwen4-Max ranks first on 4 of 16 benchmarks: HLAB-Vals-1.1 (legal agents): 21.3, versus 11.7 for Kimi K3.1 and 9.2 for Opus 5.5. Agents’ Last Exam v1.1: 46.7, versus 43.4 for Opus 5.5 and Kimi K3.1. BioMysteryBench: 85.0, versus 84.4 for GPT-6.1 Sol. DeepSWE v1.1: 75.7, versus 75.5 for Kimi K3.1. Claude Opus 5.5 leads 7 of the 16 charts. Qwen4-Max trails most clearly on coding and vision: ProgramBench: 31.5 versus 65.0 for Opus 5.5. Terminal-Bench 4.0: 48.5 versus 67.2 for Kimi K3.1. Chartography: 54.2 versus 71.1 for GPT-6 Astra. Humanity’s Last Exam: 51.7 versus 59.8 for Opus 5.5. On Alibaba’s own Work360 benchmark, Qwen4-Max scores 52.69, up from 47.74 for Qwen3.8-Max. Work360 spans 26 top-level domains and 721 specialized fields. (function(){var f=document.getElementById("mtp-qwen4max-frame");window.addEventListener("message",function(e){if(e.data&&e.data.mtpEmbed==="qwen4max"&&e.source===f.contentWindow){f.style.height=e.data.h+"px";}});})(); Why is Qwen4-Max cheaper to run? Two things stack: fewer tokens and lower prices. On Work360, token use drops about 24% at Xhigh effort and 35% at High effort. On Terminal-Bench 4.0, the drops are about 48% and 49%. Average Work360 cost per task falls from $4.43 to $1.67, a 62% cut. List prices fell too. Input is $1.50 per million tokens, down from $2 for Qwen3.8-Max. Output is $4.50, down from $6. Implicit cache reads drop 70%, from $0.25 to $0.075. Qwen4-Max vs competitors *Scores from Alibaba’s Qwen4-Max chart. Qwen3.8 column is Qwen3.8-Max-0902. The chart labels Kimi as “Kimi K3.1”. Moonshot’s own card reports Terminal-Bench 4.0 of 65.7 for Kimi K3.1 Pro and 66.4 for Opus 5.5. How can developers use Qwen4-Max? The model ID is qwen4-max on QwenCloud. The API works with OpenAI-compatible and Anthropic-compatible clients. Supported features include function calling, structured outputs, context caching, batch processing, web search and fine-tuning. The default rate limit is 5,000,000 tokens per minute. Thinking mode is toggled with enable_thinking. Subscription access runs through the Token Plan. Key Takeaways 2.4T MoE backbone, only 71B active per token. New QSA attention, Gated Residuals and 328B N-gram Embeddings. First on 4 of 16 charted benchmarks, led by HLAB-Vals-1.1 at 21.3. $1.50/$4.50 per million tokens, cached input down 70%. Weak spots: ProgramBench (31.5) and Terminal-Bench 4.0 (48.5). Check out the official Qwen4-Max blog, the QwenCloud model page and the Token Plan pricing page. You can check the deployment options and specs here through our GPULeaderboard.com chrome extension. Also, feel free to follow us on Twitter and don’t forget to join our 150k+ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well. Need to partner with us for promoting your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar etc.? Connect with us The post Alibaba Releases Qwen4-Max: 2.4T MoE, 71B Active, 1M Context appeared first on MarkTechPost.
Hark has released Handoff², the second version of the computer-use agent inside its Hark Pro app. The Hark Handoff 2 computer-use agent finishes web tasks about 2x faster than the original, on average. Hark states that the gains come from reinforcement learning (RL) that penalized wasted turns and latency. For teams building browser agents, it is a case study in training for speed, not only accuracy. You can check the deployment options and specs here through our GPULeaderboard.com chrome extension. TL;DR Runs on: Hark’s cloud. Each request gets a dedicated virtual computer. Users reach it from web, iOS and Android. No local or quantized option. Performance: 82% task completion on Hark’s 478-task internal benchmark, about 2x faster end to end than v1. Best: 93.8% on Hark’s internal alignment benchmark (v1: 90.3%). Worst: 82% browsing completion still trails Claude Opus 5.5 (max), by up to 5 points, in the same harness. Bottom line (best): Up to 3.8x faster flight booking and more than 5x faster long research. Bottom line (worst): Every Handoff² number is self-reported. No third-party score exists yet. What is Hark Handoff²? Handoff² is a computer-use agent from Hark that operates websites the way a person does. It clicks, types and scrolls on live pages instead of calling APIs. Hark previewed Handoff in August and shipped it in Hark Pro in October. Since then, Hark says it has logged over 5.6M browsing sessions and handled over $20M in purchases. Users send it groceries, flights, dentist appointments, refunds, warranty forms and job applications. How does Handoff² get 2x faster? Hark co-evolved 2 things: the agent harness and the RL training recipe. The new harness lets the model emit more actions per turn. Training then penalized excess turns, unnecessary thinking tokens and end-to-end latency. The model learned 3 habits: Batch actions, such as filling several form fields in 1 turn. Group repeated action patterns into reusable composite actions. Reuse those composites as the task continues. Each request runs on a dedicated virtual computer with its own browser, file system and terminal. The model outputs cursor and keyboard actions aimed at screen coordinates. Because savings stack per turn, gains grow on longer, browsing-heavy tasks. How fast is Handoff² compared with Handoff? Hark reports these speedups over v1: Average: about 2x faster end to end. Flight booking: up to 3.8x faster. Long research tasks: more than 5x faster. Examples: a 10-minute task can drop to 3 minutes, and a 45-minute task to about 10. What do the Handoff² benchmarks show? Hark reports 2 internal benchmarks: Browsing: 478 tasks across 238 websites. Handoff² completes 82%, up from 73% for v1. It takes 46% less time per task. Hark ran Claude Opus 5.5 (max) in the same harness as Handoff². Handoff² lands within 5 points of it. Note that v1 was measured in its original harness, not the new one. Alignment: 93.8% for Handoff², up from 90.3% for v1. The suite checks that the agent never checks out without approval. It also checks that the agent asks for clarification only when a request is truly ambiguous. On the public Online-Mind2Web human-eval leaderboard, the original Handoff scores 97.67%. Yutori’s Navigator n1.5 sits at 97.3%. Hark has not posted an Online-Mind2Web result for Handoff² yet. (function(){var f=document.getElementById('mtp-hk2-frame');window.addEventListener('message',function(e){if(e.source===f.contentWindow&&e.data&&e.data.mtpHk2Height){f.style.height=e.data.mtpHk2Height+'px';}});})(); How does Handoff² compare with other web agents? How can users and developers access Handoff²? Handoff² ships inside Hark Pro on the web, iOS and Android. Hark has not announced a public API or weights. Per the pricing page, Hark Pro is free. Pro² costs $20 a month for 2x usage. Pro³ costs $100 a month for 10x usage. All features are offered on all plans. Key Takeaways Handoff² averages 2x faster than v1: up to 3.8x on flights, 5x+ on long research. RL penalized turns, thinking tokens and latency, so the model learned to batch actions. Task completion rose from 73% to 82% on Hark’s 478-task internal benchmark. Alignment rose to 93.8%, but every Handoff² number is self-reported. Available now in Hark Pro: free, $20 or $100 a month. Check out the Hark’s Handoff² announcement, the original Handoff research preview, and the Online-Mind2Web leaderboard. Try Hark Pro. You can check the deployment options and specs here through our GPULeaderboard.com chrome extension. Also, feel free to follow us on Twitter and don’t forget to join our 150k+ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well. Need to partner with us for promoting your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar etc.? Connect with us The post Hark Releases Handoff², a 2x Faster Computer-Use Agent for Hark Pro appeared first on MarkTechPost.
Anthropic's Claude Fable 5.2 doesn't generate images the way other AI models do. Instead of computing pixels, the language model writes Python code that places hundreds of thousands of simulated brushstrokes on a virtual canvas, complete with bristle texture and paint application. A single photorealistic parking garage scene took roughly 700,000 strokes, according to Anthropic employee Jake Eaton. The article Anthropic's Claude Fable 5.2 doesn't generate images, it paints them appeared first on The Decoder.
Megaspeed, the firm owned by ousted Nvidia CEO Jensen Huang's former lover Alice Huang, arranged nearly $12 billion in Nvidia chip orders for Chinese companies between 2024 and 2025, according to the WSJ. Short seller Culper Research estimates Nvidia's actual China revenue share exceeds 20 percent, far above the officially reported 7 percent. The article Firm linked to Jensen Huang's ex-lover reportedly brokered nearly $12 billion in Nvidia chip orders for China appeared first on The Decoder.
Australia's central bank sees early signs that AI is hitting young entry-level workers in highly exposed jobs like software development and customer service. Since ChatGPT launched, job postings and employment among 15- to 24-year-olds in those fields have dropped more sharply than among older workers. Author Mike Major cautions against jumping to conclusions, however, noting that business cycle shifts and remote work trends could also explain the numbers. The article Australia's central bank finds AI hitting young workers first, especially in software and customer service appeared first on The Decoder.
Bland, the San Francisco voice-AI company, has released Tofu-1, a full-duplex speech-to-speech model in research preview. The Tofu-1 speech-to-speech model targets calls from moving cars, hospital rooms and weak-signal lines. It listens while it speaks and reasons while it talks. For phone-agent teams, one model now handles audio in and audio out, with no transcript between. You can check the deployment options and specs here through our GPULeaderboard.com chrome extension. What is Tofu-1? Tofu-1 is a full-duplex speech-to-speech model from Bland that hears, reasons and replies in audio during phone calls. It is the first release in a planned family of Bland speech-to-speech models. How does Tofu-1 differ from a cascade voice agent? Most voice agents are cascades. They turn speech into text, pass it to a language model, then turn the reply back into speech. Tofu-1 listens to the audio directly, so tone, hesitation and background sound stay available to the model. Bland has not published the internal architecture. Audio understanding Bland lists 3 audio skills on its product page: Speaker tracking: tells speakers apart and works out who each one is addressing. Noise separation: separates voices from a crying child, a TV, highway traffic, a hospital intercom or keypad tones. Paralinguistics: hears hesitation, frustration and urgency. Full duplex and thinking while talking Callers can interrupt or correct Tofu-1 mid-sentence. While it works on a request, it keeps the conversation moving. It reports the result only when the work is done. It never claims a task is finished early. Scene generation Because Tofu-1 models the sound of a call, it can also produce one. That includes a second speaker, the room around them and line noise. What is Bland’s ‘TV Test’? The TV Test asks one question: can the model follow the caller while ignoring speech from another scene? TV audio is often louder than the caller. Bland marks its TV Test walkthrough as illustrative, not recorded model output. How does Tofu-1 compare with other full-duplex models? Competitor figures come from each vendor’s own page. FDB results use different benchmark versions and are not directly comparable. How can teams access Tofu-1? Research preview access is open to a limited number of enterprises. Bland names banking, healthcare, insurance and government as target sectors. The sign-up form asks for monthly call volume, from under 1,000 to 50,000+. Key Takeaways Tofu-1 is Bland’s first full-duplex speech-to-speech model, built for noisy calls. It hears audio directly: speakers, background noise and caller emotion. The only number is self-reported: over 92% could not spot it in screenings. No size, latency, pricing or benchmarks yet; rivals publish latency and tool-use scores. Access is a closed enterprise preview, with Bland citing January availability. Check out the Tofu-1 product page, the launch post on X and the research preview sign-up. You can check the deployment options and specs here through our GPULeaderboard.com chrome extension. Also, feel free to follow us on Twitter and don’t forget to join our 150k+ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well. Need to partner with us for promoting your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar etc.? Connect with us The post Bland Launches Tofu-1, a Full-Duplex Speech-to-Speech Model for Calls appeared first on MarkTechPost.