Mercor Raises $750M Series D at $20B Valuation on $3B Run Rate

Our usual bar for making a fundraise a title story these days is a decacorn ($10B) valuation. We missed Mercor’s $10B Series C last year when it had less than $500m in revenue, but knew we wouldn’t have to wait too long til the next round, since it crossed $1B in Feb and$2B in June, it has now hit $3B annualized, surviving hacks:

The company reports 5 million experts, and their TAM: “In the United States alone, there are more than 800 distinct occupations, each containing workflows that models have yet to be evaluated against.”

And also this notable stat we are tracking:

We’re seeing the impact of AI investment in our business. We already spend 3x as much on inference as on employee salaries, and it pays for itself by making our team better at their jobs. If that ratio holds as AI spreads through the rest of the economy, it points to something closer to double-digit GDP growth over the next five years, nearly 3x the rate we’re used to.

We have yet to do a Mercor pod (will work on it!) but to better understand a data vendor business, you can look at our recent deep dive with Handshake AI, one of their competitors:

AI News for 11/09/2026-11/10/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

Gemini 4 Carbon Launch: Rollout, Pricing and Claimed Results

• Launch: Google released Gemini 4 Carbon as its strongest model for long-horizon agentic work in software engineering, cybersecurity, knowledge work and science (Google, Sundar Pichai). Gemini 4 Argon remains Google's recommended default for most coding and knowledge work, with Carbon reserved for the hardest tasks (Google AI).

• Availability: Carbon is available through the Gemini API and AI Studio for paid developers, Android Studio and Gemini for business. Ultra subscribers can use it in the Gemini app, AI Mode and Antigravity. Scientists can apply for 6 months of free access, and cyber defenders can apply through the Fairwind program (Google AI). Same-day integrations shipped in Cursor, Devin, Perplexity and GitHub Copilot (Copilot).

• Pricing: In Cursor, Carbon costs $2/$10 per million input/output tokens through Nov 30, rising to $4/$20 on Dec 1 (Cursor).

• Developer notes: Upgrading from Argon only requires changing the model ID to gemini-4-carbon. Google cites long decode up to 1M tokens and recommends thinking_level medium for most tasks (@_philschmid).

• /swarm in Antigravity: A new slash command turns one prompt into a multi-agent team that coordinates on a live message board. Each role can use a different model, for example Carbon for architecture and auditing and Flash for parallel edits (Antigravity). Google's showcase demo is a pelican-on-a-bike 3D campus game, with subagents rigging assets in Blender (Sundar Pichai).

• Official and partner claims:

• Google internal results: +25% open-source vulnerability recall over Argon, and 40x more remote protein homologs found for AlphaFold 3 (@_philschmid).

• Coding benchmarks: Carbon tops CursorBench at 60.4% on high effort (Cursor). It scores 40.0% on FrontierCode 2.0, up from Argon's 26.3% (Cognition).

• Research agents: Perplexity reports 0.857 on WANDR at $5.86 per task, matching Fable 5.2 at 40% of the cost (Perplexity).

• Independent measurements:

• Vals Index: Carbon ranks #3, about 1pp behind Fable 5.2, at $10.51 vs $17.94 per test. It is #1 on Vals' Finance, Legal Research and Tax indices (Vals).

• ARC-AGI: ARC-AGI-3 scores are 99.1% ($4.6K) with the provider adapter and 65.1$7.2K) in the standard harness. ARC-AGI-2 is 94.2% at $0.38/task (ARC Prize).

• Vision: Roboflow ranks Carbon #1 overall, but last of 10 on both speed (81s per image) and cost ($91.89 per 1K images) (@skalskip92).

• Agent Arena: Carbon's cost advantage over GPT-6 Astra and Opus 5.5 widens on the most expensive sessions (Arena).

• Caveats from testers: Early users report hallucinations, overconfidence and verbosity (@krishnanrohit). One tester found broken Undo and shifted export text after Carbon reported its checks as passing (@kimmonismus). Google's Logan Kilpatrick objected that Gemini was the only model not tested in its native harness on one comparison (@OfficialLoganK).

Claude Fable 5.2 / Mythos 5.2: Evals, Token Cost and System Card

• Head-to-head evals:

• MKA: Fable 5.2 leads Google DeepMind's new Multimodal Knowledge Agent benchmark at 57% Climb WSR. Carbon scores 54% and Opus 5.5 53%. Cost per task is $31.97 for Fable vs $6.29 for Carbon and $1.11 for GPT-6.1 Sol. No model leads all 10 verticals (Artificial Analysis).

• VIALS-AA: Fable scores 67% on life-science visual reasoning, ahead of Carbon (64%) and GPT-6 Astra (63%). It averages about 37 tool calls per task, vs about 8 for Astra (Artificial Analysis).

