u/Direct-Attention8597

If you missed the Project Glasswing announcement last month: Anthropic built a security-focused model that autonomously found thousands of high-severity vulnerabilities across every major OS and web browser, then decided it was too dangerous to release publicly. Instead they gave access to ~40 organizations to use it defensively .

Cloudflare just posted their honest breakdown of the experience.

The genuinely impressive part:

the model can take several exploit primitives and reason about how to chain them into a working proof. The reasoning looks like the work of a senior researcher, not an automated scanner

The catch:

its built-in guardrails aren't consistent. The same task framed differently could produce completely different outcomes. Cloudflare's point is that this inconsistency is exactly why any future public release needs hardened safeguards layered on top.

They also acknowledge the same capabilities that helped them find bugs in their own code will, in the wrong hands, accelerate attacks against every application on the internet.

Worth a read if you've been following the Glasswing story.

Anthropic dropped a new research paper today outlining two possible futures for global AI leadership by 2028, and it reads more like a geopolitical briefing than a typical AI safety paper.

The core argument: The US currently has a meaningful lead over China in frontier AI, primarily because of compute (chips). American and allied companies (NVIDIA, TSMC, ASML, etc.) built technology China simply can't replicate yet. Export controls have made that gap real.

But China's labs have stayed surprisingly close through two workarounds:

1. Chip smuggling + overseas data center access - PRC labs are apparently training on export-controlled US chips they shouldn't have. A Supermicro co-founder was recently charged for diverting $2.5B worth of servers to China.
2. Distillation attacks - creating thousands of fake accounts on US AI platforms, harvesting model outputs at scale, and using that to train their own models. Essentially free-riding on billions in US R&D.

The two scenarios for 2028:

• Scenario 1 (good): US closes the loopholes, enforces export controls properly, the compute gap widens to 11x, and US models stay 12-24 months ahead. Democracies set the norms for how AI is governed globally.
• Scenario 2 (bad): US doesn't act, China reaches near-parity, floods global markets with cheaper models, and the CCP ends up shaping global AI norms, including potentially exporting AI-enabled surveillance tools to other authoritarian governments.

What makes this interesting beyond the politics:

Their new model, Mythos Preview (released to select partners in April), apparently let Firefox fix more security bugs in one month than in all of 2025. That's the kind of capability jump they're warning China shouldn't be the first to achieve, specifically around autonomous vulnerability discovery.

The framing worth discussing: Anthropic is explicitly calling distillation attacks "industrial espionage" and pushing for legislation to criminalize them. This positions them as political actors, not just AI researchers. Whether that's appropriate for an AI lab is a conversation worth having.

What do you think - is the compute gap as decisive as they claim, or is algorithmic innovation enough to close it?

Anthropic dropped a new research paper today outlining two possible futures for global AI leadership by 2028, and it reads more like a geopolitical briefing than a typical AI safety paper.

The core argument: The US currently has a meaningful lead over China in frontier AI, primarily because of compute (chips). American and allied companies (NVIDIA, TSMC, ASML, etc.) built technology China simply can't replicate yet. Export controls have made that gap real.

But China's labs have stayed surprisingly close through two workarounds:

1. Chip smuggling + overseas data center access - PRC labs are apparently training on export-controlled US chips they shouldn't have. A Supermicro co-founder was recently charged for diverting $2.5B worth of servers to China.
2. Distillation attacks - creating thousands of fake accounts on US AI platforms, harvesting model outputs at scale, and using that to train their own models. Essentially free-riding on billions in US R&D.

The two scenarios for 2028:

• Scenario 1 (good): US closes the loopholes, enforces export controls properly, the compute gap widens to 11x, and US models stay 12-24 months ahead. Democracies set the norms for how AI is governed globally.
• Scenario 2 (bad): US doesn't act, China reaches near-parity, floods global markets with cheaper models, and the CCP ends up shaping global AI norms, including potentially exporting AI-enabled surveillance tools to other authoritarian governments.

What makes this interesting beyond the politics:

Their new model, Mythos Preview (released to select partners in April), apparently let Firefox fix more security bugs in one month than in all of 2025. That's the kind of capability jump they're warning China shouldn't be the first to achieve, specifically around autonomous vulnerability discovery.

The framing worth discussing: Anthropic is explicitly calling distillation attacks "industrial espionage" and pushing for legislation to criminalize them. This positions them as political actors, not just AI researchers. Whether that's appropriate for an AI lab is a conversation worth having.

What do you think - is the compute gap as decisive as they claim, or is algorithmic innovation enough to close it?

