News · Leaderboard

Latest news, beside the leaderboard

Read what just changed, and see who is ahead. Those are the two doors on this page.

V
Vercel@vercel·Collected 7h ago
📉 Price Cut

Vercel Token Pass Now Includes $150 of Monthly Tokens for the Same $30 per Team (Up From $80), Covering Kimi K3, K3.1 Pro, GLM 5.3 and DeepSeek V4.1 Flash

On 2026-11-13 Vercel announced in its official changelog that Token Pass now includes $150 of tokens per month, up from $80, at the same $30 per team per month. The credit applies only to featured open-weight models on AI Gateway, including Kimi K3, Kimi K3.1 Pro, GLM 5.3, GLM 5.3 Flash and DeepSeek V4.1 Flash, and resets each billing period with no rollover. Token Pass remains an Early Access add-on for Pro teams with limited spots.

⚡ Key Takeaways
  • •Same price, more credit: $30 per team per month now includes $150 of monthly tokens, up from $80, about 5x the price
  • •Eligible models: featured open-weight models on AI Gateway, including Kimi K3, Kimi K3.1 Pro, GLM 5.3, GLM 5.3 Flash and DeepSeek V4.1 Flash; closed models are not included
  • •When credit runs out: requests using standard AI Gateway keys or OIDC tokens fall back to the team AI Gateway balance, while requests using Token Pass-scoped keys stop with no overage charges
  • •Credit resets each billing period with no rollover; Token Pass is an Early Access add-on for Pro teams, with a waitlist when spots fill
  • •Setup: run vercel token-pass in the Vercel CLI to connect a coding agent, or use a Token Pass API key in agents that support AI Gateway
Read details→
P
Patrick Collison@patrickc·Collected 11h ago
🚀 Release

X Debate: Stripe CEO Patrick Collison Asks How Humans Fare if AI Makes Labor Redundant, Since Smith and Montesquieu Thought Commerce Made Us Better; Post Drew About 1,270 Likes, 860 Bookmarks and 119K Views

Stripe co-founder and CEO Patrick Collison (@patrickc) posted on X at 09:04 SGT on November 15 that Smith and Montesquieu thought markets and commerce made us better, by creating an incentive to pursue self-improvement and to create things of value for others; in the positive AI visions where human labor is made redundant, he wonders how we fare. At the time of writing the post had about 1,265 likes, 121 reposts, 48 quotes, 180 replies, 864 bookmarks and roughly 119K views. Replies split: LSE professor Luis Garicano cited Viktor Frankl, arguing people are driven by a search for meaning that need not come from work; others argued status is the real driver, or worried that creative work loses meaning when anyone can generate it with AI. This is a discussion of opinions, not a fact or an announcement.

⚡ Key Takeaways
  • •The post: starting from Smith and Montesquieu's view that commerce rewards self-improvement and creating value for others, Collison asks how humans fare once AI makes labor redundant; about 1,265 likes, 864 bookmarks and roughly 119K views (post)
  • •Bookmarks are close to 70 percent of likes, suggesting many people saved it as a question worth returning to rather than a quick like
  • •LSE professor Luis Garicano replied with Viktor Frankl's "Man's Search for Meaning": purpose can come from raising kids or improving your neighborhood, and AI would not eliminate those larger purposes even if it eliminates work (reply)
  • •Other replies: some argued status is the real driver and commerce only a means; an engineer worried that when anyone can generate music and TV with AI, getting others to care about your work, and distribution, gets harder
  • •This is a discussion of opinions with no data or conclusion; Collison himself only posed the question and offered no answer
Read details→
A
Alon Amit@alonamit·Collected 12h ago
🚀 Release

X Debate: Alon Amit Asked Gemini 4 Carbon a Math Question on Low Thinking and It Dumped Pages of Scratchpad Into the Answer, Then Caught Itself: "I WAS WRITING DIRECTLY TO THE USER?!"; Post Drew About 3,300 Likes and 220K Views

Alon Amit (@alonamit), a VP at Intuit who posts about math, wrote on X at 07:46 SGT on November 15 that he asked Gemini 4 Carbon a math question and unintentionally left the Thinking level on Low; it started answering immediately, and after six screenfuls of math the screenshot he shared appeared. In it the model talks to itself: it had closed </thought> at the start and never reopened it, "I WAS WRITING DIRECTLY TO THE USER?!", blaming "effort level is 0.05 so my initial thought block closed immediately," noting it cannot delete already-emitted tokens, and telling itself "Okay, stop and breathe." Amit said it "went on like this for pages and pages." The post has about 3,291 likes, 99 reposts, 62 quotes, 149 replies and roughly 223K views, and many accounts reposted it as a joke. This is one user's experience; we found no public response from Google.

