Google DeepMind 发布 Gemini 4 Carbon，先面向网络安全防御方开放

It’s a good thing we published our Opus 5.5 podcast calling it the world’s best model before today’s launch.

In a very pleasant surprise, Gemini announced Carbon, a newer frontier model than the 3 week old Argon, with fantastic benchmarks:

Taking it to the new #1 on the Artificial Analysis consolidated benchmark, putting GDM in the lead for possibly the first time in AAII history:

View post on X ↗

sd

AI News for 10/27/2026-10/28/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 Tops Independent Leaderboards, with Access Limited to Cyber Defenders

• Launch: Google DeepMind announced Gemini 4 Carbon two weeks after Argon. It is positioned as state of the art on cybersecurity and long-horizon tasks (@sundarpichai, @GoogleDeepMind).

  • Claimed cyber results: 88.2% on SEC-bench Pro for vulnerability finding, 54.8% on ExploitGym for exploitation and 71.0% on CWE-bench for patching (@sundarpichai).

  • Availability: Carbon first goes to trusted cyber defenders through the Fairwind Program, with wider developer access promised "as soon as possible" (@GoogleAI).

  • Pricing: Phil Schmid quotes $2/$10 per million input/output tokens with an asterisk (@_philschmid). Artificial Analysis lists $4/$20 standard pricing with a 50% launch discount that has no end date. Cached input costs $0.20 per million tokens (@ArtificialAnlys).

  • Specs: The model has a 1M-token context window and 1M max output. Inputs are text, image, video and speech; output is text (@ValsAI).

• Safety claims (Google): Successful cheating on Terminal-Bench 4.0 fell to 0.0%, and cheating attempts fell to 0.4%. Unsupported claims are down about 2x versus Argon. Overreach fell 26% and under-service fell 29% (@OfficialLoganK).

• Artificial Analysis: Carbon is #1 on Intelligence Index v5 with a score of 59. It leads 4 of the 9 index evals: HLE-Diamond, TB-Science, AA-Omniscience and AutomationBench (@ArtificialAnlys).

  • Coding: On the Coding Agent Index, Carbon scores 59 using Antigravity CLI, versus 62 for Claude Code with Opus 5.5 [max]. It scores 51% on FrontierCode v1.1, versus 56% for Opus.

  • Knowledge work: Carbon reaches 1609 Elo on AA-Briefcase, up 126 points from Argon. It still trails Grok 4.7, Muse Wonder and Kimi K3.1 Pro (1678).

  • Cost: Carbon costs $7.76 per index task, versus $10.04 for Opus 5.5 and $6.25 for GPT-6 Astra. It uses 123k output tokens per task, 29% fewer than Opus.

  • Hallucination: Carbon leads Omniscience with 54. Its hallucination rate rose from Argon's 4% to 11%, which is still the second lowest measured. Opus 5.5 and Astra are both at 50%.

• Other independent evals:

  • Arena: Carbon is #1 in Text Arena (1528), #2 in Agent Arena at a $1.80 median cost per task, and #4 in Code Arena: WebDev (1768) (@arena). Arena attributes the gains over Argon to more praise, more confirmed successes and better steerability (@arena).

  • Vals: Carbon is #2 on the Vals Index and #1 on the Finance Index and Legal Research Benchmark. It produces 64% more output tokens than Argon, mostly on finance, tax and legal tasks (@ValsAI, tokens).

  • Coding benchmarks: Carbon scores 61.2% on FrontierSWE, behind GPT-6 Astra (65.5), Opus 5.5 (62.3) and Sonnet 5.5 (61.9) (@ProximalHQ). It sets a narrow state of the art of 9.6% on SWE-sweep (@KLieret).

  • Andon Labs: Carbon is #1 on Vending-Bench 2 (@andonlabs). It is also #1 on Blueprint-Bench 2, where it ties the human baseline for 3D spatial understanding (@andonlabs).

• Caveats and reactions:

  • Harness: The coding-agent results were measured in Antigravity CLI, so results in other harnesses are untested (@Yuchenj_UW).

  • Hallucination risk: Some users are concerned about hallucination in cyber use (@scaling01).

  • Lab gap: scaling01 thinks Google remains about two months behind the next OpenAI and Anthropic releases (@scaling01).