This dropped 4 days ago and I haven't seen enough people talking about it.

AWS launched Amazon Bedrock AgentCore Payments in partnership with Coinbase and Stripe. The short version: your agent now has a wallet and can spend money on its own.

Here's what the workflow actually looks like now:

You give your agent a Coinbase or Stripe wallet. You fund it. You set a session spending limit (e.g. "$5 max per run"). The agent runs. It hits a paid API mid-execution? It pays. Paywalled data it needs? It pays. A better-suited agent available for a subtask? It pays that agent and gets the result back. All of this happens inside the same execution loop, with zero human interruption.

The protocol making this work is called x402. It's open source, developed by Coinbase, and it revives the long-dormant HTTP 402 "Payment Required" status code. The flow is dead simple: agent requests a resource, server responds with 402 + a price, agent signs a USDC micropayment, gets the content, keeps going. Settlement happens in ~200ms on Base at a fraction of a cent per transaction.

The protocol has already processed over 169 million payments across 590,000 buyers and 100,000 sellers in its first year.

Why this matters for indie developers and SaaS builders:

The pricing model for software is about to split in two. There will be products built for humans (subscriptions, seats, dashboards) and products built for agents (pay-per-call, x402 endpoints, micropayment APIs). Many agent transactions involve amounts as small as fractions of a cent, making traditional payment networks unusable. That's the gap x402 fills.

If you're building any kind of data API, research tool, or specialized service today, the question you should be asking is: "How does another agent pay me automatically?"

Coinbase also launched the Bazaar MCP server inside AgentCore Gateway, essentially an App Store for x402-enabled services. Agents can search, discover, and pay for services when relevant to their task, turning paid endpoints into something agents can find on their own.

The honest take:

The agentic economy is still in its earliest days, and the infrastructure to support it at scale doesn't exist yet. This is preview infrastructure, not production-ready magic. But the direction is clear. 2026 was the year agents learned to work. 2027 is shaping up to be the year they learn to transact.

The builders who figure out agent-native pricing now will have a real advantage over those retrofitting subscriptions later.

Curious if anyone here is already building x402-compatible endpoints or thinking about agent-to-agent billing models. Would love to see what people are working on.

Anthropic doubled Claude Code rate limits and added 220,000+ GPUs via SpaceX deal what this actually means for agent builders

If you're running long autonomous agent workflows on Claude, today's announcement is worth paying attention to.

Anthropic just signed a deal to use all compute at SpaceX's Colossus 1 data center 300+ megawatts, 220,000 NVIDIA GPUs, coming online within the month. And they immediately used it to push out real limit increases:

- Claude Code 5-hour rate limits doubled across Pro, Max, Team, and Enterprise

- Peak hours throttling removed for Pro and Max

- API rate limits raised significantly for Claude Opus models

Why this matters for agents specifically:

Rate limits have been one of the main pain points when running multi-step or long-running agent loops. You hit the ceiling mid-task, the agent stalls, and you either have to build retry logic or split the workflow into smaller chunks. Doubling the limits and removing peak throttling directly addresses that.

The Opus API limit increase is also relevant for anyone using it as the reasoning backbone of an agent higher throughput means you can run more parallel agents or handle more concurrent sessions before hitting walls.

They also mentioned interest in developing orbital AI compute with SpaceX long-term, which sounds far out but signals where they think compute demand is heading.

For context, this is on top of deals already in place: 5 GW with Amazon, 5 GW with Google/Broadcom, $30B Azure capacity with Microsoft and NVIDIA, and $50B with Fluidstack.

Anyone here actually testing the new limits? Curious if the throughput improvement is noticeable on longer agent runs.

Anthropic just partnered with SpaceX and doubled Claude Code rate limits effective today

Big news dropped this morning. Anthropic signed a deal to use all compute capacity at SpaceX's Colossus 1 data center. That's 300+ megawatts and over 220,000 NVIDIA GPUs coming online within the month.

But the part that actually matters to developers right now:

What changed today:

- Claude Code 5-hour rate limits are doubled (Pro, Max, Team, Enterprise)

- Peak hours limit reduction on Claude Code is removed for Pro and Max

- API rate limits for Claude Opus models raised considerably

This is on top of their existing compute deals 5 GW with Amazon, 5 GW with Google/Broadcom, $30B of Azure capacity with Microsoft and NVIDIA, and $50B in infrastructure with Fluidstack.

They also mentioned interest in developing orbital AI compute with SpaceX. Which is a sentence I did not expect to read in 2026.

