An unprecedented day in my history with PHP. Some bumps along the way, but really proud of the @laravel team for working through the night ensuring all of our products and customers had patches available to them and, when possible, applied automatically. Given the advancement of agents, it's quite possible this won't be the last time this happens, and it's likely PHP won't be the only language that goes through this. We built some solid muscle today to do even better next time. Onward. 🫡

Protip for AI coding: If the agent does smth wrong, don't just fix or reprompt. Think about how to ensure that it wouldn't repeat IN THE FUTURE. - One more verification layer or tool - One more automated test - One more instruction in skills/rules/prompts Improve the SYSTEM.

THIS IS F*CKING BRILLIANT. Anthropic’s docs describe one of the smartest ways to run Opus three models work on one task and each does only the part it’s cheapest at. start Claude Code like this: claude -> model sonnet -> advisor opus you stop paying Opus prices for work that doesn’t need Opus > Sonnet runs the session and edits the code > Haiku 5.5 searches the repo and docs, at up to 40x less per token than Opus 5.5 > Opus waits as the advisor and reads the whole session, tool calls included Claude usually calls Opus at three points: > before it locks a plan > when the same error comes back > right before it says it’s done Sonnet drives. Haiku scouts. Opus signs off and if you go one step lower, most of an agent’s day is tiny choices like picking a file or a tool, or deciding whether to retry. Jev takes those first, so Sonnet and Opus only see the moments that are really open the whole setup Sonnet runs the main session Explore on Haiku 5.5 searches and pulls docs, read-only Opus on call as the advisor give Claude Code this setup and the prompt below ↓ “Set up my Claude Code exactly like this: Main model Sonnet, advisor Opus, saved as advisorModel in my settings. One read-only subagent named exactly Explore, on claude-haiku-5-5, to replace the built-in one. One line in CLAUDE.md: ask the advisor before locking a plan, after the same error twice, and before calling a task done, not more often. Check what could turn the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY) and only report it. Show every change as a diff first. Don’t edit anything until I say go.” code.claude.com/docs/en/advi… before you turn it on: every advisor call re-reads the whole transcript with no cache. on a 200k session that’s about $0.80 in input, against $0.04 for a normal request. keep it to a few calls the built-in Explore agent runs on your main model unless a subagent is named exactly Explore. any other name does nothing turning the advisor on or off keeps your prompt cache. switching models rebuilds it it needs the Anthropic API, and it stays off if telemetry is disabled bookmark it before your next long session

One command to upgrade every prompt you've written for Opus 5.5: /claude-api prompt-audit Run it in Claude Code. It audits your skills, CLAUDE.md and prompts, cuts what's holding the model back, and rewrites the rest with the official Opus 5.5 guide. Took 5 minutes.

I think I just cooked something 🔥 jev(): a PostgreSQL extension that searches your whole database in natural language. No index, no embeddings, just one function. WHERE jev(people, 'could work from home') or WHERE jev(people, 'name sounds european') 129 rows judged in ~1s for $0.0009. Second run: 6ms from cache.