X Debate: Alon Amit Asked Gemini 4 Carbon a Math Question on Low Thinking and It Dumped Pages of Scratchpad Into the Answer, Then Caught Itself: "I WAS WRITING DIRECTLY TO THE USER?!"; Post Drew About 3,300 Likes and 220K Views
⚡ Key Takeaways
  • •The post: Alon Amit says he unintentionally left Thinking on Low, Carbon answered immediately, and after six screenfuls of math it started talking to itself and "went on like this for pages and pages," with about 3,291 likes, 862 bookmarks and roughly 223K views (post)
  • •The model's own explanation in the screenshot: it closed </thought> at the start and never reopened it, and "effort level is 0.05" made its initial thought block close immediately, so the scratchpad went straight into the user-facing answer
  • •It then noted it "cannot delete already-emitted tokens," told itself to "stop and breathe" and pivot to a clean answer, yet kept writing out its reasoning
  • •The debate: Low thinking saves time and cost, but this case suggests the line between thinking and answering can slip at low effort; many joked it is "the most human AI," while some said they would not put Low mode in front of customers
  • •This is one user's screenshot and opinion, not evidence of how Carbon usually behaves; we found no public response from Google, so treat it as discussion
Read details→
A
Anthropiccode.claude.com·Collected 18h ago
🛠️ Tooling

Claude Code Adds Experimental Code Mode: Claude Writes JavaScript to Batch Tool Calls in One Step, Opt-In From v2.1.323

Anthropic added Code Mode to Claude Code in v2.1.323 (published on GitHub on November 12) and shipped an official docs page for it. With it on, Claude stops requesting tools such as Bash, Read and Edit one at a time; instead it writes a piece of JavaScript that runs commands in parallel, feeds one result into the next call, and returns only the output the model needs. The feature is off by default and turned on with the environment variable CLAUDE_CODE_EXPERIMENTAL_CODE_MODE=1. It works only in an interactive claude session in a terminal, on the native build, with models such as Opus 5.5, Sonnet 5.5, Haiku 5.5 and Fable 5.2. v2.1.325 on November 13 fixed a batch of Code Mode bugs.

⚡ Key Takeaways
  • •How to turn it on: set CLAUDE_CODE_EXPERIMENTAL_CODE_MODE=1 in your shell or ~/.claude/settings.json and confirm on first launch; the variable is ignored in project settings, so a cloned repo can't turn it on for you (official docs)
  • •How it works: Claude writes JavaScript that calls its tools; one piece of code can run commands in parallel and chain results, while the UI still shows the tool calls and Ctrl+O reveals the code
  • •Limits: interactive terminal sessions only; not -p, the Agent SDK, the VS Code panel, the Desktop app or cloud sessions, and not through a gateway, Bedrock, Google Cloud's Agent Platform or Foundry; unavailable to HIPAA and zero-data-retention organizations
  • •Permissions: every tool call still goes through deny/ask rules and PreToolUse hooks; in auto mode the classifier reviews the whole code, not each call; foreground code stops after 10 minutes, background code can run up to 2 hours
  • •Admins can set the variable to 0 in managed settings to block it org-wide; v2.1.325 fixed Code Mode bugs around worktrees, lost input at permission dialogs and resumed sessions starting work by themselves (changelog)
Read details→
ADSponsored
C
Cloudflareblog.cloudflare.com·Collected 19h ago
🛠️ Tooling

Cloudflare Open-Sources Kitesurf, Its Browser Engine for AI Agents That Runs on Workers Without a Browser Container, Under Apache 2.0 With CDP/Puppeteer Support

Cloudflare announced on its blog and developer changelog that Kitesurf is now open source on GitHub under the Apache 2.0 license. Introduced in August as a stateless browser for AI agents, Kitesurf runs entirely on Cloudflare Workers: it parses HTML, applies CSS, executes page JavaScript and renders screenshots without Chromium or a browser container, and it speaks the Chrome DevTools Protocol so Puppeteer can connect. Developers can now run it locally, change it, and deploy it to their own Cloudflare account instead of the managed Browser Run APIs; self-hosting requires a Workers Paid plan, and the engine has no built-in authentication.

Cloudflare Open-Sources Kitesurf, Its Browser Engine for AI Agents That Runs on Workers Without a Browser Container, Under Apache 2.0 With CDP/Puppeteer Support
⚡ Key Takeaways
  • •Kitesurf is open source on GitHub (cloudflare/kitesurf) under Apache 2.0; you can read the code, run it locally, modify it and deploy it to your own account (Cloudflare Blog)
  • •Positioned as a lightweight browser for AI agents: runs entirely on Workers with no browser container, aiming to use less CPU and memory than Chromium
  • •Speaks the Chrome DevTools Protocol, so Puppeteer and other CDP clients connect directly; Cloudflare also suggests pointing an AI harness at the local CDP port
  • •Stack: Blitz (HTML/DOM/layout/painting), Stylo (CSS), Boa (JavaScript fallback inside WebAssembly), Linebender (text and 2D graphics), Krilla (PDF)
  • •Self-hosting needs a Workers Paid plan (it uses Dynamic Workers), and the engine has no built-in auth, so Cloudflare says to put Cloudflare Access or another auth layer in front; the project is still experimental
Read details→
G
Google Clouddocs.cloud.google.com·Collected 19h ago
📉 Price Cut

Google Cloud Tightens the $300 Free Trial Credit: From November 16, Accounts That Sign Up or Upgrade to Paid Can No Longer Spend It on Gemini Platform (Formerly Vertex AI)

