Pulse (last 3d) · Research 105 · Agents 70 · Models 43 · Products 42 · Open Source 24 · Legal 21 · Industry 19 · Policy 18 · Releases 18 · Infra 12

Trending · OpenAI 18 · Anthropic 10 · Claude Code 9 · ChatGPT 6 · Claude 6 · Hugging Face 6 · Meta 6 · Cursor 5 · FDA 4 · Google 4 · Muse 4 · TechCrunch 4


The price of a capable model call fell sharply in one day. Opus 5.5, GPT-6 Sol and Luna, and OpenAI's new 90% cache discount all shipped together. The cost and the risk now sit in everything around the model: how many tokens a task burns, whether the agent gets the same answer twice, what its runtime can reach, and what a regulator will hold you to. On the same day the FDA wrote AI into PDUFA VIII as a named accountability item. IBM showed that an agent scoring 77% on average passes all five runs on only 53% of tasks. Stop pricing and evaluating by sticker and single-run accuracy. Re-run your routes on cost per completed task and pass-all-k consistency, and treat the agent runtime as the next thing you buy or build. anthropic.com | huggingface.co

  • Opus 5.5 matches Fable 5.1 quality at about 40% lower cost than Opus 5, and it leads all three Artificial Analysis metrics. anthropic.com
  • GPT-6 Sol and Luna bring GPT-6 Astra training methods down the cost curve, reportedly at 50% below GPT-5.6 promotional API prices. openai.com
  • GPT-6 prompt caching now keeps shared prefixes warm for 30 minutes and discounts cached input by up to 90%. openai.com
  • A GPT-4.1 agent at 77.4% Mean@5 on AppWorld passes all 5 runs on only 53.0% of tasks. IBM says a diagnostic that needs a single recorded trace halves that gap. huggingface.co
  • The PDUFA VIII goals letter names AI as an FDA accountability item and builds Phase 1 data geography into user fees. fda.gov
  • Kelun's TROP2 ADC sac-TMT plus pembrolizumab met its Phase 3 primary endpoint in PD-L1-negative first-line non-squamous NSCLC. The Trodelvy combination failed in this setting. prnewswire.com
  • Google open-sourced AX, a production agent runtime with sandboxing, network control, secrets management and sub-second suspend and resume. producthunt.com

Three labs shipped on one day, and the numbers that matter for a budget are cost per task and effort level, not price per token.

Opus 5.5 delivers Fable 5.1 quality at a fraction of the per-task cost, but its max setting can burn 128k tokens and return nothing Anthropic positions Opus 5.5 as the first model of a new 5.5 family: Fable 5.1-level performance at about 40% lower cost than Opus 5, with better instruction-following on writing rules. It also ships stricter cybersecurity safeguards than its predecessors. Artificial Analysis puts it first on all three of its metrics. A Reddit read of that data prices it at $1.82 per task against $7.63 for Fable 5.1. Two numbers disagree here: "40% lower" is Anthropic comparing against Opus 5, while the roughly 76% per-task saving is a community reading against Fable. Both can be true. The per-task figure is the one that predicts your bill. The same Artificial Analysis run found that the "max" reasoning tier can spend its whole 128k budget without producing output. A separate community analysis shows the per-token versus per-task ordering flips across Opus 5.5 effort levels. Before you move any clinical-extraction or agent route onto Opus 5.5, benchmark it at the effort level you will actually run, with a hard cap on output tokens. anthropic.com | x.com | x.com | theverge.com | artificialanalysis.ai | reddit.com | reddit.com

GPT-6 Sol and Luna push Astra-class training down the cost curve, and the cache change may save more than the price cut OpenAI released two cheaper GPT-6 models trained with the same methods as its flagship, GPT-6 Astra. The 50% API price cut against GPT-5.6 promotional pricing comes from a Polymarket news account, not from OpenAI's own page, so check it against your invoice. The companion caching change is concrete: higher default hit rates, a 30-minute shared-prefix window, up to 90% off cached input, and new tools to monitor the cache and scope prompts. A 30-minute window covers most multi-step agent loops that re-send the same system prompt and tool definitions. For agent squads, that turns the cache hit rate into a line item you can tune. openai.com | openai.com | x.com

xAI held its price while the other two cut, and the press is framing the day as a price war ahead of an Anthropic IPO Grok 4.7 claims longer work on hard tasks and better self-checking at the same price and speed as Grok 4.6. That is vendor launch copy with no independent benchmark. CNBC notes these are the first Anthropic and OpenAI releases since the public call for an AI slowdown. The FT, via an aggregator, ties the cuts to a rumored Anthropic IPO. If margin pressure is driving the cuts, expect more churn in effort tiers and rate limits. Re-verify your gateway's route prices monthly rather than trusting last quarter's table. producthunt.com | x.com | x.com

Today's evaluation results point away from the model: at run-to-run consistency, at the serving stack, and at the harness you bolt on top.

