@ThePhilliesShow@RAJr_20@JimSalisbury215 Does anyone else think that the Phillies players are sandbagging to ultimately get rid of Dave or Rob? How does a 96 win team for multiple years just get bad all of a sudden?
Does anyone else think that the Phillies players are sandbagging to ultimately get rid of Dave or Rob? How does a 96 win team for multiple years just get bad all of a sudden? #Phillies#ringthebell#MLB
Well, that’s the end of an era: I’ve just canceled my ChatGPT subscription.
The reason is nothing extraordinary. It feels strange because Chat used to be a significant part of my life.
I can’t recall the last time I used ChatGPT, and it has been replaced by better AI services, such as Claude.
My OpenAI API will still be utilized within projects, and I might reconsider if something remarkable emerges.
Google and Microsoft just co-authored the spec that turns every website into an API for AI agents. The second-order effects here are massive.
Right now, browser agents work by taking screenshots, parsing the DOM, and guessing which buttons to click. It works about as well as you’d expect. Fragile, expensive, slow. WebMCP replaces all of that with a single browser API: navigator.modelContext. Websites register structured tools directly in client-side JavaScript. The agent reads a menu of available actions, calls them, gets structured data back. No scraping. No backend MCP server in Python or Node. The tools run inside the browser tab and share the user’s existing auth session.
Early benchmarks show ~67% reduction in computational overhead compared to visual agent-browser interactions. Task accuracy around 98%.
The second-order effect is where this gets wild. Today, when a browser agent visits two competing airline sites, it’s guessing at both interfaces equally. Once WebMCP adoption spreads, the site that exposes structured tools gives the agent a clean, reliable path to complete the task. The site that doesn’t forces the agent to fumble through the UI. Agents will prefer the cheaper path. Every time.
This means “Agent Experience Optimization” becomes a real discipline. Tool naming, schema design, description quality. Sound familiar? It’s the same shift that happened when meta descriptions and structured data became optimization surfaces for search engines. Except this time, the traffic source isn’t Google’s crawler. It’s every AI agent on the internet.
Bots already make up 51% of web traffic. Google just gave them a front door.
Claude Opus 4.6 is here!
Opus 4.6 is state-of-the-art on several evaluations including agentic coding, multi-discipline reasoning, knowledge work, and agentic search.
Available today wherever you get your Claude.
Will share some thoughts and best practices throughout the day.
Claude Sonnet 5: The “Fennec” Leaks
- Fennec Codename: Leaked internal codename for Claude Sonnet 5, reportedly one full generation ahead of Gemini’s “Snow Bunny.”
- Imminent Release: A Vertex AI error log lists claude-sonnet-5@20260203, pointing to a February 3, 2026 release window.
- Aggressive Pricing: Rumored to be 50% cheaper than Claude Opus 4.5 while outperforming it across metrics.
- Massive Context: Retains the 1M token context window, but runs significantly faster.
- TPU Acceleration: Allegedly trained/optimized on Google TPUs, enabling higher throughput and lower latency.
- Claude Code Evolution: Can spawn specialized sub-agents (backend, QA, researcher) that work in parallel from the terminal.
- “Dev Team” Mode: Agents run autonomously in the background you give a brief, they build the full feature like human teammates.
- Benchmarking Beast: Insider leaks claim it surpasses 80.9% on SWE-Bench, effectively outscoring current coding models.
- Vertex Confirmation: The 404 on the specific Sonnet 5 ID suggests the model already exists in Google’s infrastructure, awaiting activation.
(Unverified leaks; treat timelines, pricing, and benchmarks with caution.)
@haider1 If we are truly months away from end-to-end software engineering models, the fundamental nature of 'seniority' in tech shifts from being the one who writes the most code to being the one with the sophisticated architectural taste to audit and orchestrate the AI's output.
@ashpreetbedi Transitioning from reactive chatbots to agents that possess a self-evolving memory is the defining shift of this era, but as they begin to learn from every interaction, how do we ensure they are inheriting our best logic rather than just replicating our most efficient shortcuts?
Since the Ralph Wiggum loop essentially treats debugging as a high-velocity evolution, do you think the 2% who master it are gaining their edge from the sheer speed of failure or from the creative serendipity that only happens when you stop trying to be 'perfect' and start being prolific?