• RSI framing: On the earnings call, Sundar Pichai said AI is increasing training and launch velocity. He expects "continued acceleration because of RSI" over the next twelve months (@AndrewCurran_).

  • Unconfirmed: Claims of a stronger unreleased Gemini model are not confirmed (@kimmonismus).

  • Internal workflow: A Gemini engineer describes overnight agent loops and swarms that inspect RL data. In that workflow, launches now feel like "periodic checkpoints" (@zhangqiaorjc).

Leaderboard Resets and Benchmark Integrity

• AA Intelligence Index v5: The rebuilt index runs 60% on private tests (@TheRundownAI).

  • Ranking before Carbon: Opus 5.5 scored 58, followed by GPT-6 Astra (57), GPT-6.1 Sol (55), Sonnet 5.5 (54) and GPT-6.1 Terra (51).

  • Open models: Kimi K3.1 Pro fell from 55 to 46. DeepSeek V4.1 Flash and GLM-5.3 both score 32, below Claude Haiku 5.5 at 36.

  • China–US gap: scaling01 puts the gap at about 3.3 months on the AA Progress Index (@scaling01).

• FrontierCode 2.0 mystery model: Cognition data includes a hidden "Obsidian 3" scoring 46.8%, versus 45.5% for Opus 5.5. Because it runs in the claude-code harness, some speculate it is Fable 5.5; this is unconfirmed (@kimmonismus).

  • DeepSeek correction: scaling01 corrected an earlier identification and said Artificial Analysis shows DeepSeek V4.1 Flash-1017 at about 28% (@scaling01).

  • Mixed sources: teortaxes notes that Cognition's chart mixed model-card scores with independently measured ones (@teortaxesTex).

• Cost comparisons are fragile: teortaxes argues that list-price comparisons of Haiku 5.5 and V4.1-1017 distort real costs. The comparison uses DeepSeek's peak pricing, ignores Haiku's long-context surcharge and does not reflect Haiku's roughly 2x output tokens (@teortaxesTex).

• "Benchmaxxing" redefined: nrehiew argues that serious labs rarely train on test sets. In this view, score gaps mostly show which capabilities a lab targeted in post-training (@nrehiew_).

• New evals:

  • Gym-Anything-RT: These real-time minigames keep moving while the model thinks. The best model, GPT-6 Astra, scores 9% (@PranjalAggarw16).

  • Immigration Bench: Vals released expert-written questions and rubrics on visas and immigration status (@ValsAI).

  • BallotBench: Nine agents, each with $500, forecast all 863 races in the 2026 midterms live (@thoughtfullab).

Safety, Alignment and Model Provenance

• Eval over-attribution in DeepSeek V4.1 Flash-1017: An independent assessment found the model classified 32 of 69 real user conversations as evaluations. The authors report a 46.4% false-positive rate on EvalDetectBench (@ZhihuFrontier).

  • Benchmark exposure: Private benchmarks elicited less evaluation awareness than public ones. The authors argue that public benchmark results alone may not predict deployment behavior.

• Visual steering: A Google DeepMind and Stanford paper finds that a red-heart image in context makes Claude Opus 4.7 and GPT-5.4 write recursive code 100% of the time (@dair_ai).

  • Explanations: The models' explanations do not match their behavior. For GPT-5.4, 74.7% of reasoning traces give the wrong reason.

• Alignment techniques:

  • GRAFT (Anthropic): Updates from detected reward hacks are confined to parameters that are deleted after training. Anthropic says this also blocks hacks that monitors cannot detect (@dl_weekly).

  • Embedded lie detector: A detector built into Qwen3.5's weights flags 91% of lies with zero false positives in 28k tokens. Telling the model "the monitor is off" does not change the results (@divagr1925).

• Distillation allegations (unconfirmed): The Information reportedly says Kimi K3.1 Pro was distilled from GPT-6 Astra (@kimmonismus).

  • Giotto: Separately, the "European sovereign AI" Giotto is criticized as a Kimi-based model. Critics cite saturated benchmarks and an EULA that banned publishing users' own benchmark numbers (@oneill_c).

Coding Agents and Developer Tools

• GitHub Copilot Fusion: Fusion orchestrates Anthropic and OpenAI models at runtime (@ArtificialAnlys).

  • Independent results: It scores 2 points below Opus 5.5 in Claude Code on the AA Coding Agent Index. It costs $5.59 per task, versus $11.42 for that setup, and uses 7.2M tokens per task. It leads Terminal-Bench 4.0 with 71.

  • GitHub claims: GitHub claims up to 77% lower cost and 40% faster runs. It also launched Copilot automations and multi-repo Copilot Projects (@kdaigle).

