找到 212 篇相关文章
Anthropic just announced Claude Fable 5, a new AI model it said is the most powerful model it has ever made widely available. According to the company, Fable 5 "shows exceptional performance in software engineering, knowledge work, and vision," with its lead over other models growing as tasks become longer and more complex. Fable 5 […]
As expected, yesterday's WWDC keynote was mostly about AI. And also as expected, Apple tried to turn its late arrival into its sales pitch: it didn't rush into AI because it was taking its time to do things right. In this case, "right" means "with more privacy than anyone else." It's a good pitch - […]
The 30-second version Anthropic shipped Claude Opus 4.8 a few hours ago. Every benchmark on the announcement page is up: SWE-bench Verified, GPQA, MATH-500, the agentic tool-use evals. The marketing copy reads as it always does — "our most capable model", "strongest coding performance", "better instruction following". If you have been around since 4.5, you know the shape of this announcement by heart now. The announcement skipped the only question that matters for teams running Claude in production: should you upgrade today, next week, or next month, and which of your workloads should stay on Opus 4.7 indefinitely? Anthropic does not write that part. They cannot — it is workload-dependent, and the answer for a code-review agent is different from the answer for a customer-facing chat product. This post is the decision tree I am applying to my own stack today. It is opinionated. Three of the workloads I run are staying on 4.7 until at least mid-July, and I will explain exactly why. Your mileage will vary, but the reasoning shape should transfer. What actually shipped in Opus 4.8 Let me anchor on the facts before the opinion. Opus 4.8 is the third release in the Opus 4.x family this year. The pattern across 4.6 (March), 4.7 (April), and 4.8 (today) has been roughly monthly. Each release has shipped a 2-4 point bump on SWE-bench Verified and a similar bump on the agentic evals. 4.8 follows the pattern: roughly 3 points on SWE-bench, about 2 points on the multi-step tool-use benchmark, and a more visible jump on the long-context retrieval evals — the 'needle in a haystack at 200K tokens' style tests. Three changes are worth pulling out of the announcement: Better long-context coherence . The 4.8 release notes specifically call out improved behavior on tasks that span more than 100K tokens of context. Concretely: less mid-context summarization, fewer instances of the model 'forgetting' early-context instructions, better citation of source material when retrieved chunks sp
OpenAI on Monday checked off a preliminary step in the IPO race that it and rival Anthropic have been competing in for the better part of a year: The company announced it has confidentially submitted a Form S-1 with the US Securities and Exchange Commission, following Anthropic's decision to do the same on June 1st. […]
80%. That is the share of code currently being merged into Anthropic's production systems that was written by Claude. Not code-reviewed. Not pair-programmed. Written. In February 2025, when Claude Code launched, that number was in the low single digits. Sixteen months later, the company decided that data point — and the trajectory behind it — was worth a public warning. On June 4, 2026, Anthropic published "When AI Builds Itself," a research paper co-authored by Marina Favaro, head of the Anthropic Institute, and Jack Clark, one of the company's co-founders. It was the first major publication from the Anthropic Institute since its founding in March 2026. The paper did two things simultaneously: disclosed internal productivity data that most AI companies keep private, and called for a global mechanism to slow or pause frontier AI development before the process becomes self-sustaining without meaningful human direction. The data came first. The policy recommendation followed from it. Here is what the numbers actually show and why every developer building on AI infrastructure today should read this carefully. The Productivity Curve Nobody Predicted Anthropic published a chart of engineering output per engineer, indexed to a baseline from 2021–2024. The curve is flat for four years. Then Claude Code shipped in February 2025. The multiplier progression from that point: 1.2x, 1.5x, 1.9x, 2.5x. By Q1 2026: 5.8x. By Q2 2026: 8x. The typical Anthropic engineer is now merging eight times as much code per day as they were in 2024. Not 8% more. Eight times more. That is not a productivity improvement — it is a different category of output from the same headcount. To understand what drives the number, you need to understand what Claude Code actually does inside Anthropic's engineering workflows. The tool was built for and by engineers working on frontier AI systems — which means the tasks it handles are not boilerplate CRUD endpoints. Claude is writing test harnesses for novel m
The signal hidden in this week's GitHub trending Two agent-shaped repositories cracked the daily GitHub trending board this week. The first is mvanhorn/last30days-skill , a Claude-style skill that researches a topic across Reddit, X, YouTube, Hacker News, and Polymarket, then synthesizes a grounded summary. The second is NousResearch/hermes-agent , billed as "the agent that grows with you" — a persistent agent runtime that compounds context across sessions. Both ranked the same week. Both are skill-shaped: a manifest, a trigger, a set of instructions, and a runtime expectation. This is the first time I have seen two skill repos chart simultaneously on GitHub trending. Most observers will treat them as cool side projects, fork them, star them, and move on. They are cool side projects. They are also a phase transition that the agent ecosystem has been edging toward for nine months. By Q4 you are going to wish you had read this signal in early June, because the dependency-graph problem about to land in production agents is the same one the npm ecosystem ran into between 2011 and 2018 — except faster, less tooled, and with a much larger blast radius. This post is about that phase transition. The benchmark coverage of skills is everywhere; what you cannot easily find is a working operational model for managing them at fleet scale. I am going to give you one. What actually shipped this week Let me anchor on the facts before I extrapolate. last30days-skill (mvanhorn) is a single skill bundle. Its SKILL.md tells the host agent: when the user asks for recent news, controversy, or sentiment on a topic, run a structured multi-source fetch — eight queries minimum, across five platforms, with a freshness window of 30 days — then synthesize. The skill ships with prompt scaffolding, query templates, and a synthesis rubric. It is roughly 600 lines including instructions and helper scripts. Installation is a git clone into your skill directory, no package manager, no version negotia
We're likely to see more price increases as the big AI companies plan to go public.
Notion's head of product said he was "astonished" at “the amount of people RT-ing this."
The benchmark is the wrong story Anthropic shipped Claude Opus 4.8 this week. You probably saw the announcement post on Tuesday, the swarm of benchmarks on X by Wednesday, and somebody's curated leaderboard of "the new SOTA on SWE-bench Verified" by Thursday morning. By Friday everyone had moved on. That is the normal shape of a model release in 2026. It is also the wrong story. The benchmark delta from 4.7 to 4.8 is real but not load-bearing. The load-bearing story is the calendar. Opus 4.6 shipped late February. Opus 4.7 shipped in April. Opus 4.8 shipped this week, in early June. Three Opus generations inside four months. Whatever the headline numbers say about coding, agentic reasoning, or long-horizon tool use, the operating reality has already changed underneath you: if you run a production agent on a fixed model pin, you are now eating a migration tax every six to ten weeks. You can either notice that now and refactor, or notice it in late August when Opus 4.9 lands and your customer-facing agent regresses for the third time this year. This post is the second story. I am going to skip the benchmark recap — go read the model card — and tell you what to do before the next release lands. What Anthropic shipped The announcement post on anthropic.com confirmed three things and implied a fourth. The three confirmed: Opus 4.8 is the new default Opus tier model, ID claude-opus-4-8 . The previous defaults (4.7 and 4.6) remain accessible by explicit pin for at least 90 days. Fast mode is available on 4.8 the same way it shipped on 4.7 — same model weights, higher-throughput inference path, no quality downgrade. That matters because the practical difference between Opus and Sonnet for many workloads now comes down to fast-mode availability, not raw capability. The model card claims meaningful improvement on long-context coherence, agentic tool dispatch, and refusal calibration. The benchmarks back this up to roughly the degree we expect from a 6-week cycle — modest but
SpaceX won’t get easy access to billions of dollars from passive investors.
While the AI fundraising machine keeps breaking its own records, some founders are building in the other direction. Mirror founder Brynn Putnam just raised money for Board, a startup focused on bringing people together through in-person games and social experiences. Cyberdeck creators are going viral crafting whimsical DIY computers that literally encourage users to touch grass. Unlike the AI-free browser crowd, this doesn’t just feel like backlash, […]
The U.S. eavesdropping agency is reportedly preparing Anthropic's Mythos for use in cyberattacks, despite a federal ban on using the AI model maker.
“Why wouldn’t you want to be in both Pepsi and Coke?” says one venture capitalist. “It’s the same here.”
Anthropic has been growing at a breakneck pace. The company announced that annualized revenue crossed $47 billion in May, up dramatically from roughly $9 billion at the end of 2025. That trajectory faces a real test, though.
Estonian government benchmark shows how dozens of models combat Russia's "strategic narratives."
Lovable and Google signed an expanded multiyear deal that involves a 5x expansion of Lovable's footprint on Google Cloud, and expanded access to Anthropic Claude.
Several real estate listings in the San Francisco Bay Area are offering to exchange a home for a piece of the AI startup.
Claude Opus 4.8 shipped today. The benchmarks are a distraction — here is what actually changes about how your agents run tomorrow. Anthropic announced Claude Opus 4.8 at 16:00 UTC on June 3, 2026. The launch post leads with the usual benchmark deltas: SWE-bench Verified up 4.1 points, GPQA Diamond up 2.9, TAU-bench tool-use up 6.4. There is a chart. There is a marketing line about "the most capable agentic model we have ever shipped." If you stop reading there, you will miss the three things that will change how your production agents behave starting tomorrow. I have spent the morning re-running our internal agent harness against Opus 4.8 and reading the model card line by line. Two of the three changes are improvements. One of them is a silent regression that will bite anyone who pinned the model ID. Here is the full picture. What 4.8 actually changes The model card and release notes ship three changes that the launch blog post does not foreground: Cache-aware routing inside long agentic loops. The 4.7 router treated every tool-call cycle as a fresh planning step. 4.8 keeps an internal trace of which cache breakpoints were hit on the previous step and biases the next plan toward extending those traces. In agent harnesses that already use prompt caching aggressively (Claude Code, the Agent SDK with cacheControl: "ephemeral" on the system prompt), cache hit rates jumped from a measured ~46% on 4.7 to ~71% on 4.8 across a 30-step coding loop. The 200k context window now actually behaves at 200k. Anthropic published a needle-in-a-haystack chart in the model card going out to 200,000 tokens. The 4.7 chart got noticeably worse past ~140k tokens; the 4.8 chart is flat. This sounds like a benchmark thing. It is not. It changes the cost equation for "just stuff everything in context" patterns that 4.7 quietly punished by degrading accuracy. claude-opus-4-7 was not aliased. The launch shipped a new model ID — claude-opus-4-8 — and the previous ID is still callable. But if y
Uber's cutback has occurred after the company had reportedly encouraged staff to use AI as much as possible.
Anthropic is expanding Project Glasswing, its security vulnerability program, and access to Mythos to 150 organizations across 15 countries — targeting critical infrastructure in power, water, healthcare, and communications where a cyberattack could affect 100 million people.