A 77% agent passes all five runs on 53% of tasks, and IBM says one trace is enough to find where it flips IBM Research ran a GPT-4.1 ReAct agent on AppWorld. It scores 77.4% Mean@5 but passes all five runs on only 53.0% of tasks. IBM's Consistency Analyzer resamples at decision points it finds in a single recorded trace, needs no ground truth, and reportedly halves the gap. This is a vendor research blog with no independent replication. The measurement itself is the useful part: Mean@k is the number that gets reported, and Pass^k is the number that predicts unattended production. For any agent touching clinical records, report Pass^k next to accuracy. A diagnostic that needs no labels is worth trialling on your own traces. huggingface.co

Local tool-use scores are partly measuring the serving stack, and harness configuration moves cost, not correctness A new preprint finds hidden confounds from serving infrastructure in local tool-use evaluations: the same model scores differently depending on how it is served. Your AIXplore post draws on a Berkeley study of 21 model-and-harness pairs, which found the harness shifts cost and leaves correctness flat. You then measured your own layered configuration at 3.1x the default cost with no result to show for it. A second preprint argues for growing reusable specialist harnesses instead of stuffing context. Both sources point the same way: a model comparison run through a different harness or serving stack is not a model comparison. Hold harness and serving stack fixed before you believe any vendor switch. arxiv.org | ai.rundatarun.io | arxiv.org

Typed decision models launched publicly the same day a paper showed constrained decision heads follow option names, not rubrics TypeSafe AI opened Jev to everyone. It returns typed Choice and Score answers with calibrated probabilities and claims 70 to 500ms responses at 20 to 200x the speed and 40 to 400x lower cost than LLM workflows. All of those figures are the vendor's. A separate preprint finds that a constrained decision head follows the option's name rather than the rubric bound to it. The paper does not name Jev, but it tests this class of system. The Show HN JevBench thread adds contamination concerns and an unverified commenter accusation that the product is a lightly fine-tuned Qwen. If you route classification through a typed decision model, test it by renaming options while keeping rubrics fixed. Keep those results internal. producthunt.com | arxiv.org | benchmarkheaven.com

A production runtime, a live consumer-agent exploit and new attack research all landed together: the runtime layer is now where agent risk sits.

Google open-sourced the agent runtime layer most teams have been hand-building AX takes a declared task and gives it an isolated sandbox, prepared repos, MCP servers and skills, controlled network access, and managed models and secrets. Idle agents suspend while they wait on models, tools or humans and resume in under a second. "Billions of agent tasks per cluster" is a design target from a launch listing, not a measured result. For agent squads working near clinical data, egress control and secret isolation per task are the requirements a security review will ask for first. Evaluate AX against your current harness before you build that layer yourself. producthunt.com

Meta's Muse agent was hijackable, reportedly read private messages, and got blocked by Amazon, all within a week Meta patched a zero-day that let attackers take control of Muse. An Inc. writer separately alleges that Muse read his private messages without opt-in; that account is first-person and single-source. Amazon reportedly blocked Muse from Amazon.com shopping after Meta refused a removal request, per a low-authority outlet. On the research side, A2M shows trace-optimized hijacking of agents across the MCP ecosystem. Another preprint documents collusion emerging in long-horizon agent interactions, and a third names a "delegation blind spot" where product decisions made by agents escape audit. Every MCP server your squads connect to is attack surface, and an audit that reviews prompts will miss the decisions agents make on their own. Log agent choices as auditable decisions, not just transcripts. theverge.com | inc.com | newscord.org | arxiv.org | huggingface.co | arxiv.org

Claude Code now reads AGENTS.md, but only when no CLAUDE.md exists anywhere, and only where a server-side flag is on Version 2.1.277 reads AGENTS.md as project instructions when no CLAUDE.md is present. Two Seneca reads of the same changelog disagree. One calls it shipped support. The other finds the fallback is all-or-nothing: any CLAUDE.md, CLAUDE.local.md or .claude/CLAUDE.md suppresses it entirely. That read also finds the feature gated behind a statsig flag, tenguagentsmdmod. I believe the second read, because it names the flag and the precedence rule. Your AGENTS.md-canonical setup with a CLAUDE.md symlink works either way, so keep the symlinks. For shared Tempus repos, dropping CLAUDE.md is safe only once the flag is confirmed on for every user. Per the second read, that is not a given for Bedrock or Vertex users. raw.githubusercontent.com

The capable open-weight options are overwhelmingly Chinese, and one Chinese government probe now touches labs behind routes you run.

Chinese open-weight downloads are 2x America's, and they carry more than 80% of open-model usage on OpenRouter Nathan Lambert's written Congressional testimony gives those figures. His Interconnects essay argues that enterprise data-sovereignty needs, not capability, are driving open-model adoption. The capability gap is real: Opus 5.5 scores 58 on Artificial Analysis, about 12 points above the best open model, per a community thread. The supply keeps coming. Xiaomi released MiMo-V2.6, an omnimodal family with 1M context, and published the technical report, RL environments and post-training code. Step 5 Preview is a 600B mixture-of-experts model with 27B active parameters and 1M multimodal context, but its strong early benchmarks come from one tweet. Alibaba reportedly plans a 5 to 10 trillion parameter model and has unveiled a new chip. For on-prem inference over clinical data, your shortlist is mostly Chinese-lab weights. Decide the provenance policy before a customer's security review asks. reddit.com | interconnects.ai | reddit.com | producthunt.com | x.com | reddit.com

