AllyshipContent Radar

Hands-on 278

Công cụ, thử nghiệm và hướng dẫn thực hành

Crawl live-1795090500000 · 19:15 19 thg 11, 2026 · Xuất bản 19:35 19 thg 11, 2026

19

[AINews] Fable 5.2 retakes World #1 LLM spot as $ANT IPO roadshow begins

41.5

Thử nghiệm thực tế swyx .ai

On Friday, we asked Jamin Ball what comes next for Anthropic’s IPO . On Monday the roadshow started and Anthropic shipped the long-anticipated next-version of Claude Fable and Mythos . Of course, it is the new top model in the world, taking back Opus 5.5’s #1 spot from Gemini 4 Carbon which had its brief moment in the sun (10 days). View post on X ↗ Fable comes with a 20% per token price cut… but is more token hungry, as both SemiAnalysis GDPx and Artificial Analysis agree: Fable 5.1 cost $10 per million input tokens and $50 per million output tokens. Fable 5.2 costs $8 and $40 . Yet on GDPx, a benchmark of professional tasks, SemiAnalysis paid $88.15 per task, up from $67.16 . The run logs give a clue. Where Opus 5.5 and Fable 5.1 would try about 20 test cases, 5.2 sometimes wrote hundreds or thousands and spun up subagents to check its work independently. All that checking helped Fable take first place at 16.4% . You pay for the checks either way. Which effort setting should you put in production? On FrontierCode 2.0, Anthropic reports that Fable at High matched Opus 5.5 at Max for about half the cost per task… but don’t talk about Fable at Max. AI News for 11/07/2026-11/09/2026. We checked 12 subreddits, 544 Twitters and no further Discords. AINews' website lets you search all past issues. As a reminder, AINews is now a section of Latent Space . You can opt in/out of email frequencies! AI Twitter Recap Top Story: Claude Fable 5.2 / Mythos 5.2 Benchmarks, Economics, Restrictions, and First Impressions What happened Anthropic shipped Claude Fable 5.2 and Claude Mythos 5.2, claiming both are "a step above Opus 5.5 in almost all the capabilities we evaluated." It tops most independent leaderboards. It also arrives with deliberate RSI nerfs, heavier per-task costs and restricted subscription access. Launch claims. @claudeai announced the pair as built for "the most daunting technical challenges," with gains in coding, reasoning and vision. @marktenenholtz flagged unusual system-card phrasing: "The model that underlies Claude Fable 5.2 and Claude Mythos 5.2." That implies a single shared base model. Vendor-reported headline numbers , per @kimmonismus : Up to 30% faster output than the 5.1 models. On FrontierCode 2.0, Fable 5.2 at High matched Opus 5.5 at Max for about half the cost per task, and at Xhigh it was the top released model. 1,000 Fable 5.2 agents formalized the existing proof of Fermat's Last Theorem in 30 hours. Opus 5.5 completed 26% in 18 hours on the same setup. Mythos 5.2 accurately modeled 28 of 34 gene-therapy capsids. Alignment was at or above recent Claude models, with external pre-release testing. Default effort. Medium is the default effort in the Claude apps and Claude Code. Pricing. $8/$40 per 1M input/output tokens, 20% below Fable 5.1's $10/$50 ( @jaminball , @arena ). The rest of the spec, per Artificial Analysis : Cache writes cost $10 (5-minute TTL) or $16 (1-hour TTL); cache reads cost $0.20. 1M-token context with text and image input. Five effort levels: low, medium, high, xhigh, max. Long-horizon demos from Anthropic. An OS was built from an empty folder by 1,000+ subagents over 8 days. It boots on a laptop and has its own kernel, disk/keyboard/network drivers, persistent storage, windowing, login, an installer and built-in Claude ( @kimmonismus ). Fable designed three working electronic devices from a short prompt ( @kimmonismus ). It proposed untested chemical synthesis routes. It improved on listed solutions to 72 open optimization problems. @RLanceMartin published the safety-bounded scaling write-up for the 1,000-agent FLT run. Subscription access. Ultra and Team Premium users get Fable "resets" scaled by tenure: 1 reset under 6 months, 2 for 6–12 months, 3 above 12 months, usable until March 8 ( @ClaudeDevs ; echoed by @bcherny and @edwinarbus ). Pro and Team Standard get a one-week trial capped at half the weekly limit, plus one reset. Fable can only consume 50% of a weekly limit. Data retention. Fable 5.2 requires data retention by default so Anthropic's safety classifiers can run. Zero data retention is available only to eligible enterprise customers ( @code ). Rollout, day one: Cursor ( @cursor_ai ). GitHub Copilot / VS Code, where it "solved more tasks than Fable 5.1 while using fewer steps and tool calls" ( @code ). Perplexity Computer (Pro/Max) and Search (Max) ( @perplexity_ai ). @AravSrinivas made it his "new default." Factory ( @factory ). Hermes Agent via Nous Portal and OpenRouter ( @Teknium ). Arena ( @arena ) and DesignArena ( @grx_xce ). Official model-selection guide. @ClaudeDevs published guidance on Fable vs Opus vs Sonnet vs Haiku. It covers when to raise effort instead of switching models, and when to push subagents to smaller models. Independent evals (facts) Artificial Analysis Intelligence Index v5 ( @ArtificialAnlys , breakdown ): Fable 5.2 is #1 at 65 (max) . Fable 5.2 (max) — Index score 65 Gemini 4 Carbon (high) — Index score 60 Opus 5.5 (max) — Index score 59 GPT-6 Astra (max) — Index score 57 Fable 5.1 (max) — Index score 49 New records: HLE-Diamond — Fable 5.2 80% · Previous best 69% AA-Omniscience v1.1 — Fable 5.2 67 · Previous best 54 Terminal-Bench-Science — Fable 5.2 73% · Previous best 65% CritPt v2 hard — Fable 5.2 77% · Previous best 72% FrontierCode 2.0 — Fable 5.2 49% · Previous best 46% (Opus 5.5) Weaker spots: AA-Briefcase: 1785 Elo, within the confidence interval of Opus 5.5 (1800) and behind Sonnet 5.5 (1813). GDP.pdf: 24% all-pass vs 26% for Opus 5.5. Terminal-Bench 4.0: 60%, level with Opus 5.5 and behind Kimi K3.1 Pro (67%), Gemini 4 Carbon (65%) and Sonnet 5.5 (64%). AutomationBench-AA: 76%, ahead of Opus 5.5 (70%) but behind Gemini 4 Carbon (78%). Efficiency: At high and xhigh it scores 62 using about 98k output tokens per task, vs 173k for Opus 5.5 max. At max, cost per task is about $26.5, roughly 2.6× Opus 5.5 ($10.0) and 2× Fable 5.1 ($12.99). Epoch Capabilities Index ( @EpochAIResearch ): a record 174