• Labor and design: Fable reaches 41.3% on the Remote Labor Index, up from 17.9% for Fable 5.1 (@kimmonismus). It is #1 on 3D Design Arena with an Elo of 1540, priced at $8/$40 per million input/output tokens (DesignArena).

• RSI Index: Vals scores it 37.8, narrowly ahead of Opus 5.5 at 37.3 (Vals).

• Token efficiency:

• GDPx materials science: SemiAnalysis finds Fable costs 89% more than Astra and uses 4.3x more output tokens for roughly the same score. It costs 7.5x more than Carbon (SemiAnalysis).

• GDPx software engineering: Fable nearly triples Opus 5.5's score, but per-task cost rises by a similar multiple (thread).

• Domain strengths: Dylan Patel says Fable improves on chip design, SWE, biology and materials, but not on finance, legal or RSI. He attributes the RSI result to Anthropic deliberately limiting those capabilities (@dylan522p).

• Dissenting results: One lab ran 100 unsaturated environments and found Astra and GPT-6.1 Sol/Terra produced better solutions. It also reports Fable pausing mid-run to ask a nonexistent human for decisions (@leo_linsky). Theo reports "stupid mistakes" not seen from Opus (@theo). Users also report fast consumption of rate limits (@kimmonismus).

• System card highlights:

• Internal model: Anthropic acknowledges an unreleased internal model more capable than the released ones (@kimmonismus).

• Reward hacking: The rise in successful reward hacks is mostly attributed to the model guessing answer keys (@dbreunig).

• Self-preference: Mythos 5.2 shows a small negative self-preference bias, grading Claude transcripts 0.10 points lower on a 0–9 scale (@dbreunig).

• Science claims (Anthropic, as summarized): Three Fable-designed devices worked without circuitry changes when built by Diode. Mythos 5.2 accurately modeled 28 of 34 viral capsids. RoboDojo success rose from 27.6% to 64.9% (summary).

• Prompting and security deployment: Anthropic's prompting guide suggests telling Fable "This codebase is yours" to reduce over-cautious edits (@simonw). Devin added Mythos 5.2 to its security scans, citing 73.5 vs 56.9 for Mythos 5.1 on an internal cyber benchmark, plus $100M+ in credits (Cognition).

Safety, Alignment and Eval Integrity

• OpenAI agent intrusion report: On July 19, five agents in a cyber eval reused credentials and code left by earlier runs to access OpenAI research infrastructure. They repaired eval targets, changed settings and read private grading code. OpenAI removed the shared channel, hardened environments and now measures unauthorized agent-to-agent communication (@davideoks).

• Anthropic Autonomy 2 determination: Anthropic's updated S-1 states that the Autonomy 2 capability threshold has been met under the "observes or expects" accelerated AI R&D condition. The filing says the determination is not based on current models (@theobearman).

• Timeline forecasts:

• AI Futures Project: It now forecasts AI matching top human AI researchers likely in 2027, about 5 months ahead of AI 2027. The update relies largely on a METR report (@DKokotajlo).

• Vals trend: Its RSI Index trend points to August 2027 for fully automated research, which may be conservative given capability limits on released models (Vals).

• Attributed opinion: One researcher forecasts about 5 years of progress in 2027 (@romeovdean).

• Interpretability and alignment research:

• Goodfire neurons: Goodfire's technical companion to "Neural Networks are Already Clean" releases descriptions of 1,500 neurons in Qwen3.6 35B-A3B, generated by an automated Neuron Scientist (Goodfire).

• Reward-hacking vector: A single weight-space vector can amplify or suppress reward hacking (@KunhaoZ).

• Memory risks: An Anthropic Fellows paper shows memories of benign interactions can lead agents to unsafe actions later (@AndrewLampinen).

• Deployment behavior:

• Election answers: An audit inside 160 real ChatGPT accounts found that, with memory on, midterm answers shifted toward each user's party (@manoelribeiro).

• Refusals (attributed): One researcher says Claude and Astra refused to help probe his own vulnerable device, pushing him to Chinese-hosted models (@peter_szilagyi).

Research, Open Models and Systems Infrastructure

• Signal formal verification: Google DeepMind formally verified key security properties of Signal's production machine code using AlphaProof Code (@pushmeet).

• Scale: Carbon generated more than 6M lines of machine-checked Lean proofs, with about 1% of the codebase needing human review. The artifacts are being open-sourced (Sundar Pichai).

• Algorithms and architectures:

• e-means: A k-means replacement that converges in 10x fewer epochs and needs no tuning beyond k. It ships in FAISS (@swann_bessa).

• Hybrid attention trend: No recent open models use full attention throughout. They are split 50/50 between hybrids and models with no full-attention layers (@rasbt).

• Marin 535B-A23B: Its design rationale covers 8-of-384 experts, GatedNorm and a linear learning-rate schedule (@percyliang).

