☕️ Cursor launches its own model router

• Cursor Router looks at each coding request—how hard it is, what it's for, and the surrounding code—then sends it to whichever model fits best, so developers no longer pay frontier prices for simple work.
• Instead of picking one model by hand in Cursor's settings and sticking with it, developers get automatic routing plus three modes that shift the balance between speed, cost, and raw power for each task.
• Router draws on Cursor's Composer and Grok 4.5 models plus outside providers, saved early customers 30-50% versus Opus 4.8, and ships to Teams and Enterprise only, matching similar routers from Ramp and Meta's Switchboard.

• FreeBSD froze its ports tree for over 48 hours after a 150MB binary landed in the repository, prompting core@ to halt all commits while they roll back the offending change and clean up the history.
• The commit added the full github-copilot-cli Linux binary through its FreeBSD port, which normally just uses Linuxulator to run the unmodified binary rather than porting the closed-source tool itself.
• The blob broke the GitHub mirror by exceeding the 100MB filesize limit and introduced questionable licensing into the tree, though ports wasn't compromised and users' systems remain unaffected.

• Cloudflare launched Cache Response Rules, a new rule type that runs after the origin replies but before content is written to cache, letting you fix caching problems that only surface in the origin's response.
• The rules support three actions: stripping headers like Set-Cookie, ETag, and Last-Modified that break caching, managing cache tags for purge-by-tag, and modifying Cache-Control directives, all without any origin code changes.
• Setting `cloudflare_only: true` on a directive adjusts how Cloudflare caches while leaving the downstream browser Cache-Control value untouched, and when a Cache Rule and Cache Response Rule conflict, the response rule wins.

• Dependabot now enforces a three-day cooldown by default before opening pull requests for version updates, giving maintainers, researchers, and scanners time to catch a malicious release before it reaches your build pipeline.
• The delay applies only to version bumps, not security updates, which still open immediately since holding back a fix for a publicly disclosed vulnerability would leave you exposed longer than necessary.
• Three days was chosen because reviewed supply chain attacks on packages like chalk, axios, and Solana web3.js were caught within hours, and you can override the window using the cooldown option in dependabot.yml.

• Jotai v2.20.0 has shipped, reworking the internal store building blocks that library authors depend on to boost performance in high-throughput scenarios while leaving the everyday application API completely unchanged for typical React developers.
• The update fixes a reported performance regression by dropping the WeakMap approach used to make building blocks flexible, instead passing everything as parameters, alongside type narrowing for hooks and lazy handling of new atom state.
• The breaking change affects downstream tooling, prompting jotai-devtools v0.14.0 to add support and drop older versions, while patches v2.20.1 and v2.20.2 cover edge cases ahead of a planned v3 that redesigns these internals and drops CommonJS builds.

📚 Tutorials & Advice

🔗 Other News & Articles

• Outperforming Fable 5 at half the price: meet model synthesis, a new server-side tool on DigitalOcean Inference Engine LINK

• The Pulse: New trend - concern about massive increase in code review load LINK

• Geekbench 7 will push your computer or phone even harder for better benchmarking LINK

• Meta Develops Switchboard to Route Simpler AI Tasks to Cheaper Models LINK

• Runway launches AI model router as generative media gets crowded LINK

• Poolside's Laguna S 2.1 is a small open-weight coding model that punches well above its size LINK

• Article: Multi-Agent AI for Production Security Operations: An A2A and MCP Architecture in a 5G Core LINK

📄 Papers & Resources

🧰 Latest Tools

💬 How did you find today's edition?

We read every reply — just reply to this email and let us know how we can improve!