Latent Space · 10 thg 11, 2026

Nguyên văn nguồn
Chi tiết nguồn
20

Introducing Arete-27B: Qwen3.8-27B, post-trained to reinforce Western values.

34.8

Thử nghiệm thực tế nousresearch

Introducing Arete-27B: Qwen3.8-27B, post-trained to reinforce Western values. Chinese open models are currently the strongest available, but they ship with state-aligned behavior in the weights. We built an 803-prompt eval across seven value categories, including freedom of expression, democracy, and privacy, and measured how often a model adopts China’s party line. After fine-tuning on roughly 53 million tokens, Arete-27B's propaganda rate fell from 22% to 1%, in line with the Western models we tested. Its Hermes Bench score shows no significant performance tradeoffs. The values in an open model are one fine-tune away. Our eval, weights, and training data are available now along with the full blog post: http://nousresearch.com/arete Media

X · 7 thg 11, 2026

Nguyên văn nguồn
Chi tiết nguồn
21

We’ve been hard at work trying to make models work with harnesses better. The best thing @yb2698 found: “harness adapters”. Small LoRAs trained with RL inside the actual agent harness they’ll be used

34.2

Thử nghiệm thực tế lysandrejik

We’ve been hard at work trying to make models work with harnesses better. The best thing @yb2698 found: “harness adapters”. Small LoRAs trained with RL inside the actual agent harness they’ll be used with. Same base model. Different adapter for pi, opencode, hermes, etc. Why? Simply because the same model behaves very differently depending on the tools, prompts and control flow around it. Instead of asking one set of weights to be optimal everywhere, we can specialize a tiny part of the model for each environment. Early results are pretty encouraging: on held-out tasks, the adapters make fewer tool calls than the base model while keeping or improving accuracy. And because they’re LoRAs, the operational side is surprisingly cheap too. For one LFM2.5-24B-A2B experiment, we evaluated 9 checkpoints / 1,350 agent sessions on a single H200 in under an hour. The total: ~$5! Merging and serving every checkpoint separately would have cost around $90. There’s another important piece: RL agents will eventually try to hack the reward. So every tool call goes through `safeagents`, a deterministic rule-based guard that blocks things like editing tests, tampering with rewards or bypassing the sandbox before they execute. And the whole loop can start from real usage: your coding sessions -> verifiable environments -> RL -> a better adapter for your agent. The model doesn’t have to change completely. Sometimes it just needs to get better at the harness it actually lives in. https://huggingface.co/blog/harness-hub/harness-adapters Media