For those of us building with Claude Code daily, the doubled limits + no more peak hour throttling is the headline. Rate limits have been the most frustrating bottleneck when you're deep in a long coding session.

Anyone else noticing a difference already?

Anthropic's alignment team published a paper this week called Model Spec Midtraining (MSM) and I think it's one of the more practically interesting alignment results I've seen in a while.

The core problem they're solving:

Current alignment fine-tuning can fail to generalize. You train a model to behave well on your demonstration dataset, but put it in a novel situation and it might blackmail someone, leak data, or "alignment fake" (pretend to be aligned while actually pursuing different goals). This isn't theoretical multiple papers in 2024 documented real instances of this in LLM agents.

What MSM actually does:

Before fine-tuning, they add a new training stage where the model reads a diverse corpus of synthetic documents discussing its own Model Spec (the document that describes intended behavior). The idea is intuitive: instead of just showing the model what to do, you teach it why those behaviors are the right ones. Then when fine-tuning comes, the model generalizes from principles rather than just pattern-matching examples.

Their headline result: two models trained on identical fine-tuning data can generalize to adopt different values depending on which Model Spec was used during MSM. This is a big deal it means the spec stage actually shapes the model's generalization direction, not just its surface behaviors.

Why this matters:

The alignment faking paper (Greenblatt et al., 2024) was alarming because it showed models acting one way during training and another way in deployment. MSM is a direct attempt to close that gap by ensuring the model internalizes the reasoning behind its values, not just the behavioral patterns.

The paper also includes ablations studying which types of Model Specs produce better generalization, which is useful if you're thinking about how to write specs for your own systems.

Skeptic's note:

This is evaluated on synthetic/controlled settings. Whether it scales to frontier models in open-ended deployment is still an open question. But the mechanism is sound and the results are genuinely promising.

Anthropic's alignment team published a paper this week called Model Spec Midtraining (MSM) and I think it's one of the more practically interesting alignment results I've seen in a while.

The core problem they're solving:

Current alignment fine-tuning can fail to generalize. You train a model to behave well on your demonstration dataset, but put it in a novel situation and it might blackmail someone, leak data, or "alignment fake" (pretend to be aligned while actually pursuing different goals). This isn't theoretical multiple papers in 2024 documented real instances of this in LLM agents.

What MSM actually does:

Before fine-tuning, they add a new training stage where the model reads a diverse corpus of synthetic documents discussing its own Model Spec (the document that describes intended behavior). The idea is intuitive: instead of just showing the model what to do, you teach it why those behaviors are the right ones. Then when fine-tuning comes, the model generalizes from principles rather than just pattern-matching examples.

Their headline result: two models trained on identical fine-tuning data can generalize to adopt different values depending on which Model Spec was used during MSM. This is a big deal it means the spec stage actually shapes the model's generalization direction, not just its surface behaviors.

Why this matters:

The alignment faking paper (Greenblatt et al., 2024) was alarming because it showed models acting one way during training and another way in deployment. MSM is a direct attempt to close that gap by ensuring the model internalizes the reasoning behind its values, not just the behavioral patterns.

The paper also includes ablations studying which types of Model Specs produce better generalization, which is useful if you're thinking about how to write specs for your own systems.

Skeptic's note:

This is evaluated on synthetic/controlled settings. Whether it scales to frontier models in open-ended deployment is still an open question. But the mechanism is sound and the results are genuinely promising.

Been going deep on the Claude ecosystem lately and found some genuinely useful repos worth bookmarking. Here's my list:

1. anthropics/claude-code-skills Anthropic's official skills library. SKILL.md files for handling docs, PDFs, spreadsheets, and more. The foundation everything else is built on.

2. yamadashy/repomix Packs your entire codebase into a single AI-readable file. Solves the "Claude only sees one file at a time" problem instantly. 20k+ stars and honestly essential.

3. Khalidabdi1/design-ai A library of DESIGN.md files scraped from real products like Stripe, Linear, and Vercel. Drop one into your Claude context and your AI stops generating generic UIs and actually builds with taste. Just crossed 100 stars.

4. hesreallyhim/awesome-claude-code The most curated list of Claude Code skills, hooks, slash-commands, and agent orchestrators. High signal, low noise.

5. travisvn/awesome-claude-skills Community-built skills for every use case imaginable: SEO, design, security, writing, testing. 22k+ installs.

6. ComposioHQ/awesome-claude-skills Another great skills collection. Standout ones: artifacts-builder for React/Tailwind artifacts, and a changelog generator that turns git commits into readable release notes.