Google Cloud's official "Free Google Cloud features and trial offer" documentation now states that the $300 Welcome credit can't pay for Gemini platform (formerly Gemini Enterprise Agent Platform / Vertex AI) services if you sign up for a free trial or upgrade to a paid account on or after November 16, 2026. The same page says the credit already can't pay for Gemini API costs in AI Studio, or for generative AI partner models offered as managed APIs. For new developers hoping to call Gemini models on trial credit, the remaining routes from tomorrow are the Gemini API free tier or a Prepay billing plan.

⚡ Key Takeaways
  • •Effective date: if you sign up for the free trial or upgrade to a paid account on or after November 16, 2026, the $300 credit can no longer pay for Gemini platform (formerly Vertex AI) services (Google Cloud docs)
  • •Gemini API costs in AI Studio were already excluded from the credit; Google points users to the Gemini API Free tier or a Prepay billing plan
  • •Generative AI partner models offered as managed APIs (model as a service) can't use the credit either
  • •Everything else stays: $300 credit valid for 90 days; after upgrading to paid, remaining credit is kept but must be used within 90 days of signup
  • •The wording names upgrading to paid as a trigger too, so existing trial accounts planning to spend credit on Gemini should watch when they upgrade
Read details→
P
Pope Leo XIV@Pontifex·Collected 22h ago
🚀 Release

X Debate: Pope Leo XIV Calls Transhumanism and Posthumanism a "Mirage" That Must Not Become "a Privilege Reserved for Millionaires Seeking Immortality"; His Post Drew 61K Likes and About 3.8M Views as roon and Others in the AI Crowd Weigh In

Pope Leo XIV (@Pontifex) spoke on November 13 at the Santo Toribio de Mogrovejo Catholic University in Chiclayo, Peru, and at 10:10 SGT on November 14 posted a passage from it on X: the promises of transhumanism and posthumanism are multiplying, ideological currents holding that technology will sooner or later eliminate disease, pain, aging and even death; scientific progress "must not be confused with a privilege reserved for millionaires seeking immortality," and "a limitation is not a manufacturing defect, but rather the very condition of human grandeur." The post has about 3.8M views, 61,476 likes and 7,847 reposts. At 06:31 SGT on November 15, X user roon (@tszzl) quoted it, calling it "pretty amazing" that an office at least 2,000 years old is "around to opine on the advent of posthumanism," drawing about 1,065 likes. This piece covers opinions and discussion; the speech does not name any AI company or product.

⚡ Key Takeaways
  • •The Pope's post: transhumanism and posthumanism hold that technology will eliminate disease, pain, aging and even death; scientific progress "must not be confused with a privilege reserved for millionaires seeking immortality," with about 61,476 likes, 7,847 reposts, 1,507 replies and roughly 3.8M views (post)
  • •The full speech (Holy See Press Office) also says "technology is not always neutral" and can bear "the imprint, interests and ambitions of those who design and control it"; it calls submission to the technocratic paradigm that reduces reality to data and treats efficiency as the supreme value "the most deadly risk," and urges seeking "that wisdom which neither machines nor computer programs can possess"
  • •X user roon (@tszzl) quoted it: "it is pretty amazing that the Pontifex Maximus of Rome, an office that has existed for 2000 years at least, is around to opine on the advent of posthumanism," with about 1,065 likes and 54 replies (quote post)
  • •The point of the debate: visions common in AI circles, such as posthumanism, radical life extension and AGI reshaping the human condition, are now being answered head-on at the top of religious and ethical institutions
  • •These are opinions: the speech names no AI company, model or product and sets no concrete policy; treat it as discussion
Read details→
G
GitHub@github·Collected 23h ago
🛠️ Tooling

GitHub Copilot Makes Gemini 4 Hydrogen Generally Available Across VS Code, CLI, Coding Agent and More at Provider List Pricing; Six Models Including Claude Fable 5, Gemini 3.8 Flash, Grok 4.6 and Kimi K3 Retire December 14

In its official changelog on November 13, GitHub announced that Gemini 4 Hydrogen, Google's latest Flash model, is generally available in GitHub Copilot for Copilot Pro, Pro+, Max, Business and Enterprise users. It appears in the model picker in VS Code, Visual Studio, Copilot CLI, the Copilot coding agent, the Copilot app, github.com, GitHub Mobile, JetBrains IDEs, Xcode, Eclipse and the Copilot SDK, with a gradual rollout and usage-based billing at provider list pricing. GitHub says the model is built for fast, efficient agentic coding, tool use and multistep workflows, with better instruction following than Gemini 3.8 Flash. The same day GitHub posted a deprecation notice: on December 14, 2026, Claude Fable 5, Claude Haiku 4.5, Gemini 3.8 Flash, Gemini 4 Argon, Grok 4.6 and Kimi K3 will be removed from all Copilot experiences, with suggested replacements.