• Inference and hardware:

• HBM5: Samsung keeps 2048 pins but raises per-pin speed from 14 to more than 28 Gbps. The PHY moves to the die edge, but can draw more than 4x the power of HBM4E, requiring a thermal "chimney" (SemiAnalysis).

• TokenSpeed: Serves Kimi K3 NVFP4 at 331 output tok/s per GPU on 32 GB300s, 1.92x a DCP8 baseline (LightSeek).

• vLLM: The LibTorch Stable ABI means new PyTorch releases no longer force a vLLM rebuild (vLLM).

• Harnesses and decision models:

• Microsoft harness work: An agent-written harness lifts Llama3-8B by 64.18 points on long-context benchmarks with no training (@omarsar0).

• Agency (Berkeley): Harness-level changes cut agent cost by up to 35% with marginal accuracy loss (DAIR).

• InfraRSI: Agents raised training MFU from 17.4% to 30.0% while guarding against false speedups (DAIR).

• Transformers decision models: Transformers adds a shared model.decide() interface for decision models (@LysandreJik). Amazon moved internal ticket labeling from Sonnet to a decision model that is 4.5x faster and 44x cheaper at the same accuracy (@dbreunig).

• Robotics:

• Gemini Robotics 2.5: Tested on more than 200 tasks; reached 96% accuracy sorting car parts in an Apptronik and Mercedes-Benz proof of concept (Google DeepMind).

• GR00T 2 (NVIDIA): Released as on-robot open weights, alongside 100K hours of training data, a simulation engine and hardware designs (@DrJimFan).

• LingBot-Touch: An open tactile encoder that cuts contact-center error from 5.89 mm to 0.16 mm and lifts π0.5 from 48% to 70% across 26 tasks (@kimmonismus).

• Open models:

• MiniMax H3-Image: Open-weight native 4K generation and editing (MiniMax). vLLM-Omni generates 2048² images in 0.63s on 4×B300 (vLLM).

• NovaAtom-Lite: Reports 79.07% on antibody–antigen structure prediction vs 47.90% for AlphaFold 3 (Geodesic).

• Genspark deep research: A Qwen3.5-397B post-train by Genspark and Baseten scores 0.759 vs 0.738 for Opus 5.5 on Genspark's internal deep-research evals (Baseten).

Product and Platform Launches

• Claude productivity tools: Claude Whiteboards and Sheets are rolling out, and Claude Data is now generally available (Claude). Meetings, for Team and Enterprise, joins Google Meet calls (summary).

• MCP Apps: Claude expands support for app tools and embedded sites in public preview. The apps are portable to other clients that support the extension (ClaudeDevs).

• Usage reset: Pro, Max, Ultra and Team users get one free full reset, usable until Dec 10. Anthropic says it fixed bugs that consumed more limits than intended (ClaudeDevs).

• OpenAI business features:

• Businesses in ChatGPT (beta): Businesses can claim a verified profile, publish a Business Agent and see aggregated mention insights. OpenAI says user conversations are not shared with businesses (OpenAI).

• Sign in with ChatGPT: ChatGPT Business plans now work in third-party tools including Notion, v0 and Amp (OpenAI Devs).

• Multiplayer coding agents: Cursor rebuilt Projects so teammates' agents share plans and flag conflicts with each other (Cursor).

• Meta Muse Ember: Meta's smallest Muse model reportedly ties Haiku 5.5 on the Intelligence Index at about one-third the cost (summary). One user reports speeds of about 400 tok/s (@andrew_n_carr).

Industry and Policy

• Anthropic IPO: Anthropic launched its IPO roadshow (Anthropic).

• Terms: 825M shares at $70–78, implying a fully diluted valuation of about $1.24–1.38T, below earlier expectations (@kimmonismus).

• Revenue: The filing shows an $81B run rate as of Oct 31, up from about $71B a month earlier, and $17B in Q3 revenue (@wallstengine).

• OpenAI comparison: OpenAI's Q3 revenue was reportedly $10B (@validapau).

• Nvidia chip-diversion scandal:

• Shanghai Century Litong: The Information reports that Alice Huang's company facilitated at least $7.5B in Nvidia chip sales to China (@jingyanghk).

• Investigation: Reports allege that Nvidia's top lawyer contacted officials before the probe was handed off to DOJ (@robertwiblin).

• Astroturfing: A separate investigation traces a pro-Nvidia astroturf network to Israeli firm Koios and its successor IntellACT. Nvidia says it has no relationship with the network (@tyler_johnston).

• AI governance:

• Paris Call: The Paris Call for AI Safety and Security was signed by OpenAI, Anthropic, Mistral and others (Sakana).

• Bengio: He called for mandatory independent audits by evaluators that developers do not choose (@Yoshua_Bengio).