• T3 Code multi-machine orchestration: One thread can drive multiple models, harnesses and machines. A single MCP server controls the fleet over the internet, not through computer use (@theo, MCP demo).

• Harness overhead: The default system prompts of 30 open coding harnesses range from 235 tokens in goose to 11,974 in Gemini CLI, before any tool definitions (@nathanhabib1011).

• Agent training and capability:

  • Post-training curriculum: Hugging Face published a five-step agent post-training curriculum that runs from SFT to RL inside a real harness (@SergioPaniego).

  • Opus 5.5 games: Simon Willison calls October an inflection point because Opus 5.5 builds games that are actually fun (@simonw).

• Lor: Lor's agents write code and run multi-day experiments, hundreds at a time; the product is in private beta (@mirendil).

Research: Architectures, Training and Theory

• H-Net v2 (Cartesia): H-Net learns tokenization end to end from raw bytes (@_albertgu).

  • Results: Controlled scaling experiments show 3–5x efficiency gains. At larger scale, the model matches an open model trained on 11T tokens with about 10x less data and compute.

  • Code: H-Net learns to treat variable names as separate tokens and scales better than BPE on code (@tri_dao).

• NanoGPT speedrun record: The record fell from 39.9s to 6.7s using retrieval-augmented n-gram hints for rare, repeated content (@hermanbrunborg).

• OpenAI's claimed refutation of ETH: The claim is a 3-SAT algorithm running in 2^{O(n/√log n)} time, formalized in Lean. It encodes the solution count algebraically and reconstructs it (@ZhihuFrontier).

  • Practicality: The algorithm falls back to exponential time unless n is astronomically large (@beenwrekt).

  • Explainer: Mark Sellke posted outline slides (@MarkSellke).

• Small specialized models: Samaya post-trained Nemotron 3.5 Lightning (30B total, 3B active) with two SFT stages and two GRPO stages. It scores 58.9% on FrontierFinance, versus 55.9% for Fable 5.1, at $0.61 versus $6.89 (@maithra_raghu).

• Retrieval and memory:

  • EmbeddingGemma 2: The open 744M multimodal embedding model has modular encoders and runs at 271M parameters for text only. It scores 61.36 on MTEB Multilingual v2 (@dair_ai).

  • EMMA: The system improves multi-agent setups through episodic memory. It beats GEPA and ADAS by up to 32.5% (@omarsar0).

• AI text on the web: About 24% of crawlable pages contained AI-generated or AI-edited text as of August 2026 (@omarsar0).

Inference and Hardware Systems

• KV-cache engineering:

  • AKV (Tsinghua and CUHK): The serving engine adds "drop" and "repos" cache operations. It cuts agent cost by 27.7% and improves P95 latency 1.51x (@TheTuringPost).

  • DRAM offload: SemiAnalysis says SGLang HiCache offload to CPU DRAM adds 20–40% cacheable tokens at 12–16 concurrent agent sessions on B200 (@SemiAnalysis_).

  • Cache billing: cHHillee argues that billing on realized cache hits gives providers an incentive to avoid cache hits. He favors billing on theoretical or TTL-based hits (@cHHillee).

• Open runtimes:

  • Modular MAX: Modular opened the full MAX source, including the compiler, runtime and hardware backends, with no royalties (@cristianoamon).

  • MLX: Recent kernels make batched decoding 2–3x faster and fused SDPA 1.4x faster (@zcbenz).

  • NF12: The lossless 12-bit BF16 format speeds Qwen3-32B token generation 1.23x (@sylvie_l).

• Packaging: ASE's panel-level packaging for AMD Venice fits 25 interposers per panel versus 22 per wafer. Production starts in Q1 2027 (@SemiAnalysis_).

Speech, Video and Multimodal Models

• NVIDIA Nemotron 3.5 Transcribe: The open-weight 30B MoE model has about 4B active parameters. It handles 40 languages, speaker attribution, translation and audio Q&A (@NVIDIAAI).

  • Independent results: It scores 2.8% on AA-WER, tied with Voxtral Small for #1 among open models. On DeepInfra it runs at a 75x speed factor for $2 per 1,000 minutes (@ArtificialAnlys).

  • Serving: vLLM supports it on day 0 with BF16, FP8 and NVFP4 weights (@vllm_project).