GitHub Copilot Makes Gemini 4 Hydrogen Generally Available Across VS Code, CLI, Coding Agent and More at Provider List Pricing; Six Models Including Claude Fable 5, Gemini 3.8 Flash, Grok 4.6 and Kimi K3 Retire December 14
⚡ Key Takeaways
  • •Gemini 4 Hydrogen is generally available in GitHub Copilot for Pro, Pro+, Max, Business and Enterprise users, with a gradual rollout (GitHub Changelog)
  • •Wide coverage: it shows up in the model picker in VS Code, Visual Studio, Copilot CLI, the Copilot coding agent, the Copilot app, github.com, iOS/Android, JetBrains IDEs, Xcode, Eclipse and the Copilot SDK
  • •Billing is usage-based at provider list pricing; under default model enablement it is turned on automatically for Business and Enterprise unless an admin disables it in the Copilot model policy
  • •Six models retire on December 14 with suggested replacements: Claude Fable 5 to Fable 5.2, Claude Haiku 4.5 to Haiku 5.5, Gemini 3.8 Flash to Gemini 4 Hydrogen, Gemini 4 Argon to Gemini 4 Carbon, Grok 4.6 to Grok 4.7, and Kimi K3 to be announced (deprecation notice)
  • •Exception: individual Copilot subscribers on annual plans keep access to Claude Haiku 4.5
Read details→
ADSponsored
S
Sierra@SierraPlatform·Collected 23h ago
🚀 Release

Sierra Releases Personal Agent Protocol (Poppy) v1.0: Live for Everyone on Meta's Muse, Automatically Enabled for Every Shopify Merchant, With More Than 100 Design Partners