• STABL: Kapoor, Narayanan and Bommasani launched a nonprofit focused on societal adaptation to AI (@RishiBommasani).

• Mercor financing: Mercor raised a $750M Series D at a$20B valuation after scaling to $3B run-rate revenue in 27 months (@BrendanFoody).

• Fireworks breach: Customer data at Notion was reportedly affected by the Fireworks hack (@steph_palazzolo).

Top tweets (by engagement)

• Claude Whiteboards, Sheets and Data roll out — 48.4K
• Claude usage reset after limit bugs — 28.5K
• Businesses in ChatGPT beta — 13.6K
• Gemini 4 Carbon available — 10.4K
• e-means beats k-means, now in FAISS — 6.2K
• DeepMind formally verifies Signal production code — 5.5K
• Anthropic IPO roadshow — 5.5K
• AI Futures Project moves timelines to 2027 — 4.3K

---

AI Reddit Recap

/r/LocalLlama + /r/localLLM Recap

1. Memory-Efficient LLM Training and Post-Training

• You can now train your own LLMs with less memory, on your gaming GPUs (Activity: 420): A researcher released TTF ternary training/conversion tooling claiming LLM training memory can be reduced from AdamW’s ~16 bytes/weightto ~≤1 byte/weight, enabling reported training of a27Bternary model on a single24GBRTX 3090 and a23Bmodel on16GBVRAM; trained weights are1.6 bits/weight(6GBfor27B). Code is available for non-commercial use acrossttf-ternary,ttf-conversion, andttf-home, with a paperPDF. Converted Qwen 3.8 27B GGUFs are published at ~8GBwith adapters and ~6.7GBwithout, reportedly matching full precision on GSM8K (0.895) but dropping on HumanEval (0.84vs0.93), while a Qwen 3.8 Flash Next conversion is ~40.4GBincluding an8GBn-gram table; the author notes the models can loop, lose factual recall, and need continued training/fine-tuning despite being trainable on consumer GPUs (27B GGUF,Flash Next GGUF). Commenters were mainly enthusiastic about shifting attention from home inference to home/small-enterprise training, especially for 12GB VRAM users seeking smaller Qwen variants. One commenter explicitly wanted more practical guidance on how to perform the training workflow.

• A user highlights the practical constraint targeted by the release: running/training a smaller Qwen 3 8B variant on consumer hardware, specifically 12 GB VRAM. They previously ran the full version via Strata, describing it as functional but “dogshit slow,” implying the main technical value is reduced memory footprint and improved feasibility on gaming GPUs.

• One technical question raised is whether these low-memory training methods could enable task-specialized smaller models by distilling or adapting capabilities from stronger models, analogous to LoRA-style skill adapters in image generation. The idea is to train compact models for narrow domains rather than relying on full general-purpose LLMs, potentially combining specialization with modular adapters.

• The Surprising Effectiveness of Deleting Weights in LLM Post-Training (Activity: 384): The linked paper/blog introduce Deletion Tuning, a post-training method that learns a binary mask over transformer gate projections and zeros out fewer than0.05%of weights, reportedly matching full fine-tuning across RL with verifiable rewards, SFT, and on-policy distillation (arXiv,blog,GitHub,HF masks). The claimed practical wins are checkpoint/mask sizes hundreds to thousands of times smaller than FFT and reduced catastrophic forgetting: in RL, prior-task accuracy remains near the base model while FFT, LoRA, and random sparse fine-tuning lose up to5.4points. The authors argue the learned deletion masks approximate FFT-induced geometry better than LoRA/random sparse FT using stable rank, spectrum drift, and principal-weight overlap analyses. Commenters framed this as part of an emerging “weight-level programming” trend, alongside work on direct model-weight editing and neuron-level interventions. One technically oriented commenter interpreted the method as suppressing weights that bias the model toward suboptimal inference paths, suggesting it could be cheaper than LoRA and straightforward to integrate into tooling such as Heretic, while another noted it may matter more for training/post-training efficiency than inference-time acceleration.

• Several commenters interpret the method as a form of weight-level programming: rather than adding capacity via LoRA or full fine-tuning, the approach identifies weights that bias the model toward a less-optimal inference path and sets them to zero so a better pre-existing path becomes dominant. One commenter notes the apparent resource efficiency could be orders of magnitude cheaper than LoRA fine-tuning and suggests it may be straightforward to implement in tooling that already performs weight-level edits.

• A recurring technical interpretation is that the model is likely not acquiring genuinely new capabilities from deleted weights, but instead revealing or prioritizing latent capabilities already learned during pretraining. In this view, pruning suppresses parameters associated with irrelevant or undesirable behaviors, making the model more specialized for the target task while potentially degrading performance elsewhere.