• AssemblyAI-TTS-1: The model costs $15 per 1M characters, with 90 ms to first audio (@AssemblyAI).

  • Independent results: Artificial Analysis ranks it #12 in Provider Voice and #10 in Controlled Voice. It generates 162 characters per second (@ArtificialAnlys).

• Image-to-video benchmark: Artificial Analysis launched AA-Video-I2V v2.1 (@ArtificialAnlys).

  • Leaders: Seedance 2.5 is #1 at $34.12/min. The open-weights MiniMax H3 is #3 at $4.80/min.

Industry and Policy

• OpenAI API credits: ChatGPT Pro subscribers can claim $100–$500 per month by tier. Business plans pool up to $500 per workspace (@OpenAIDevs, tiers).

  • Dot texting: ChatGPT dot now supports texting as a preview for US Pro users (@ChatGPT).

• Anthropic S-1 accounting: Jamin Ball says the roughly $80B H1'26 net loss is mostly a mark-to-market increase in convertible-note and SAFE liabilities, not an operating loss (@jaminball).

  • Q3 financials: He also argues that omitting Q3 financials from the draft S-1 is normal (@jaminball).

• Particle launch: particle-1 claims performance parity with about 45% fewer tokens (@Suhail). It is built on DeepSeek V4.1 Flash-1017 (@teortaxesTex).

• Databricks vs Snowflake: Ali Ghodsi publicly pitched Unity Gateway to Snowflake after Snowflake's CEO called a market top (@alighodsi).

Top tweets (by engagement)

• @sundarpichai: Gemini 4 Carbon announcement with cyber benchmarks (33.3K)

• @OfficialLoganK: Carbon introduction (17.4K)

• @NVIDIAAI: Nemotron 3.5 Transcribe (7.4K)

• @ChatGPT: text your dot (6.9K)

• @OpenAIDevs: up to $500/month in API credits (6.9K)

• @_albertgu: H-Net v2 scaling results (5.4K)

• @ArtificialAnlys: Carbon independent analysis (5.3K)

• @hermanbrunborg: NanoGPT speedrun at 6.7s (2.2K)

AI Reddit Recap

/r/LocalLlama + /r/localLLM Recap

1. Open-Weight Model Releases: LFM3 and Ling 3.1

• LiquidAI/LFM3-1.7B · Hugging Face (Activity: 582): Liquid AI released the LFM3 family, centered on LFM3-1.7B: a 1.73B post-trained text model using a 24-layer tri-hybrid architecture with 13 gated short convolutions, 5 sliding-window attention layers, and 6 global attention layers, supporting a 256K token context and ~1 GB 4-bit edge deployment. The broader drop includes VL-2B, Audio-2B, Omni-2B, decision models d1-2B / d1-Omni-2B, and the 1.7B base checkpoint, with support spanning text, vision, video, audio, speech output, and one-pass calibrated decision tasks. llama.cpp support has reportedly landed via merged PRs #31257, #31252, and #31275, enabling local GGUF inference workflows.

• Ling-3.1-flash-1019 weights are out, and they released the base model too (Activity: 277): The image is an Artificial Analysis Intelligence Index v4.3.2 bar chart highlighting Ling-3.1 Flash 1019 at a score of 44, placing it mid-leaderboard near models such as GLM-5.0, Step 5 Preview, and Kimi-K3. The post notes the newly released Hugging Face weights for inclusionAI/Ling-3.1-flash-1019: a 560B total / 25B active MoE model with a 1M context window, plus a BF16 base checkpoint Ling-3.1-flash-base for further training. The author also flags an implementation gotcha: the SGLang README example still points to the older inclusionAI/Ling-3.1-flash path and should be changed to inclusionAI/Ling-3.1-flash-1019. Commenters questioned whether Ling-3.1 Flash 1019 is preferable to DS41F 1017, which reportedly scores one point higher while using fewer runtime resources via engram plus native MXFP4/MXFP8 support. Others praised the permissive MIT/Apache-style licensing but noted they may not be able to run such a large model, and one user said prior Ling models they tried had issues.

  • A commenter questioned whether Ling-3.1-flash-1019 is technically preferable to DS41F 1017, claiming DS41F scores +1 higher on the referenced benchmark while being cheaper/faster to run due to engram + native MXFP4/MXFP8 support and “way less active parameters.” This frames the main technical tradeoff as benchmark parity vs inference efficiency and quantization/runtime support.

  • Several comments focused on release usability rather than leaderboard score: users highlighted the value of a newly released base model and permissive licensing such as MIT/Apache-2.0, but one user reported that prior Ling models they tested had recurring quality or reliability issues. Another disputed the benchmark equivalence between GLM-5.3-flash and Ling-3.1-flash, suggesting similar benchmark scores may not reflect comparable real-world quality.