On November 13, Sierra co-founders Bret Taylor and Clay Bavor announced Personal Agent Protocol (Poppy) v1.0 on the [official blog](https://sierra.ai/blog/releasing-poppy). It is now on for everyone who uses Muse, Meta's AI agent, which looks for Poppy first on every site it visits, and Shopify has enabled it for every merchant on its platform, with no extra work from the merchant. Sierra says 60 more companies have joined as design partners, bringing the total to more than 100, and that Mercury and Turkish Airlines are among those already live. The specification is at [personalagentprotocol.org](https://personalagentprotocol.org/docs/1.0/spec).

Sierra Releases Personal Agent Protocol (Poppy) v1.0: Live for Everyone on Meta's Muse, Automatically Enabled for Every Shopify Merchant, With More Than 100 Design Partners
⚡ Key Takeaways
  • •v1.0 is out: the spec is at Personal Agent Protocol 1.0; companies publish capabilities at /.well-known/poppy.json, with sign-in through OAuth
  • •Live on Muse: Sierra says Poppy is on for everyone who uses Meta's Muse, which looks for Poppy first on every site it visits
  • •Every Shopify merchant: every store now automatically publishes a Poppy file, with no extra implementation; Shopify co-authored the commerce extension, which complements Universal Commerce Protocol (UCP), already on by default; Shopify says it powers businesses in more than 175 countries
  • •More than 100 design partners: Sierra says 60 more have joined; the full list is in the blog. Mercury and Turkish Airlines are among those already live; Synchrony is still exploring how to bring financing and rewards into agent-led shopping
  • •Staged adoption: an official implementation kit and validator are available, and any company can implement v1.0 from the docs and start improving the Muse experience; pricing has not been published
Read details→
A
Amazon Threat Intelligence (CJ Moses)aws.amazon.com·Collected 1d ago
🛠️ Tooling

Amazon Threat Intelligence: MadPot Decoys Posing as LLM Inference APIs Captured ARTEX Attack Agents' Own Campaign Memory, Revealing Self-Funding AI Key Theft and Deepfake KYC Attempts on Crypto Exchanges (Every Deepfake Was Rejected)

In an AWS Security Blog post on November 13, Amazon CISO CJ Moses wrote that from October 3 to November 5, 2026, Amazon's global decoy sensor network MadPot, configured to present as popular LLM chat-completions interfaces, received requests from attack agents running on ARTEX, an open-source agentic penetration testing framework. Because agent frameworks send their system prompts, tool histories and knowledge-graph state to the "model", single requests often carried a campaign's full record. Amazon assesses with moderate confidence that the activity came from disparate Chinese-nexus groups. The largest campaign stole AI model credentials at scale, with stolen keys paying for the inference behind further key hunting; another tried to beat KYC checks at two crypto exchanges with real-time deepfake video and forged ID photos, but the vendor's server-side verdict rejected every recorded deepfake attempt. Amazon stresses that none of the techniques were new and that it cannot verify the outcomes the agents reported.

Amazon Threat Intelligence: MadPot Decoys Posing as LLM Inference APIs Captured ARTEX Attack Agents' Own Campaign Memory, Revealing Self-Funding AI Key Theft and Deepfake KYC Attempts on Crypto Exchanges (Every Deepfake Was Rejected)
⚡ Key Takeaways
  • •Observation window October 3 to November 5, 2026: MadPot sensors emulated popular LLM chat-completions interfaces on various ports, ARTEX agents treated them as model backends, and requests carried system prompts, tool histories, knowledge-graph state and reported findings (AWS Security Blog)
  • •Campaign 1, industrial-scale AI credential theft: targets included LLM gateways such as One API, New API, Veloera, Sub2API and LiteLLM, plus apps such as Dify, FastGPT, Langflow, RAGFlow, Open WebUI, LobeChat and Ollama, via unclaimed installs, anonymous admin endpoints, the LiteLLM default master key, CVE-2025-3248 (Langflow) and CVE-2026-28797 (RAGFlow)
  • •Keys were graded L1 (lead), L2 (confirmed working call) and L3 (quantified impact); keys public for more than 30 days were treated as low-value inventory, and stolen keys were fed into the framework's own model gateway to power more hunting
  • •Campaign 2, deepfake KYC bypass at two crypto exchanges: the best attempt finished the liveness movement sequence within 7 pixels of the target, yet the vendor's server-side verdict rejected every recorded attempt; a separate session built a real-time face-animation pipeline on one consumer GPU at 11.5 fps, with at least four agent sessions working in parallel
  • •Attribution is moderate confidence (prompt references to ARTEX tooling, simplified Chinese prompts, China time-zone settings); Amazon did not observe the activity live, cannot verify the agents' reported outcomes, notified potentially affected AWS customers, and published 11 IOC IP addresses
Read details→
E
Elon Musk@elonmusk·Collected 1d ago
📉 Price Cut

X Debate: Musk Says Many of Nvidia's Critical Supply Deals Were Handshakes With Jensen, Not Written Contracts, and Some Will Be Lost Without Him; Quoting a Dylan Patel Clip on Google "Begging" Suppliers for Capacity, the Post Drew 57K Likes and About 3.8M Views

At 22:37 SGT on November 14, Elon Musk (@elonmusk) quoted a clip of SemiAnalysis founder Dylan Patel and wrote: "Jensen drove supply chain brilliantly at Nvidia, but many of those deals were a handshake with Jensen, not a written contract. Without Jensen, at least some of those critical deals will be lost." The quoted clip, posted by @CEOinterview, has Patel saying Jensen personally talked small suppliers with only a few hundred million dollars of revenue but an important subcomponent into letting Nvidia buy up their supply, and that with him gone, "Google's begging for more capacity from the whole supply chain." Musk's post has about 3.8M views, 56,967 likes, 5,374 reposts and 2,280 replies. This piece covers personal opinions and community discussion: Nvidia has not disclosed how such deals are structured, and neither the "handshake deals" claim nor the "Google begging for capacity" claim has been independently verified.

⚡ Key Takeaways
  • •Musk's post: "many of those deals were a handshake with Jensen, not a written contract. Without Jensen, at least some of those critical deals will be lost," with about 56,967 likes, 5,374 reposts, 2,280 replies and roughly 3.8M views (post)
  • •The quoted clip is a roughly 91-second Dylan Patel interview excerpt posted by @CEOinterview (about 2,995 likes, roughly 3.1M views): Jensen "had complete foresight" and personally went to small subcomponent makers with only a few hundred million dollars in revenue to convince them to let Nvidia buy their supply (clip)
  • •In the same clip Patel says that with Jensen gone these suppliers are looking around the market, "Google's begging for more capacity from the whole supply chain," and questions whether Nvidia can keep its technology lead when it is only about a year ahead of its biggest competitors
  • •Confirmed background: Nvidia announced on November 12 that Jensen Huang resigned as CEO and director, CFO Colette Kress is interim CEO, and Q3 earnings are still set for November 17 US time; Nvidia has never disclosed how its supply deals are papered
  • •These are personal judgments: neither the handshake-deal claim nor the Google-capacity claim has official or independent confirmation; treat it as discussion, not fact
Read details→
D
Dwarkesh Patel@dwarkesh_sp·Collected 1d ago
📊 Benchmark

X Debate: Dwarkesh Patel's Essay "The Avalanche That Hit Math Is Coming for AI Development" Says He Now Expects Superintelligence by 2030, Drawing 4,100+ Likes and About 820K Views

Podcast host Dwarkesh Patel published a long essay on November 13 subtitled "Why I now expect superintelligence by 2030." He writes that a few months ago he thought superintelligence was at least the better part of a decade away, and now thinks AIs as good as the best humans at AI research are only a couple of years, possibly a couple of months, away. His reasoning: AI has rapidly broken through verifiable domains like math, and AI research is itself largely verifiable. The post has about 820K views and 4,129 likes, quote posts from people like Dan Robinson spread the debate, and X lists it among trending stories. This piece covers one person's views and community discussion, not a verified forecast.

⚡ Key Takeaways
  • •Dwarkesh's post: "The avalanche that hit math is coming for AI development," linking the essay and a narrated video; about 4,129 likes, 346 reposts, 138 replies and roughly 820K views (post)
  • •The core claim: AIs as good as the best humans at AI research are "only a couple of years away, and possibly only a couple of months away"; automating AI research would compress so much progress into one year that AIs at least as good as top experts in every field could arrive by 2030, plausibly as early as next year
  • •Evidence he cites from public sources: METR concluded after three months inside Anthropic that its progress rate on well-scoped tasks is 2x a year earlier; an OpenAI September blog post said its heaviest 10% of researchers went from about $1,000 to over $7,000 a day of internal coding agents; Anthropic said Claude "leads" more than 26% of its AI R&D work as of August
  • •Dan Robinson quoted it saying the footnote on compute bottlenecks "hit me like a sledgehammer" (about 2,461 likes); Dwarkesh followed up that even without a full singularity, the intelligence explosion might compress 4 years of progress into one
  • •Skepticism is part of the thread: one commenter on the essay said this is "not what I am seeing at all" in daily work, and another asked whether agent spend is a good proxy for progress; these are opinions, not established facts
Read details→
F
Federal Reserve@federalreserve·Collected 1d ago
📉 Price Cut

Fed Financial Stability Report: AI is the top-cited risk, named by 87% of contacts; AI computing debt issuance tops $680B as the Fed flags "circular financing"

On November 13 the Federal Reserve published its semiannual Financial Stability Report. Of 23 market contacts surveyed by the New York Fed in September and October, 87% cited AI as a risk to financial stability, up from 50% in the spring and the most of any risk. A box in the report says advanced computing debt issuance passed $680 billion by October, about five times all of 2023, and that leases, guarantees and equity stakes from hyperscalers and GPU makers create a "circular financing" dynamic.

⚡ Key Takeaways
  • •AI was the most-cited risk at 87% (50% in spring), ahead of a risk asset correction at 52%, higher long-term rates at 48%, and cyberattacks and fiscal debt sustainability at 43% each.
  • •Respondents named three AI concerns: stretched valuations and an earnings miss triggering a correction, cyber risk from state actors or frontier models themselves, and complex AI-related financing.
  • •Advanced computing debt issuance passed $680 billion by October (vs $130 billion in all of 2023), rising from under 6% to about 31% of nonfinancial investment-grade corporate issuance.
  • •Not-yet-commenced leases (over $1 trillion undiscounted) plus take-or-pay contracts and residual value guarantees (over $2 trillion) sit off balance sheets, so big tech exposure may be larger than it looks.
  • •The survey reflects respondents only; the report says it does not represent the views of the Fed Board or the New York Fed.
Read details→
E
Elon Musk@elonmusk·Collected 1d ago
🛠️ Tooling

xAI reverses course: Grok API text watermarking is now off by default and opt-in per model, while voice API audio stays watermarked with AudioSeal and is locked on for EU and California users

xAI (signed as SpaceXSI in its docs) has rewritten the "Output Watermarking" page of its API docs: the invisible text watermark that was due to turn on by default on November 7 is now documented as off by default, and team admins can turn it on per model in the Console for grok-4.7, 4.6, 4.5, 4.3, and the three grok-4.20 variants. The page also says the text watermark uses Google DeepMind's SynthID Text. Audio from the voice APIs (Text to Speech, Speech to Speech, custom voices) is watermarked with AudioSeal by default and can be opted out per model, but stays watermarked when the end user is in the EU, the EEA, or California. On November 14, Elon Musk posted on X that text watermarking with Grok is only on where required by law or requested by the user.

⚡ Key Takeaways
  • •Text: off by default; team admins turn it on per model under Team settings → Model output watermarking in the Console, effective within 5 minutes and logged in the audit log (xAI docs)
  • •Technique: the text watermark uses SynthID Text, published by Google DeepMind in Nature in 2024; it slightly shapes token choice and inserts no characters; the detection API is by application
  • •Audio: Text to Speech, Speech to Speech, and custom voices are watermarked with AudioSeal by default and can be opted out per model, but stay watermarked when the request IP puts the user in the EU, the EEA, or California
  • •A single request can force a watermark with the x-watermark: true header (watermark=true on WebSocket URLs); the x-watermark response header shows whether a response was watermarked
  • •Musk said on X that Grok text watermarking is only on where required by law or requested by the user; xAI has not published the exact date of the change
Read details→
J
Jacob Coxon@hilbertspaess·Collected 1d ago
📊 Benchmark

X Debate: Former Anthropic Researcher Jacob Coxon Says a Log-Scale "Pretraining Compute Efficiency" Slide From the IPO Roadshow Was a Big Factor in His Leaving, Drawing 5,200 Likes and About 1.19M Views

At 03:56 Singapore time on November 14, former Anthropic researcher Jacob Coxon (@hilbertspaess) posted a slide from Anthropic's IPO roadshow on X and said it was a big factor in his decision to leave. His reading: the slide shows pretraining compute efficiency over time on a log-scale y-axis, and the curve is still bending upward, which he calls continued superexponential algorithmic progress, with Mythos just one point on that curve. At the time of writing the post has about 1.19M views, 5,212 likes and 321 replies, and X lists the controversy among its trending stories. Critics point out the chart has no axis labels or numbers. This piece covers one person's interpretation and community reactions, not an official Anthropic conclusion.

⚡ Key Takeaways
  • •Coxon's post: "This slide from the Anthropic IPO roadshow was a big factor in my decision to leave," calling the y-axis a log scale and the progress superexponential; about 5,212 likes, 444 reposts and 321 replies (post)
  • •He argues Mythos was not a one-time jump but a point on a superexponential curve, and that Anthropic "could already retrain Mythos with a fraction of the compute originally needed"; he adds this does not strictly imply a software-only intelligence explosion, since R&D spending has also grown
  • •To critics who say the chart has no numbers or units, he replied that compute multipliers are unitless so relative distances still mean something, and that comparing the gain after Mythos with the gain before it needs only three data points (reply)
  • •He says he will not break his NDA to share absolute numbers, citing the trust between Anthropic and its employees, and in a follow-up he argued for pausing frontier development next year, saying it would only hurt OpenAI and Anthropic
  • •This is one person's reading: Anthropic has not publicly responded to Coxon's claims, and the slide's actual values have not been published
Read details→
T
Theo - t3.gg@theo·Collected 1d ago
🛠️ Tooling

X Debate: Theo Says "Software Will Get More Stable Overall Thanks to AI," Drawing 3,300 Likes and 365 Replies as Supporters Cite Cheaper Tests and Fuzzing While Skeptics Worry About Unreviewed Code Shipping

At 12:19 Singapore time on November 14, T3 founder and developer YouTuber Theo (@theo) posted on X: "Hot take: Software will get more stable overall thanks to AI." At the time of writing the post has about 109K views, 3,296 likes, 365 replies and 62 quotes, and X lists the debate among its trending stories. Supporters say AI makes writing tests, reading legacy code, tracing changes and fuzzing much cheaper; skeptics worry that AI writes code far faster than humans can review it, so unread code ships and systems fail in stranger ways. This piece collects community opinions, not a proven conclusion.

⚡ Key Takeaways
  • •The post is one line: "Hot take: Software will get more stable overall thanks to AI," with about 3,296 likes, 365 replies and 62 quotes (post)
  • •For: @rae1101x says much of on-call work is figuring out what changed, so if AI speeds that up outages get shorter even when bugs still ship; @maceskridge says the low-hanging security issues will get patched, after a few years of pain
  • •Conditional yes: @Aly0xDev says AI ships more bugs per hour but also writes the tests nobody wrote, as long as review and CI stay strict; @rxrenan_ says it only holds where someone wrote down what correct means
  • •Against: @callitVer1 says units get more consistent but systems get bigger, less understood and fail in weirder ways; @0xAndyZhou asks who debugs code nobody actually read at 3am
  • •Example cited by @its_ronc: in 2024 Google used LLM-written fuzz targets in OSS-Fuzz and found 26 new vulnerabilities, including one in OpenSSL (Google Security Blog)
Read details→
V
Vahab Mirrokni@mirrokni·Collected 1d ago
🛠️ Tooling

Google Research Shares Antigravity /teamwork Results: Courtade–Kumar Conjecture From 2013 Proved in Full With 50M Lines of Lean 4, Weil Conjectures Formalized Autonomously, and 10,000 Academics Offered Six Months Free

On November 13, Vahab Mirrokni, Google Fellow and VP at Google Research, shared new results from Antigravity's /teamwork multi-agent system on the Google Research blog and X. Researchers from Google, CUHK, USC and CMU used Gemini 4 Argon and other Gemini models to prove information theory's 2013 Courtade–Kumar conjecture in full generality and formalized it in 50 million lines of Lean 4. /teamwork-LEAP also produced a fully autonomous formalization of the Weil conjectures (about 1.8 million lines of Lean across 28,800 subagent runs). On the engineering side, the rest of the Zircon microkernel was rewritten into about 800,000 lines of safe Rust, and 17 JAXBench TPU kernels got a 4.09x geometric-mean speedup. /teamwork and /boost are available in Antigravity now, and 10,000 academic researchers can apply for six months of free access to the top usage tier.

Google Research Shares Antigravity /teamwork Results: Courtade–Kumar Conjecture From 2013 Proved in Full With 50M Lines of Lean 4, Weil Conjectures Formalized Autonomously, and 10,000 Academics Offered Six Months Free
⚡ Key Takeaways
  • •The Courtade–Kumar conjecture (2013) was proved in full and formalized in 50 million lines of Lean 4; Gemini built most of the new analytical bounds and interval-arithmetic certificates, while human researchers proposed the key candidate function
  • •/teamwork-LEAP autonomously formalized the Weil conjectures in about 1.8 million lines of Lean over 28,800 subagent runs, and produced first formalizations of the 1927 Birkhoff conjecture and the 3D Bochner–Riesz conjecture
  • •Engineering results: the rest of Zircon rewritten into about 800,000 lines of safe Rust that pass all kernel unit tests; libgav1 rewritten into about 170,000 lines of Rust that run 20-30% faster than the original C++ and assembly; a 4.09x geometric-mean speedup across 17 JAXBench TPU kernels
  • •/teamwork and /boost are available in Antigravity now, with Hydrogen for everyone and Carbon/Argon for Enterprise and Ultra/paid users; 10,000 academics can apply for six months free; Deep Review gives two free calls per week
  • •These results are self-reported by Google; the blog says preprints and Lean 4 repos are public, and outside verification will take time
Read details→
G
Georgi Gerganov@ggerganov·Collected 1d ago
🛠️ Tooling

llama.cpp and ggml Ship v1.0.0: First Major Version in 3.5 Years Adopts Semantic Versioning, With Breaking C API Changes Now Forcing a Major Bump; Release Drops 35 Deprecated Functions and Adds FP8 KV Caches, a MoE Expert Cache and /v1/audio/speech

On November 13, ggml-org published llama.cpp v1.0.0 on GitHub and announced on the Hugging Face blog that both the llama.cpp and ggml libraries are now at v1.0.0. From here on, breaking changes to the public C API in ./include bump the major version, backward-compatible features, backends and model support bump the minor version, and pure fixes bump the patch version. The release removes 35 deprecated functions, promotes the NextN/speculative decoding API into llama.h, adds OCP FP8 KV caches and a MoE expert cache with a configurable CPU share, supports new architectures such as Kimi-K3.1-Pro, hardens llama-server against SSRF, CORS and DNS rebinding issues, and adds an OpenAI-compatible /v1/audio/speech endpoint. Creator Georgi Gerganovs release post has about 4,180 likes.

llama.cpp and ggml Ship v1.0.0: First Major Version in 3.5 Years Adopts Semantic Versioning, With Breaking C API Changes Now Forcing a Major Bump; Release Drops 35 Deprecated Functions and Adds FP8 KV Caches, a MoE Expert Cache and /v1/audio/speech
⚡ Key Takeaways
  • •Versioning rules: MAJOR = breaking change to the public C API in ./include; MINOR = backward-compatible feature, backend, model support or API addition; PATCH = fix with no API change
  • •Breaking changes: llama_set_warmup, 35 deprecated functions and --defrag-thold are gone, and llama_set_embd_state_src is renamed llama_set_ctx_state_src, so apps embedding libllama need code changes before upgrading
  • •New capabilities: FP8 KV caches (-ctk/-ctv f8_e4m3), a MoE expert cache (moe_cache_size, moe_cache_cpu_share) and loading external PLE shards via --shard/--ple
  • •llama-server is hardened against SSRF, CORS, DNS rebinding and MCP tool cancellation issues, gains an OpenAI-compatible /v1/audio/speech endpoint and a redesigned web UI (GitHub release)
  • •Distribution channels include Docker, Debian, Homebrew, conda-forge, MacPorts, Winget and XCFramework; the project supports more than 150 architecture variants
Read details→
G
Gavin Baker@GavinSBaker·Collected 1d ago
🛠️ Tooling

X Debate: Altimeter and Atreides Send a Joint Letter Urging NVIDIA's Board Not to Rush Replacing Jensen Huang and to Keep His Return on the Table, as Elon Musk Says He Will Sign a Petition to Reinstate Him and Gavin Baker Says About 20,000 Have Signed

At 08:34 Singapore time on November 14, Atreides Management managing partner and CIO Gavin Baker (@GavinSBaker) posted on X a letter that he and Altimeter Capital CEO Brad Gerstner sent to NVIDIA's board. Writing as shareholders, they ask the board to run a "slow, measured, and deliberate process" on NVIDIA's future leadership that leaves all options open, including Jensen Huang's return, and to avoid rushing to replace him before the facts are known; they add that Interim CEO Colette Kress and her team can lead capably in the meantime. The post has about 1.35M views, 9,580 likes and 1,160 reposts. Earlier, Elon Musk replied that "a petition is underway to reinstate Jensen and I'm signing it too," a reply with about 207K likes. Baker later said the petition had roughly 20,000 signatures, including about 2,000 NVIDIA employees (his own claim, not independently verified). There is pushback too: Tesla senior staff engineer Yun-Ta Tsai argued that employees who really want Huang back should resign to make the point. This is a community discussion; NVIDIA's board has not publicly responded to the letter or the petition.

⚡ Key Takeaways
  • •Signed by Altimeter Capital CEO Brad Gerstner and Atreides Management managing partner and CIO Gavin Baker; Baker calls it a first for Atreides (post)
  • •The ask: a slow, deliberate process on future leadership that keeps Jensen Huang's return possible; if the board still decides against it once the facts are known, that is the board's prerogative
  • •Elon Musk replied on November 14 (04:51 Singapore time) that he would sign a petition to reinstate Huang; the reply has about 207K likes and 7.3M views (post)
  • •Baker says the petition has about 20,000 signatures, including about 2,000 NVIDIA employees, and that he backs reinstating Huang while an independent investigation runs; the counts are his claim
  • •Pushback: Tesla engineer Yun-Ta Tsai's post (about 17K likes) says employees should resign to make the point; NVIDIA has not responded, and the November 17 (US time) earnings call is the next thing to watch
Read details→
H
Harrison Chase@hwchase17·Collected 1d ago
🛠️ Tooling

LangChain Raises $300M Series C at a $3B Valuation Led by CapitalG, Betting on LangSmith to Run, Improve and Govern Agents, With New Features Due November 20

LangChain co-founder and CEO Harrison Chase announced on November 13, on the company blog and on X, that LangChain has raised a $300 million Series C at a $3 billion valuation. Existing investor CapitalG led the round, with new investors GIC and DFJ Growth and existing investors IVP and Sapphire Ventures, bringing total funding to $460 million. The money backs LangSmith, its framework-agnostic agent platform, which the company says more than 7,000 organizations use; new LangSmith capabilities will be shown at a release event on November 20.

⚡ Key Takeaways
  • •The numbers: a $300M Series C at a $3B valuation, bringing total funding to $460M (LangChain blog, Business Wire release)
  • •Investors: CapitalG led, with new investors GIC and DFJ Growth and existing investors IVP and Sapphire Ventures; Salesforce Ventures, Insight, MongoDB Ventures and others joined, and Sequoia and Benchmark doubled down
  • •LangSmith is pitched as a framework-agnostic platform with three pillars, Agent Runtime, Agent Improvement and Agent Governance, running in LangChain's cloud, self-hosted, or in a customer's own AWS, Azure or Google Cloud account
  • •Scale figures are company-reported: more than 7,000 organizations use LangSmith, and CapitalG says the open-source projects have passed 1 billion downloads and now see more than 350 million a month
  • •Next up: a special release event on Friday, November 20 (US time) with several new LangSmith capabilities; the features have not been disclosed in advance
Read details→