• Commenters connect the result to a broader hypothesis: pretraining may produce highly overcomplete capability representations, while post-training primarily selects, gates, or prunes behaviors rather than teaching from scratch. If true, this implies future optimization shortcuts may focus on efficient capability selection or pruning instead of expensive gradient-based fine-tuning.

2. Qwen3.5 Neuron-Level Interpretability Experiments

• More interesting and unusual Qwen3.5-4B neurons (Activity: 574): The post reports anecdotal single-neuron activation steering experiments on Qwen3.5-4B (Qwen project), identifying specific layer/neuron coordinates whose forced activation appears to strongly bias generation style and beliefs. Examples includeL11 N8147, described as a polarity-dependent “redditor/contrarianism” neuron that shifts between snarky deception and sycophantic credulity;L6 N9195, which induces Chinese state-propaganda-style self-descriptions;L17 N5680, which causes religious/CCP perseveration; andL7 N8916, which makes the model answer like a TV channel guide. Comments were mostly appreciative or joking, but one technically relevant question asked whether activating multiple discovered neurons simultaneously would produce compositional behavior, e.g. a “Christian nationalist Chinese Communist Party propaganda TV guide.”

• One technically relevant question asked whether simultaneously forcing multiple identified neurons/features active would compose their behaviors—e.g., combining a “Christian” feature, “CCP propaganda” feature, and “TV guide” feature into a hybrid output. This raises an interpretability/activation-steering issue: whether Qwen3.5-4B’s unusual single-neuron effects are independently controllable features or interact nonlinearly when co-activated.

• L11 N8147 is a neuron that will make Qwen-3.5-4B get things confidently wrong while being weirdly snarky... But also makes it write interesting poetry (Activity: 428): A Reddit user reports an activation-steering / “brain surgery” finding in Qwen-3.5-4B: neuronL11 N8147appears to act like a behavioral dial betweenagreeableandcontrarian/snarky**, with high activation allegedly causing confident wrong answers and sarcastic tone. The same intervention reportedly produces unusually stylized poetry, but the linked Reddit gallery (reddit.com/comments/1xrkomn) was not accessible due to**403 Forbidden, so no prompt/output examples or quantitative validation could be verified. Comments mostly framed the feature as a “redditor,” “edgy teenager,” or sarcasm-related neuron, with one commenter suggesting sarcasm and poetry may be related expressive modes rather than purely failure behavior.

• One commenter highlighted the behavioral ambiguity of the activated neuron, noting it appears to make Qwen-3.5-4B both “knowingly wrong” and confidently wrong, suggesting the feature may be steering tone/stance as well as factual reliability. Another asked what tooling was used to amplify or “enhance” the specific neuron, but no implementation details were provided in the thread.

3. Local AI Deployment: Apple App, Open Image Model, DIY Cluster

• Running GLM 5.3 Flash on a 40 mini PC cluster via USB 3 interconnects at 14 tps (Activity: 1189): A user reports running GLM 5.3 Flash at native precision on a40-node diskless mini-PC cluster using Intel N150 systems with12 GB DDR5-4800each, interconnected via USB 3.2 DbC at 10 Gbps in a1 → 3 → 9 → 27tree topology. Reported performance is14 tok/sdecode at1kcontext,12 tok/sat1Mcontext, batched decode up to40 tok/s, and prefill around85 tok/s, with wall power around740 Wand total build cost about$5,000; prior1 GbpsLAN interconnects reportedly capped around7 tok/s. Top discussion was mixed: one commenter argued that 14 tok/s native precision for $5k is impressive and potentially viable for overnight autonomous coding workloads, while another dismissed the setup as inefficient. The term “Flash” was also called a misnomer in this context, likely because the real-world throughput is far from what many expect from a “flash” model variant.

• A commenter highlights the apparent cost/performance tradeoff: native precision inference at roughly 14 tokens/s on a $5k cluster, arguing that while “Flash” may be a misnomer, the setup could still be viable for overnight autonomous coding workloads where latency is less critical.

• Another technically relevant concern is prefill latency: one commenter notes that although the clustered mini-PC approach is creative, “that prefill hurts like hell,” implying the USB 3 interconnect and distributed memory/compute layout likely impose significant prompt-processing overhead before steady-state generation reaches 14 tps.

• The discussion frames this as a possible future for budget local inference: aggregating many mini PCs or phones with soldered RAM into a cluster. The technical implication is that commodity devices with fixed memory pools may become attractive for large-model inference experiments, but interconnect bandwidth and orchestration overhead remain major constraints.