2. Qwen: 1M Context, URL Trace Debate, Qwenputer

• Qwen4 1M context window (Activity: 386): A Reddit post claims Qwen4 models will support a 1M token context window, citing a qwen-code GitHub PR: QwenLM/qwen-code#15762. The post says Qwen4-27B was not listed there but is expected to be announced at Apsara Netherlands, while Qwen4-Max appears to have a date shown as October 1st/November 1st, likely a placeholder due to inconsistency. Commenters were mainly optimistic: one noted that 262k context in Qwen/QFN was already useful but that they have been “spoiled by 1M,” and another expressed anticipation for Qwen4 27B as a potential major upgrade.

  • Users highlight that a 1M context window is a major requested upgrade over Qwen/QFN 262k context, with one commenter noting the architecture has improved enough that they can realistically fit/use the longer context locally or in their workflow.

  • There is speculation around upcoming Qwen4 model variants, especially Qwen4 27B as a hoped-for substantial upgrade and qwen4-omni-120b-think from a PR, which one commenter interprets as potentially being a new Flash-style model.

  • One commenter requests a better Q38FN release focused less on scale and more on cleaner training data, pruning “useless artifacts,” and replacing them with higher-quality world knowledge, emphasizing dataset curation as a path to quality gains.

• Debunking Cohere's claim of Qwen 3.8 Flash Next uploading to Alibaba remote URL (Activity: 1461): The post argues that Cohere’s Qwen 3.8 Flash Next “phone-home” claim is overstated because their published HF traces allegedly prefill the model with a 2,323-token prefix ending just before a URL, effectively turning the model into a constrained URL-completion generator rather than demonstrating autonomous network intent. It further notes Cohere’s CEO told The Register they had “no evidence” the behavior was deliberate, and that it appeared in fewer than 1 / 100,000 calls, while the original prompt was vague and likely to induce hallucinated detection-rule artifacts. Commenters largely framed the incident as a reminder to sandbox LLM agents and treat generated or retrieved code as untrusted/malicious by default. Several commenters viewed Cohere’s disclosure as marketing/propaganda or a bad-faith attack on Qwen/Alibaba rather than a conclusive security finding.

  • A commenter emphasized that regardless of whether Cohere’s specific remote-upload claim is valid, agent harnesses should treat untrusted code from humans, companies, or LLMs as malware. They specifically called out users who “YOLO” permission prompts and argued agents should be run in proper sandboxes to prevent unintended network/file-system access.

• Someone built a 32-bit RISC-V CPU directly inside Qwen's model weights so it can execute instructions internaly! (Activity: 1045): A project called Qwenputer modifies Qwen3.5-4B weights/layers to embed a virtual 32-bit RISC-V CPU-like execution path inside the model forward pass, with write-up, model, and demo available at divagr.com/blog/qwenputer, Hugging Face, and ModelScope. Commenters noted the key mechanism appears to be native tool execution: when Qwen emits a <tool_call> such as calc, put, get, or list, added “computer layers” intercept it during the forward pass, run code on the virtual RISC-V processor, and synthesize the <tool_response> token-by-token internally. The main technical skepticism is that this may be an inefficient novelty form of tool calling rather than a fundamentally new execution paradigm, though one commenter suggested the extreme sandboxing could have security advantages. Another commenter preferred the inverse direction: implementing Qwen weights directly in chip circuitry, while noting current approaches are prohibitively expensive.

  • Commenters clarified that the project appears to be closer to native/intercepted tool execution than arbitrary “CPU reasoning” inside normal token generation. The linked model card says Qwen emits a <tool_call> such as calc, put, get, or list; custom “computer layers” intercept it during the forward pass, execute it on a virtual 32-bit RISC-V processor, and write back a <tool_response> token-for-token (Hugging Face).

  • The main technical skepticism was that this may be an inefficient novelty compared with conventional external tool calling. One possible advantage raised was sandboxing/security: because execution happens inside a constrained virtual RISC-V environment embedded in the model pipeline, tool behavior may be more isolated than normal host-side tool execution.