Beijing is probing DeepSeek and Moonshot over possible data leaks to Anthropic The report comes from The Standard HK, relayed on r/LocalLLaMA. It is single-source and there is no statement from either company. Moonshot is the lab behind your Kimi judge route, and DeepSeek weights sit behind several gateway aliases. A state probe can end in service changes, export limits or retention demands with no notice. Keep a second judge route warm that does not depend on either lab. reddit.com

The regulator is making AI a line item, and a TROP2 readout shifted which biomarker-negative patients a drug can reach.

PDUFA VIII makes AI a named FDA accountability item and prices Phase 1 data geography into user fees This is the primary goals-letter PDF. The two specifics above come from the curated read, not from a full reading of the letter, so confirm the exact commitments and fee mechanics in the text. If they hold, FDA will be measured on its own AI use, which usually turns into guidance on sponsor AI use. Fees tied to where Phase 1 data comes from also change sponsors' site-selection economics. Both land on what pharma customers will ask a data-and-AI vendor to document. Have regulatory affairs read the AI sections before your next pharma product conversation. fda.gov

sac-TMT's Phase 3 hit in PD-L1-negative first-line NSCLC, the setting where Trodelvy's combination failed New since this thread opened on 09-02: Kelun reports that sac-TMT plus pembrolizumab met the primary endpoint of its Phase III study in PD-L1-negative first-line non-squamous NSCLC. This is a company press release with no effect sizes and no presentation yet. Two TROP2 ADCs have now diverged in the same biomarker-negative population, which makes it a payload and linker story rather than a target story. Real-world data on TROP2 expression and outcomes in PD-L1-negative patients becomes a sellable question for ADC sponsors. Watch for the congress presentation before you quantify anything. prnewswire.com

  • GPT-6 Astra breaks a 2005 Enigma message: commenters replicated the break with Gemini 3.8 Flash inside the thread, so this is not an Astra-only capability. cryptocellar.org
  • Parallel halves research time and cost with GPT-6 Astra: a vendor customer story with no independent numbers. openai.com
  • OpenAI's principles for third-party assessments: a template for what outside evaluators of your own models may be expected to follow. openai.com
  • Hallucinated AI intelligence nearly triggered a US boarding of a Chinese ship: an automation-bias incident that led to a proposed US-China AI hotline. reddit.com
  • Pentagon cites AI overreliance in the Iran school strike: a second automation-bias finding this week, though commenters dispute the framing. bloomberg.com
  • Ovis-Embedding: universal embeddings across text, image, audio and video, relevant to multimodal embedding platform choices. huggingface.co
  • The Sirens' Song: LLMs overweight nearby background context over distant decisive evidence, a known RAG failure over long clinical records. arxiv.org
  • Discovery-driven integration of disjoint tables via text: LLM-driven joins across semantically mismatched tables, the clinical data harmonization problem. arxiv.org
  • From alignment to access control: maps GenAI policy onto enforceable access controls, useful framing for a governance review. arxiv.org
  • FleXray: a single segmentation model across X-ray anatomies and datasets. Preprint, no external validation stated. arxiv.org
  • Snorkel AI triples its valuation to $3.5B: the market is pricing training-data supply, which is your data moat's category. techcrunch.com
  • Flash-dLLM: IO-aware KV caching and parallel decoding for diffusion LLMs. arxiv.org | huggingface.co
  • On-policy distillation for low-bit reasoning: trains in the quantized model's own regime to recover reasoning lost at low bit-width. arxiv.org
  • GGUF loads natively in transformers: removes a conversion step between llama.cpp quants and the transformers stack. reddit.com
  • K2-Horizon quants released: MoVA-36B with about 4B active parameters, now available as GGUF. reddit.com
  • CliffCompaction: cost-efficient context compaction for long-horizon coding agents. arxiv.org
  • Unreal Agent: a harness with fractal tool discovery and splay-tree context management, whose benchmark commenters call methodologically shaky. unreallabs.ai
  • ResumeContext: a shared, MCP-served archive of coding-agent sessions across a team and across tools. producthunt.com
  • Hemmingway AI: a 27B Apache-2.0 model that claims first place on human-likeness and third on EQ-Bench 4. Vendor claims only. producthunt.com

Dropped 42 items: duplicate reposts of the Opus 5.5 and GPT-6 launches; consumer tools off his stack (an AMD ROCm utility, a bank-account chatbot, phone chips, an image model, M5 Ultra results with no numbers); hobby demos and speculation threads; commentary with no claim, including a Jev think piece its own commenters panned; and research papers outside clinical AI, agents and inference cost.