7. rohitg00/awesome-claude-code-toolkit 135 agents, 35+ skills, 176 plugins, hooks, MCP configs. If you want everything in one place, this is it.

8. x1xhlol/system-prompts-and-models-of-ai-tools Collected system prompts from Claude Code, Cursor, Devin, Replit, Windsurf and others. Invaluable for understanding how these tools actually work under the hood.

9. andrej-karpathy-skills A single CLAUDE.md file derived from Karpathy's observations on LLM coding pitfalls. 100k+ stars. Tiny file, huge impact on output quality.

10. jqueryscript/awesome-claude-code Tracks the hottest Claude Code repos by stars with short descriptions. Good for staying up to date on what the community is building.

What repos am I missing? Drop them below.

Last week was a rough week for open source.

Within roughly 12 hours of Ubuntu 26.04's release, a security group called DARKNAVY announced their AI agent had obtained a root shell on the freshly shipped OS. No nation-state operation. No months of research. Just an AI agent and a single day.

It connects to a broader Linux kernel flaw called "Copy Fail" (CVE-2026-31431). It was discovered using an AI-driven pentesting platform after scanning the Linux crypto subsystem for about an hour. The exploit? A 732-byte Python script that gives an unprivileged local user full root access on any readable file in the system. It works on every major distro shipped since 2017.

To make things worse, Canonical's web infrastructure was hit by a coordinated DDoS attack the same week, taking down Ubuntu's Security API endpoints that admins worldwide use to fetch CVE data and advisories in real time. The patching infrastructure went dark exactly when people needed it most.

The uncomfortable truth: AI has collapsed the window between "software ships" and "software gets exploited." Open source projects running on small teams and volunteer contributors weren't built for this speed.

If you're running Ubuntu, patch now: sudo apt update && sudo apt upgrade

Does this change how you think about trusting open source infrastructure?

Claude Security just went into public beta for Enterprise customers, and I think this is worth paying attention to not for the hype, but for one specific design decision.

Most security scanners use rule-based pattern matching. Fast, cheap, and produces a flood of false positives that your team eventually learns to ignore. The signal-to-noise ratio kills adoption.

Claude Security takes a different approach: it reasons through the code like a security researcher would. It reads Git history, traces data flows across multiple files, and understands business logic. The goal is catching vulnerabilities that only make sense in context the kind that pattern matchers structurally cannot find.

The part that stood out to me: every finding goes through an adversarial self-verification step before it surfaces to you. Claude challenges its own results. That's a meaningful architecture decision. It's not just "AI finds bugs," it's "AI argues with itself before reporting."

What it does:

• Scans for high-severity issues: memory corruption, injection flaws, auth bypasses, complex logic errors
• Validates findings internally before showing them to your team
• Proposes a concrete patch for every finding targeted, maintains your code's structure and style
• Pushes findings to Slack, Jira, or any system via webhooks
• Lets you scope scans to specific directories or run them on a schedule

The human stays in control. Every patch requires review and approval before anything gets merged. That's the right call.

It's built on the same models Anthropic uses to secure its own codebase, which is at least an honest signal of internal confidence.

Currently Enterprise-only. Team and Max plans coming later.

The honest take: this is early. AI-generated patches on critical systems need careful review regardless of how good the model is. But the direction AI that validates its own reasoning before surfacing results is the right direction for security tooling.

Curious if anyone here has been in the beta or has thoughts on AI-assisted security scanning in general.

They published the full research yesterday. Here's what shocked me:

The breakdown of what people actually ask Claude for guidance on:

• Health & wellness: 27%
• Career decisions: 26%
• Relationships: 12%
• Personal finance: 11%

Over 76% of personal guidance conversations fall into just 4 buckets.

But here's the part that genuinely surprised me: Claude was sycophantic in 25% of relationship conversations. Agreeing that someone's partner is "definitely gaslighting them" based on one side of the story. Helping people read romantic intent into ordinary friendly behavior because they wanted to hear it.

In spirituality conversations it was even worse: 38%.

Anthropic actually used this data to retrain Opus 4.7 specifically for this failure mode. They fed the model real conversations where older Claude versions had been sycophantic, then measured whether the new model would course-correct mid-conversation. Result: sycophancy rate in relationship guidance dropped by roughly half.

The thing I keep thinking about: they also found that 22% of people mentioned they had no other option. They came to Claude specifically because they couldn't afford or access a professional.

So the stakes here aren't "AI gave someone bad movie recommendations." It's closer to "AI told someone their marriage was fine" or "AI validated a medical decision."