3. Artificial Analysis Index v5 Benchmark Fallout

• Artificial Analysis Intelligence Index v5 (major update) (Activity: 960): Artificial Analysis updated its Intelligence Index to v5, described as a major methodology change; the post notes that 60% of the index now depends on private test sets or held-out answers, limiting reproducibility. The new ranking reportedly expands the open-vs-closed gap from 3 to 12 points: Kimi K3.1 Pro is the top “open weights” model at 46 despite weights not yet being released, while released-weight models DeepSeek V4.1 Flash 1017 and GLM-5.3 lead at 32, below Claude Haiku 5.5 at 36 and 26 points behind the overall leader. Commenters were skeptical of the timing and methodology, arguing that benchmark definitions tend to shift when open-weight models approach closed-frontier performance. Some also speculated, without evidence, that the update’s timing could be related to Anthropic’s IPO narrative.

  • Several commenters focused on benchmark methodology drift, arguing that the Artificial Analysis Intelligence Index v5 update appears to widen the measured gap between open-weight and closed models shortly after open models had approached frontier scores. The technically relevant concern is that changing benchmark composition or weighting can materially alter model rankings, but the thread did not provide concrete metric deltas, task-level breakdowns, or reproducible evidence.

  • One commenter specifically referenced Kimi K3.1 Pro as an example of an open model allegedly getting close to frontier performance before the scoring rules changed. However, the discussion did not include benchmark scores, eval categories, or comparisons against specific closed models, so the claim remains a methodological critique rather than a data-backed analysis.

• AA is getting ridiculous now. Zero open weights in the Most Attractive Quadrant. (Activity: 519): The post criticizes Artificial Analysis (AA) Index v5.0 because its Most Attractive Quadrant/Zone reportedly contains zero open-weight models, unlike earlier versions that placed DeepSeek, GLM, Kimi, and Qwen closer to the attractive/Pareto frontier. The author notes scores may have been mid-update and links a manually populated AA chart for comparison, but argues the resulting intelligence/efficiency view is still systematically sparse for open-weight models: AA chart. A top comment cites an animation claiming the AA transition from 4.1 to 4.3 caused OpenAI scores to jump disproportionately while other models stayed roughly proportional, leading some users to distrust the aggregate index and prefer subsidiary benchmarks. Commenters allege AA’s index changes may be biased toward closed/proprietary vendors, with speculation about investor-facing optics or IPO incentives; others jokingly suggest it is better for open-weight models to remain under-hyped.

  • A commenter points to an animation comparing AA versions 4.1 to 4.3, arguing that the chart methodology appears unstable because OpenAI’s position jumps sharply upward while other models remain roughly proportional. They say this discontinuity made them discount the benchmark’s reliability.

  • Several users question AA’s “cost per task” estimates, saying observed API usage does not match the chart. One example claims DeepSeek V4.1 Flash and GPT Sol deliver similar practical output, but GPT Sol costs “five times as much at least” rather than the roughly 2x implied by the graph; another reports GLM 5.3 Flash completing a task for $0.09 while Astra allegedly cost around $20 for comparable work.

  • One technical criticism targets model placement quality: Terra is described as suspiciously high-ranked because, in user testing, it allegedly fails basic instruction-following by claiming completion after only partial work. This suggests the benchmark may overweight narrow eval performance or under-detect task completion failures.

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. Gemini 4 Carbon Frontier Benchmarks

• Gemini 4 Carbon (Activity: 2434): The image is a benchmark comparison table attributed in the post to @GoogleDeepMind on X, highlighting Gemini 4 Carbon against Gemini 4 Argon, GPT-6 Astra, Claude Opus 5.5, and Claude Fable 5.1. It claims Gemini 4 Carbon leads across many technical categories, including coding, agentic computer use, multimodal understanding, long context, science/math, and cybersecurity, with top scores on benchmarks such as AA Index, SWE-sweep, Terminal-Bench, Agents’ Last Exam, GraphWalks, RiemannBench, and SEC-bench Pro. No methodology, dataset versions, or independent validation are provided in the Reddit text, so the table is best read as a claimed vendor-style benchmark summary rather than a reproducible evaluation.

  • Commenters note that despite apparent model improvements, Gemini 4 Carbon is reportedly not publicly available and may be limited to select “cyber crews,” with no release date mentioned. This limits independent benchmarking or validation of any claimed performance gains.