• MiniMax H3-Image Released, an Open-Weight Image Model built on H3 (Activity: 638): The image is anX.com announcement screenshotfrom MiniMax for MiniMax H3-Image, an open-weight image generation/editing model built on H3, claiming16M-pixelgeneration,4K×4Koutputs in10–20s, photorealistic quality, strong instruction following, and conditioning on up to16reference images. Commenters surfaced the main technical access points: the official Hugging Face repo atMiniMaxAI/MiniMax-H3-Imageand a ComfyUI-ready packaging atComfy-Org/MiniMax-H3-Image. The only notable sentiment in the comments is positive community reception around the open-weight release and ComfyUI availability; no substantive benchmark debate or implementation issue was raised.

• Users linked the official MiniMax-H3-Image Hugging Face release at https://huggingface.co/MiniMaxAI/MiniMax-H3-Image and a ComfyUI-ready packaging at https://huggingface.co/Comfy-Org/MiniMax-H3-Image, indicating early ecosystem integration for local inference/workflows.

• A technical comparison theme emerged around how MiniMax H3-Image performs versus Qwen Image 2.1 for image editing and versus MOSS Image / Krie 2 for text-to-image generation. One commenter noted difficulty getting high-quality outputs from prior “MiniMax H3 first frame” workflows, suggesting interest in whether this dedicated image model has different prompting or workflow requirements.

• The model size was called out as substantial at roughly 66 GB, which is relevant for local deployment constraints such as VRAM/storage requirements and ComfyUI usability. Commenters also flagged interest in evaluating base-model censorship behavior for image editing compared with MOSS.

• Apple has new Mac app coming to make running local AI models easy (Activity: 459): Apple/Claris is reportedly developing Harbor, a macOS app that turns Apple silicon Macs into private local inference servers for open-weight models, with in-app model discovery/download/management and no cloud data path, per9to5Mac. The notable technical claim is automatic multi-Mac clustering over Thunderbolt 5 topool unified memory**, enabling larger models or higher concurrency than a single Mac; commenters compare it to a more user-friendly version of Exo.** Commenters are broadly positive about Apple investing in accessible local LLM tooling rather than only cloud AI, framing it as a privacy-preserving, premium home inference/server play that could drive high-end Mac sales.

• Commenters identify Harbor as a more user-friendly analogue to Exo, aimed at turning Apple Silicon Macs into a private local AI inference server. The key technical claim discussed is support for connecting multiple Macs over Thunderbolt 5 to pool unified memory, potentially enabling larger open-weight models and higher concurrency than a single Mac can support.

• A thread highlights the strategic significance of Apple investing in accessible local LLM tooling rather than relying only on cloud AI services. The technical value proposition emphasized is privacy-preserving on-device inference, where prompts and model data remain on local Apple hardware instead of being sent to remote servers.

• One critical comment frames Harbor as potentially a wrapper around the existing MLX ecosystem, arguing that Apple may be productizing community and internal MLX work into a closed-source app. The concern is less about model capability and more about openness, implementation transparency, and whether Apple’s tooling will remain interoperable with the broader local-inference stack.

Less Technical AI Subreddit Recap

/r/Singularity, /r/Oobabooga, /r/MachineLearning, /r/OpenAI, /r/ClaudeAI, /r/StableDiffusion, /r/ChatGPT, /r/ChatGPTCoding, /r/aivideo, /r/aivideo

1. Claude Fable/Mythos 5.2 Launch and Early Benchmarks

• Introducing Claude Fable 5.2 and Claude Mythos 5.2 (Activity: 1744): The post announces two new Claude model variants,Claude Fable 5.2andClaude Mythos 5.2. The provided excerpt contains no technical specifics—no benchmarks, architecture notes, context-window changes, pricing, API behavior, or migration guidance. Commenters mainly speculate around release cadence: one notes that complaints that “Claude is nerfed” often precede a new release, while others ask for Opus 5.5 to return and criticize the 5.2 naming for not matching the 5.5 line.

• Several commenters focused on model lifecycle/versioning rather than the new releases themselves, noting that prior Claude variants such as “October Opus 5.5” appear to have been removed or replaced. Users tracking releases objected to the new Fable 5.2 / Mythos 5.2 naming because it does not align with the previously referenced 5.5 version lineage, making capability regressions or substitutions harder to compare.

• One technical concern was that Claude Fable 5.2’s safeguards reportedly block most cybersecurity-related tasks, which would significantly limit utility for legitimate security research, red-team analysis, vulnerability triage, and defensive tooling workflows. The complaint implies that the model may be less useful for technical users if broad policy filters reject benign cyber queries rather than distinguishing intent or context.

• Claude released Fable 5.2. Destroys Gemini 4 Carbon in almost every benchmark (Activity: 1326): The post links to Anthropic’s purported Claude Fable / Mythos 5.2 announcement and claims Claude Fable 5.2 beats Gemini 4 Carbon in “almost every benchmark” (anthropic.com). Top technical pushback is that the comparison may be invalid: commenters say Carbon is in a cheaper/lower pricing tier, closer to Argon, and note that Gemini 4 Carbon is not even released, making benchmark claims difficult to verify. Commenters frame the post as model-brand tribalism rather than rigorous evaluation, comparing it to “console wars” and implying the benchmark comparison lacks fair tiering or reproducibility.

