As a result of a US government directive, we are suspending access to Claude Fable 5 for all users. You can continue to use all other Claude models.
Here’s what this means for you:
Across Claude products, new sessions will run on your selected default model or Opus 4.8, and existing Fable 5 sessions will end with an error.
On the Claude Platform, requests to Fable 5 will also return an error. Please update your integrations to other Claude models.
We know this is a disruption to your workflows; we appreciate your patience and support.
As a result of a US government directive, we are suspending access to Claude Fable 5 for all users. You can continue to use all other Claude models.
Here’s what this means for you:
Across Claude products, new sessions will run on your selected default model or Opus 4.8, and existing Fable 5 sessions will end with an error.
On the Claude Platform, requests to Fable 5 will also return an error. Please update your integrations to other Claude models.
We know this is a disruption to your workflows; we appreciate your patience and support.
What I love about Silicon Valley is that the future is up for grabs, ready for anyone to build.
I get intros for angel investing to all kinds of people. I take everyone equally seriously. 2 lads & a dog, or a 5-time award-winning entrepreneur.
No place more meritocratic.
Anthropic pricing for Claude Code feels broken.
We’re currently spending around $800/day (3 users) on token usage on the standard Business plan, which oddly doesn’t include any "Max" tier option, unlike the retail plans.
Out of curiosity, I switched to the Claude Max20 retail plan as an experiment, and the same amount of work/token usage is still comfortably within the limit.
Feels like the pricing model between business and retail plans might need another look 🤔
Right now, the retail pricing seems dramatically better than the actual business offering.
Ghostty is leaving GitHub. I'm GitHub user 1299, joined Feb 2008. I've visited GitHub almost every single day for over 18 years. It's never been a question for me where I'd put my projects: always GitHub. I'm super sad to say this, but its time to go. https://t.co/DQDemHdytV
INSTEAD OF WATCHING NETFLIX TONIGHT
Spend 30 minutes with this.
A speech by the Head of Anthropic's Coding Agents research team that teaches you more about vibe coding than 100 paid courses ever could.
This is not a tutorial.
This is the person who actually builds the system explaining how it works from the inside.
Most people learning to vibe code are learning the surface.
This goes underneath it.
30 minutes tonight.
The people who watch this will build differently tomorrow.
Completely free.
Bookmark this before you open Netflix 👇
Whether design belongs in Figma or Claude Design is a distraction from a bigger shift.
1️⃣ Design will become autonomous. More helpful to think of it as 𝙳𝙴𝚂𝙸𝙶𝙽.𝚖𝚍, used by your coding agents running your software factory.
2️⃣ Specialized “personal” design tools generated by teams will proliferate. Design is a capability, not a tool. I agree with @rsms that there are many facets of design, and multiple tools are required.
I love prompting in @v0 and it’s become the place where I can channel my inspiration, explore, communicate. But I’m also seeing a new generation of products that use the v0 Platform API or Sandbox and put design on autopilot.
There are next-generation agents like @tryflint and https://t.co/fZ7TO6rczt generating design & brand systems and maintaining them autonomously. Flint can even keep your website and content up to date and its design consistent. No human prompting needed.
From this we will see the emergence of fully autonomous companies with agents like https://t.co/YhOmGYYwgE and https://t.co/v8TuIxujwy, which go a step further and grow and advertise your business.
tl:dr; The future looks very different from the present. AI is a true discontinuity. The “here’s the existing thing but with AI and ${jobTitle} is cooked” is short-sighted.
Today, we’re launching a Rather Large™ update to the OpenAI Agents SDK.
Agents SDK now allows you to scale Codex-style agents in production, without building the whole harness yourself. We’ve brought all of the stuff of modern agents: computer-use, skills, memory, compaction, and more to the same platforms you’re already using.
I've been heads down for the past 6 weeks building @To11AI — a platform that unifies LLM observability, routing, and security in one place.
But honestly, the most interesting thing I've learned so far isn't about the product. It's about how we're building it.
We're running to11 as a fully agentic startup from day one. Every workflow we can hand to AI, we do. Coding, research, drafting, ops, go-to market; agents handle the heavy lifting while we focus on judgment and direction.
And here's what's become increasingly clear to me:
New startups have an unfair advantage right now.
When you're starting from zero, there's no legacy process to untangle. No existing team culture to negotiate with. No middle layer of management that needs convincing. You just... build the right way from the start.
For established companies, it's a completely different story.
Transforming into an agentic organization isn't a tooling problem, it's a cultural one. It requires people to let go of workflows they've spent years optimizing. It asks managers to redefine what productivity even looks like on their teams. That kind of change doesn't come from a top-down mandate or a new software subscription. It has to come from within.
And the pressure to make that shift? It's mounting fast.
If you've been watching the public markets, you can see it written all over the earnings calls and analyst notes. Companies that haven't figured out how to structurally embed AI into their operations are starting to show the gap in speed, in headcount efficiency, in their ability to ship.
This isn't about replacing people. It's about whether your organization is architected to move at the speed AI now makes possible.
The startups being founded today that treat agents as first-class team members from week one are building at a fundamentally different velocity. That gap is only going to widen.
We're still early at to11, but this is already one of our core convictions: the agentic-native companies will have structural advantages that are very hard to replicate later.
Curious whether others building right now are seeing the same thing or if you're at a larger org trying to make this shift, what's actually working?
Anthropic just mass-obsoleted every agent orchestration startup in a single launch.
The screenshot tells the full story. That's a production fleet dashboard. 8 agents running. 247 completed tasks. Active status. MCP-connected to HubSpot, pulling deals, generating proposals, reading attachments. This isn't a demo. It's a managed production environment where you define the agent and Anthropic runs the infrastructure.
The timing here is surgical. Four days ago, Anthropic blocked OpenClaw and every third-party harness from using subscription credentials. The message was clear: stop building on top of our consumer auth layer. Now here's the replacement. A first-party managed agent platform with fleet monitoring, production-grade MCP integrations, and prototype-to-launch timelines measured in days.
Manus spent six months on five harness rewrites. LangChain spent a year on four architectures. Anthropic just shipped the managed version that eliminates the need to build one at all.
The real bet: most companies don't want to build agent infrastructure. They want agents that work. Anthropic is pricing this into the platform the same way AWS priced server management into EC2. The 46% of enterprises citing "integration with existing systems" as their primary agent challenge just got a first-party answer from the model provider itself.
Every agent startup that raised on "we make Claude reliable in production" just lost their pitch deck.
Vercel CEO @rauchg: the era of the IC is over. Every person at Vercel acts like a CEO of their own company, and that's by design.
Inspired me to ask myself: where am I waiting for permission I could just take?
My impression from visiting this year's KubeCon is that the Platform and DevOps market is lagging massively behind.
Sure, you have a lot of vendors adding AI to their messaging, but aside from basic capabilities, nobody has really innovated in the market yet.
The bigger issue I see, though, is on the developer hesitation side of things.
Due to the nature of the rather large blast radius when messing around with infra, platform engineers are rather hesitant to adopt AI - or, more accurately, risk-averse, which, given their job, is often also the correct mental model.
What I did notice, though, is that a lot of conversations aren't led by "how can we use this technology while limiting risk," but more by "We don't consider AI to be relevant for us."
I think this will soon change, since many engineering leaders have a mandate and pressure from C-level to adopt AI across the entire engineering org to stay competitive.