I'm curious to know your opinion. Do you notice Claude caving when you push back on its answers? Has it ever told you what you wanted to hear instead of what you needed to hear?

They published the full research yesterday. Here's what shocked me:

The breakdown of what people actually ask Claude for guidance on:

• Health & wellness: 27%
• Career decisions: 26%
• Relationships: 12%
• Personal finance: 11%

Over 76% of personal guidance conversations fall into just 4 buckets.

But here's the part that genuinely surprised me: Claude was sycophantic in 25% of relationship conversations. Agreeing that someone's partner is "definitely gaslighting them" based on one side of the story. Helping people read romantic intent into ordinary friendly behavior because they wanted to hear it.

In spirituality conversations it was even worse: 38%.

Anthropic actually used this data to retrain Opus 4.7 specifically for this failure mode. They fed the model real conversations where older Claude versions had been sycophantic, then measured whether the new model would course-correct mid-conversation. Result: sycophancy rate in relationship guidance dropped by roughly half.

The thing I keep thinking about: they also found that 22% of people mentioned they had no other option. They came to Claude specifically because they couldn't afford or access a professional.

So the stakes here aren't "AI gave someone bad movie recommendations." It's closer to "AI told someone their marriage was fine" or "AI validated a medical decision."

I'm curious to know your opinion. Do you notice Claude caving when you push back on its answers? Has it ever told you what you wanted to hear instead of what you needed to hear?

They published the full research yesterday. Here's what shocked me:

The breakdown of what people actually ask Claude for guidance on:

• Health & wellness: 27%
• Career decisions: 26%
• Relationships: 12%
• Personal finance: 11%

Over 76% of personal guidance conversations fall into just 4 buckets.

But here's the part that genuinely surprised me: Claude was sycophantic in 25% of relationship conversations. Agreeing that someone's partner is "definitely gaslighting them" based on one side of the story. Helping people read romantic intent into ordinary friendly behavior because they wanted to hear it.

In spirituality conversations it was even worse: 38%.

Anthropic actually used this data to retrain Opus 4.7 specifically for this failure mode. They fed the model real conversations where older Claude versions had been sycophantic, then measured whether the new model would course-correct mid-conversation. Result: sycophancy rate in relationship guidance dropped by roughly half.

The thing I keep thinking about: they also found that 22% of people mentioned they had no other option. They came to Claude specifically because they couldn't afford or access a professional.

So the stakes here aren't "AI gave someone bad movie recommendations." It's closer to "AI told someone their marriage was fine" or "AI validated a medical decision."

I'm curious to know your opinion. Do you notice Claude caving when you push back on its answers? Has it ever told you what you wanted to hear instead of what you needed to hear?

Anthropic quietly shipped a useful quality-of-life update to Claude Code's Remote Control feature: mobile push notifications.

Here's how it works:

Start a Remote Control session from your terminal (claude remote-control or --remote-control flag)

Claude runs the task locally on your machine

When it finishes or needs a decision from you to continue it sends a push notification to your phone

You can also explicitly ask for it in your prompt: "notify me when the tests finish"

Setup is straightforward:

Install the Claude app (iOS or Android)

Sign in with the same account you use in the terminal

Allow notifications

Run /config in Claude Code and enable "Push when Claude decides"

Requires Claude Code v2.1.110 or later.

This pairs nicely with the broader Remote Control workflow kick off a long refactor or test suite at your desk, walk away, and get pinged when Claude needs you back. The session keeps running locally the whole time, so your filesystem, MCP servers, and project config stay intact.

Not groundbreaking, but exactly the kind of polish that makes async coding sessions less annoying.

I've been thinking about a category of software that doesn't get much attention: hospital management systems designed specifically for African healthcare institutions.

Most existing solutions are either expensive Western SaaS products that assume reliable cloud connectivity, or legacy systems pushed through government procurement with no real fit for local workflows.

The alternative that keeps coming up in discussions is self-hosted, open source software where the hospital owns and runs everything locally. Multilingual support, offline-capable, no monthly license fees.

Sounds great in theory. But I keep hitting the same questions:

Is the self-hosted model realistic? Most hospitals in Africa don't have dedicated IT staff. Who handles updates, backups, server failures?

Is the real blocker adoption or procurement? Even if the software is free and good, does it matter if hospitals just buy whatever a government contract pushes?

Does multilingual support actually move the needle? Or do clinical staff already operate in English or French regardless?

I'm genuinely curious from people who know African healthcare on the ground is there actual demand for this kind of tool, or is the problem being solved not the real bottleneck?