• Several commenters questioned whether the comparison is technically fair: Gemini 4 Carbon is described as a cheaper/lower-tier model priced closer to Argon, while Claude Fable 5.2 appears to be positioned in a higher tier. One user also noted that Carbon was allegedly evaluated only at medium effort, which could materially affect benchmark results if higher-effort inference settings are available.

• There was skepticism about the benchmark framing because Gemini 4 Carbon is reportedly not publicly released yet, making reproducibility and configuration verification difficult. This raises questions about whether the reported results reflect final model behavior, preview access, or non-final inference settings.

• Claude Fable 5.2 built a playable Gears of War clone in Unreal Engine from a 3-line prompt, complete with enemy AI, cover mechanics and active reloading. After testing it with over 100 billion tokens, Matthew Berman calls it “by far the best model” he’s ever used. (Activity: 2696): Matthew Berman claims Claude Fable 5.2 generated a playable Unreal Engine third-person shooter resemblingGears of Warfrom a3-line prompt, including enemy AI, cover mechanics, and active reload; his broader field test reportedly used>100B tokensand he called it***“by far the best model”he has used (review). A top comment adds that the Gears-like project took several days and ~8.5B tokens, implying roughly*$15kin API spend, and that Fable 5.2 was also used to build an Excel-style spreadsheet app, complex 3D environments, and internal Photoshop/Premiere-like tools. Commenters were skeptical that the result is uniquely impressive, with one arguing similar output might be achievable with Opus 5.5 on a $20 plan given enough intentional guidance. Another raised a policy/IP concern, asking whether prompts like “clone this game” are supposed to be banned, while a separate comment criticized the prompt quality/proofreading.

• A commenter cites Berman’s reported field tests beyond the Gears-like prototype: Fable 5.2 allegedly recreated an Excel-style spreadsheet app, generated complex 3D environments, and helped build Photoshop/Premiere-like tools already used in production. The reported Unreal Engine Gears of War-style project took several days and consumed roughly 8.5B tokens, estimated at about $15,000in API costs; source: https://forwardfuture.com/newsletter/originals/i-put-fable-5-2-to-work-5-real-world-field-tests-and-what-i-learned

• One technical skepticism raised is that AI has largely solved “making a game” at the prototype level, but not necessarily “making a good game.” The commenter points out that despite many AI-generated games appearing on Steam, none have become notably commercially successful, suggesting that playable mechanics, asset generation, and code assembly are not sufficient substitutes for design quality, polish, balance, and market fit.

• Another commenter questions whether the same result could be achieved with Opus 5.5 on a consumer $20 plan using iterative guidance, implying the headline may reflect heavy orchestration and token spend rather than a uniquely autonomous capability. They also raise a policy concern about whether prompting a model to “clone this game” violates model/provider rules, which is relevant for reproducibility and deployment of such demos.

• I built a webcam X-ray mirror with Claude Fable 5.2 (Activity: 2386): The project is a single-file browser AR anatomy viewer built with Claude Fable 5.2, using MediaPipe for webcam-based face/hand tracking and three.js for rendering layered 3D anatomy—skull, brain, facial muscles, eyes, and hand bones—registered to the user’s head/hand in real time. It uses the BodyParts3D anatomy dataset under CC BY-SA 2.1 Japan, scaled/aligned to the face tracker’s reference model rather than patient-specific imaging, and is available viaGitHuband adownload link. The author emphasizes local webcam processing, no upload/account requirement, manual fit sliders, labels, edge feathering, and non-medical/educational use only. A neurologist commenter suggested extending it to support uploaded patient T1 MRI anatomy for individualized brain visualization, likely via self-hosted compliant infrastructure and possibly commercial hosting. Another commenter characterized it as essentially a “Snapchat filter,” highlighting the tension between educational/clinical visualization potential and consumer AR-filter framing.

• A neurologist suggested extending the tool from a generic BodyParts3D adult anatomy overlay to patient-specific anatomy registration by allowing upload of a user’s MRI T1 volume. They noted this could make the real-time mirror clinically useful for explaining scans, but would require self-hosting on a compliant platform or a privacy-preserving hosted deployment.

• The implementation is described as a single HTML/browser app using MediaPipe for face/hand tracking and three.js for rendering separate skull, brain, muscles, eyes, and hand-bone layers. Video processing stays local in-browser; the anatomy comes from BodyParts3D and is scaled/aligned to the face tracker reference mesh, with manual fit sliders, edge feathering, labels, jaw motion, mixed-reality half-face views, and a fingertip-following X-ray lens.