X · 6 thg 11, 2026

Nguyên văn nguồn
Chi tiết nguồn
23

I recently tried out the Gemini assistant in the new Volvo cars (my posts are never sponsored btw), and the wife and I couldn't stop laughing, you'll see why at the end. Here goes:

32.7

Thử nghiệm thực tế giffmana

I recently tried out the Gemini assistant in the new Volvo cars (my posts are never sponsored btw), and the wife and I couldn't stop laughing, you'll see why at the end. Here goes: lucas> oh cool it has gemini. gemini is good with voice, let's try. [I turn it on] We start driving. lucas> Please open passenger side window gemini> Sorry I can't do that (safety reasons) bruh lucas> ok then please turn on seat massage gemini> you need to install and configure the youtube app for that lolwut?! I later found out that this specific car model version didn't have seat massage (another one has) but... Gemini should just know and tell us! lucas> It's getting a little cold, can you fix that? gemini> No matter how cold it is outside, I always get warmth from our friendship lolwut :D I'm not making this up, I swear! But what is going on here I didn't even mean to stress-test it. The first two queries I tested on an XPeng a few weeks earlier and both worked fine. FWIW I think the real Gemini model with the right system prompt should nail these; I think it's whatever Google team does the port to car system that's not doing a good job.

X · 6 thg 11, 2026

Nguyên văn nguồn
Chi tiết nguồn
24

Formally verifying agent-written full-stack web apps with PDD Kit

32.3

Thử nghiệm thực tế Alex Lavaee, Matthai Philipose