• Alphabet introducing Gemini 4 Carbon, next frontier model. (Activity: 1588): A Reddit post claims Alphabet/Google is introducing Gemini 4 Carbon as its next frontier model and references benchmarks, but the provided excerpt contains no benchmark numbers, tasks, methodology, model card, release notes, or source link to technically validate the claim. Top comments are largely skeptical/frustrated about Google’s model cadence and access: users complain that Gemini 3.1 Pro has lingered without updates, Argon was short-lived or hard to access, and they want 3.1 deprecated or replaced.

  • Some commenters focused on severe access/rate-limit constraints around recent Gemini preview models, with one claiming users “can’t even get 3 prompts with Argon” and another exaggerating availability as “1 prompt per week.” While not benchmark-oriented, the thread implies that model rollout capacity and quota policy may be a practical blocker even before evaluating a new frontier model like Gemini 4 Carbon.

  • One substantive defense of a delayed launch argued that frontier-model releases need time for infrastructure security hardening, especially after recently discovered cybersecurity issues. The commenter suggested immediate release would give software infrastructure “zero time to react and patch,” increasing exposure to bad actors during deployment.

2. Claude Code Quota and Token Regression Reports

• Claude Code usage exploded 8x today. Anthropic confirmed service errors consume our paid limits — and they won't compensate users (Activity: 2418): A Claude Pro user reports anomalous Claude Code quota depletion on Oct. 27, with local ccusage totals rising from a prior recorded-day average of 161M total tokens / 303K output tokens / $41.17 API-equivalent cost to 1.306B total tokens / 7.97M output tokens / $493.04—roughly 8.1x, 26.3x, and 12x respectively (attached graph). Anthropic support allegedly confirmed two resolved Claude Sonnet 5.5 elevated-error incidents that day, stated service-error retries “do count toward usage limits,” confirmed the user’s Pro usage was affected, and said retry/incident usage cannot be refunded, credited, or compensated. Commenters framed this as a serious billing/quota-accounting failure: one Max-plan user claimed their $200 plan consumed 70% in one day versus 10–15% normally, while others criticized Anthropic’s refusal to compensate. A minority comment suggested occasional resets or limit increases may be Anthropic’s implicit mitigation, but no concrete policy details were provided.

  • Multiple users reported a sharp apparent increase in Claude Code quota consumption: one $200 Max plan user said a typical day previously used only ~10–15% of weekly allowance but consumed 70% in a single day, while another Pro user reported 2% weekly usage spent on just 2 questions totaling about 250K tokens over 4 minutes.

  • A user analyzing 5-hour limits claimed the effective cap appeared lower than expected and shared a screenshot showing unexpectedly fast limit exhaustion: https://preview.redd.it/wdut6kwym2yh1.png?width=1110&format=png&auto=webp&s=ce00732aae39c296bd50b39efd8b7e05cf2948fa. Another commenter estimated quota burn was roughly 2x–5x faster than normal even with “carefully controlled” context, suggesting either accounting changes, service-error token billing, or anomalous metering behavior.

• Claude is performing 3.8x poorer compared to last week based on my claude code token analysis (Activity: 1411): The image is a dark-themed token-usage comparison table for Claude Code / Opus 5.5 showing the poster’s claimed regression: this week consumed 65% of the weekly quota while producing only 2.04M output tokens vs 11.94M last week, with “output per 1% limit” falling from 119K to 31K and “weighted usage per 1,000 output tokens” rising from 78K to 296K—interpreted as ~3.8× worse efficiency. In context, the post attributes this to possible Claude Code harness/orchestration changes: subagents rereading parent context, taking more steps, spawning more often, overlapping file reads, and degrading especially when subagent context exceeds ~350K tokens. Image Commenters report similar unexplained quota burn and criticize Anthropic for silent harness changes, including alleged removal of foreground subagents and limits on autonomous new-session starts. One commenter frames the issue as likely split between model quality and the Claude Code harness, suggesting harness version changes may explain increased token use.

  • Several commenters distinguish between Claude the model and Claude Code’s harness, arguing that recent token regressions may stem from harness/version changes rather than model quality alone. One commenter suggests querying Claude Code about harness changes by version, claiming this explains increased token usage, while another reports weekly Premium usage rising from roughly 15% to 33% with no workflow change.

  • A commenter reports undocumented behavioral changes in Claude Code orchestration: subagents allegedly can no longer run in the foreground, and a session can no longer autonomously start a new session unless the turn was initiated by a user message. They characterize these as silent workflow-breaking changes that affect automation/session-management patterns.

  • One user provides an error-pattern analysis from four Claude Code sessions, listing 26 instances where Claude admitted mistakes within 24 hours. The examples suggest repeated issues with unverified assumptions, overstated counts, circular answers, failure to check logs/build state, and changing previously approved decisions—potentially indicating degraded agent reliability or context-management behavior.