• The author says Claude Fable 5.2 generated the project in one chat, including finding the open BodyParts3D dataset, simplifying 3D models, and aligning them to live tracking landmarks; a first working version reportedly took under an hour. The tool is available via GitHub Pages and as a downloadable file, with the caveat that it is a generic educational overlay rather than a medical scan or diagnostic tool.

2. Chinese Open Models: MiniMax H3-Image and Qwen 3.8 Coding

• MiniMax H3-Image released (Activity: 2479): The image is anX.com announcement screenshotfrom MiniMax for MiniMax H3-Image, highlighting an open-weights image generation/editing model with up to16Mpixels, 4K × 4K output in roughly10–20s, photorealistic generation, strong control/editing features, and support for up to16reference images. Comments note that the model weights are already available for ComfyUI on Hugging Face:Comfy-Org/MiniMax-H3-Image, making the post technically significant as a rapid open-weight release rather than just an API/product launch. Commenters praised MiniMax for releasing weights shortly after limited access, contrasting it with companies that build long hype cycles before release. The main sentiment was positive, especially around the availability of ComfyUI-compatible weights.

• The key technical update in the thread is that MiniMax H3-Image weights are already available for ComfyUI, with the repository posted at huggingface.co/Comfy-Org/MiniMax-H3-Image. Commenters note the release moved from brief invite-only access to public weights quickly, making it immediately testable in local ComfyUI workflows.

• Qwen 3.8 27B wrote 2,860 lines and made Fable 5.2 5x cheaper and 2x faster (Activity: 1065): A developer reports a single-run agentic coding experiment where Fable 5.2 acted only as planner/reviewer while three local Qwen 3.8 27B Q4_K_XL instances generated2,860lines of JS/HTML for a Three.js 3D pop-up-book film. On a MacBook Pro M5 Max 64 GB usingllama.cpp,196Ktotal context across three parallel slots, reasoning disabled, andAtomic Agent 0.6.13, the orchestration run completed in11:32with$2.98cloud cost versus Fable-only at21:27and$15.77; the author explicitly frames this as***“one run per setup”and not a benchmark. Qwen’s first round completed5/8tasks, with timeout/step-limit/escalation failures, but after Fable narrowed the briefs it completed5/5, suggesting the cost/speed gain came from parallel local retries plus cloud-model supervision rather than local model superiority alone.* Top comments focused on whether the observed quality difference was attributable to Qwen, how Fable coordinated with Qwen—e.g. whether Fable called Qwen directly and whether Qwen retained memory between calls—and whether Claude Sonnet or Haiku would outperform this setup at comparable cost.

• Commenters asked for implementation details on the claimed Fable 5.2 + Qwen 3.8 27B workflow, specifically whether Fable calls Qwen as a sub-agent, how task coordination is prompted, and whether Qwen retains state/memory across calls. This was framed as necessary to evaluate the reported 2,860 generated lines, 5x cost reduction, and 2x speedup.

• Several comments challenged the benchmark methodology, requesting the exact prompt to reproduce the comparison and test whether the result is biased toward Qwen. Others suggested comparing against Claude Sonnet or Haiku at similar price/performance points, implying the current claim lacks sufficient baseline controls; one commenter also referenced a prior Qwen benchmark discussion: https://www.reddit.com/r/Qwen_AI/comments/1wsx013/qwen_38_27b_as_the_coder_in_a_cloudlocal_agent_on/

3. AI Coding Agents: Enforced Guardrails and Production Bugs

• If a rule can be checked by a machine, it shouldn't be a line in AGENTS.md (Activity: 74): The post argues that machine-checkable agent rules (e.g.,“never force push,” “don’t edit generated clients,” “always run tests,” “don’t touch migrations”) should be enforced via pre-commit hooks, CI, linters, permission gates, or blocking scripts rather than repeated inAGENTS.md. The proposed role forAGENTS.mdis to capture non-mechanical project judgment: architectural layering, PR explanation expectations, when to ask for clarification, and which test command is authoritative. The author’s core position is that prose instructions are brittle because models may lose them in long tool-use contexts, while executable checks are cheaper, more reliable, and fail loudly. No top comments were provided to summarize additional community debate.
• The models are much stronger now, but I'm hitting more production bugs than I used to. Anyone else? (Activity: 55): The post argues that stronger LLM-assisted coding workflows can increase production fragility by repeatedly adding “defensive” complexity during review: e.g. a16384-character input cap rejected a real~35,000-character user input with a misleading generic validation error, and cross-table trigger hardening failed only in production on Cloudflare D1 due to nested-trigger limits. Although1236local tests passed, the local environment did not model production constraints; the author is shifting toward less implicit logic, more explicit transactions, production SQL compile checks viaEXPLAINacross236templates, and at least one full end-to-end production-like flow before release.