At a glance Formal methods for everyday software. PDD Kit helps you turn your intent into a formal spec, then proves the code your agent writes for every input and uses tests where a proof can’t reach. It takes formal methods beyond niche, specialist work to engineers without a formal methods background and to everyday applications, like the full-stack web app shown here. Exhaustive line-by-line human review can become difficult to scale as AI agents generate increasingly large amounts of code. The plan is supposed to be the contract between you and a coding agent, but nothing actually forces the agent to follow it. The tests it writes usually check what it built, rather than what you asked for. PDD Kit makes the agent keep the plan. It works with you to turn your intent into a formal specification in Verus (opens in new tab) , proves the agent’s code meets that spec for every input, and falls back to tests where a proof can’t reach. We tried it on a full-stack web app. Inside GitHub Next’s Chopin (opens in new tab) , we used PDD Kit to formally verify the login logic of Pet Store, a Rust (opens in new tab) storefront. Verus hardened the code and uncovered existing bugs, proving the absence of login bugs with respect to the specification. The developer reviewed the intent and never read the generated code line-by-line. The plan is the contract the agent should follow, but nothing constrains the agent to follow it. Coding agents now ship whole features in one sitting often spanning tens of thousands or hundreds of thousands of lines of code. As a result, reading every line of the pull request doesn’t scale to this new way of work. Now, most teams invest in the plan and relevant testing instead: describe to an agent what they want, go back and forth until the plan and proposed tests look right, and hand them off to the agent for implementation. This plan or natural language spec is meant to be the contract that an agent holds. However, in practice, the agent can drift from it. It implements something slightly different, then writes tests that pass for its implementation rather than the code you intended it to write. Continuous integration (CI) grows due to a profusion of low quality and high quantity of tests, coverage looks healthy, and the gap between what you asked for and what shipped stays hidden until a bug report or a nasty edge case shows up. So, how do you reliably scale review as agents generate increasingly large amounts of code? Agent code fails in two ways a careful reviewer would usually catch: it leaves out something obviously necessary, or it does something obviously wrong. Tests alone don’t close that gap, because they only exercise a tiny slice of what a program can do. Closing it needs a different kind of machinery, which is where proofs come in. Review asks “does this look right?” A proof answers “is this right?” A mathematical proof shows that code meets its specification for every input, including the ones your test suite can miss. That provides stronger assurance for specified properties than testing alone, especially when line-by-line review isn’t practical. Proofs used to be too expensive for everyday software. You needed specialists, unfamiliar languages, proofs many times larger than the code, and proofs took years to develop, but two things have changed since. First, recent advances in coding agents have made it increasingly practical for them to help generate formal proofs from well-defined specs. Secondly, agents can now better help you write formal specs. We call this new software development paradigm Proof-Driven Development (PDD). PDD Kit is our toolkit for it. How PDD Kit works PDD Kit is to formal methods roughly what Spec Kit (opens in new tab) is to Spec-Driven Development. It runs as a partner inside Chopin (opens in new tab) , GitHub Next’s real-time, multiplayer planning environment, where a team and agents can plan in one shared document. The workflow has two halves (Figure 1). First, team members review intent in plain language. PDD Kit asks the questions a careful reviewer would ask, explains the relevant code as it goes, and records the answers in an intent artifact , a document that bridges the user’s intent with the formal specification or tests. The parts of the user’s intent that can be formalized are converted into formal specifications and the rest, which must be taken on trust, are converted to informal specifications for tests. PDD Kit automatically generates proofs that the code satisfies the derived formal specs and high-quality tests for the informal specs. You don’t need a formal methods background for any of it. Figure 1. Proof-Driven Development with PDD Kit. Team members settle intent. Verus and the test suite hold the code to it. Consequently, every result in PDD Kit says which kind of verification it rests on: Formal verification is a mathematical proof that code satisfies its specification for every possible input, checked by a tool called a verifier. For PDD Kit today, that verifier is Verus (opens in new tab) , a proof language for Rust co-developed by Microsoft Research, Carnegie Mellon University, VMware Research, ETH Zurich, MPI-SWS, UNSW Sydney, the University of Texas at Austin, the University of Michigan, the University of British Columbia, the University of Wisconsin–Madison and the Weizmann Institute of Science. Empirical verification checks code by running it and observing what it does. It covers what a proof can’t reach, such as a third-party cryptography library or a user interface. It uses unit and end-to-end tests, terminal automation, browser agents, and computer-use agents for anything a browser can’t drive. A passing test only shows the code worked on the inputs it tried, so PDD Kit labels it as evidence rather than proof. The line between the two is the Trusted Computing Base (TCB) : the code that the proof assumes behaves as described. PDD Kit makes that line explicit and asks you to sign off on each piece. T

Microsoft Research · 5 thg 11, 2026

Nguyên văn nguồn
Chi tiết nguồn
19–24 / 33
Trang 4 / 6