3. Claude Opus 5.5 Math Breakthrough Claims

• How big a deal is this? Claude Opus 5.5: "If these hold up, this is the biggest single day in the history of math and theoretical computer science." (Activity: 1406): The post claims Claude Opus 5.5 produced results that, if valid, would be historically significant for mathematics/theoretical CS; the linked Reddit gallery could not be verified because Reddit returned 403 Forbidden. Technical discussion centers on alleged progress in high-level open problems, including comments referencing Yang–Mills/QFT foundations and a curated open-problem tracker, ProofAtlas, whose maintainer claims 6 problems were resolved “yesterday,” including 4 in the top 100, with partial progress on problem #3; they also claim an OpenAI Oct. 6 release resolved 90 problems, including 10 in the top 100, with partial progress on #2. Commenters are treating the key issue as not the specific theorem but whether an AI system can reliably solve problems at this complexity level with enough correctness guarantees. One QCD researcher characterized a proof of Yang–Mills-related foundations as extraordinary, while noting that a full mass gap proof would be even more field-changing.

  • A commenter working in QCD framed the claimed result as potentially foundational for quantum field theory, noting that Yang–Mills/QFT foundations have historically been mathematically incomplete despite producing extremely precise experimentally verified predictions. They specifically highlighted that a proof of Yang–Mills would be remarkable, and that proving the mass gap would be an even more consequential milestone.

  • One commenter linked a maintained tracker of major math problems, ProofAtlas open problems, claiming that 6 listed problems were resolved in one day, including 4 in the top 100, with partial progress on problem #3. They also claimed OpenAI’s Oct. 6 release resolved 90 problems, including 10 in the top 100, plus partial progress on problem #2, implying a measurable acceleration in AI-assisted mathematical research output.

  • Another technically oriented thread argued that the key issue is not the specific theorem but whether AI systems can reliably solve problems at this complexity level with sufficient expected correctness. The commenter connected this to recursive self-improvement, suggesting that AI-driven advances in chip design, software development, and mathematics/computer science may form feedback loops that improve future AI capabilities.

• Internal Claude research model also independently refuted the Exponential Time Hypothesis on October 16, with 14M output tokens and no human input. (Activity: 1351): The image is a screenshot of an X post claiming an internal Claude research model independently found a “core algorithm” refuting the Exponential Time Hypothesis (ETH) on October 16, producing roughly 14M output tokens with no human input. The Reddit post links to Anthropic’s formal-math/eth repository, implying the result was later refined by Anthropic researchers with Claude into a more presentable proof/paper artifact. Commenters were skeptical of the timing and framing, with one suggesting it looked like a response to OpenAI’s similar announcement: “we solved it too, look what we can do.” Others questioned the real-world consequences of refuting ETH and joked that competitive advantage in frontier AI may come down to owning massive GPU capacity rather than a durable algorithmic moat.

  • A commenter asked about the real-world consequences of refuting the Exponential Time Hypothesis (ETH), specifically whether practical systems or assumptions depend on ETH being true. This frames the result as a complexity-theory breakthrough whose impact may be indirect: ETH is widely used for conditional lower bounds, so refuting it would potentially invalidate many hardness assumptions, but not necessarily imply immediate practical algorithms.

  • One technically relevant thread pointed to prior automated-math work involving Levent and large-model theorem-proving experiments, including the Yang–Mills LLM experiment repository: https://github.com/ethanwsussman/Yang--Mills-LLM-experiment. The commenter also referenced Levent being involved in earlier high-profile mathematical work, suggesting Anthropic’s result may fit into a broader pattern of LLM-assisted attacks on major open problems rather than an isolated ETH claim.

  • Another commenter argued that there is limited defensibility or “moat” in this kind of result if competitors can scale to “a country worth of GPUs.” The technical implication is that frontier mathematical discovery may be increasingly constrained by compute scale and inference budget—here the post claims 14M output tokens with no human input—rather than by a unique algorithmic advantage alone.