curated · 2026-08-12

This one's worth a look because it fixes a real friction point: browser side-panel sessions used to be siloed, so switching devices meant starting over. Now the side panel runs a full Claude Cowork session tied to your account, and you can pick up where you left off on desktop, web, or mobile. The example they give is practical: ask Claude to pull invoice data from multiple vendor portals into a spreadsheet, then switch to the desktop app to add local files or compare last month's budget. If you bounce between devices a lot, this saves real time. On safety, Anthropic added a pre-action check. In auto-approve mode, before anything like submitting a form or downloading a file, a separate review blocks steps that don't match your original request. They're upfront that prompt injection risk can't be fully eliminated, and recommend starting on trusted sites. Available now on Max and Team plans; Pro users get it in a few weeks. Enterprise is off by default, with domain-level admin controls. No support yet for other Chromium browsers or mobile.

This caught my eye because it offers a copy-pasteable fix for a real headache: what do you do when most of your contributors are AI? AutoGPT maintainer Reinier van der Leer put an AGENTS.md file in the repo to set rules for AI contributors, then added skill gating so only agents that pass linting and unit tests can submit code. Spam PRs dropped sharply. I'd discount this a bit because the post doesn't disclose how many human contributors got wrongly blocked. If the gate also filters out newcomers or non-native English speakers, it's not just spam reduction—it's a tradeoff. Also, AGENTS.md is a convention, not an enforced standard; it only works if the agent chooses to follow it. Still, that 60% figure is a signal. The noise source for open-source maintainers has shifted from clueless newcomers to batch-generated AI submissions. Putting rules in a file and using automated tests as a gate might become table stakes for popular projects.

The reason to click: Mustafa Suleyman himself announced Microsoft's first in-house reasoning model, MAI-Thinking-1, now live on Microsoft Foundry. But the post gives us nothing beyond 'built from scratch.' No parameter count, no benchmark scores, no pricing. Without comparisons, 'in-house reasoning model' is just a label. I'd discount this until we see numbers. The one concrete takeaway: Microsoft is officially in the reasoning-model race, and they're building their own rather than rebranding someone else's.

This is worth reading because Lambert isn't running a benchmark — he's stress-testing models against his own just-finished textbook, *Reinforcement Learning from Human Feedback*. Models handled LaTeX formatting, copyediting, and diagram generation fine. But when he asked them to write a full technical chapter, the output was confusing, poorly organized, and riddled with random conceptual errors. His take is blunt: models are superhuman at coding and math, but long-form nonfiction writing has stagnated. The bottleneck? Lambert points to a lack of good training data, and he notes inference-time compute scaling hasn't helped writing at all. I take this seriously because he's the author of the RLHF book, not an outsider complaining. The contradiction he flags is sharp: if models can't coherently organize established knowledge, how do we expect autonomous scientific breakthroughs? Anthropic published Riemann Hypothesis progress the same day, and Lambert clearly isn't buying it as evidence of breadth — that's a narrow task. The post doesn't cite benchmark scores, but Lambert's conclusion is measured: models will be the most powerful research assistants ever, but they're nowhere near producing revolutionary insights on their own.

OpenRouter ran Exa, Parallel, Perplexity, and native lab search engines across four benchmarks—BrowseComp, DeepSearchQA, WideSearch, HLE—with different models and search turn budgets, then published live leaderboards. The headline finding: search budget is the single biggest quality lever. On BrowseComp, Claude Opus 5 with Perplexity went from 35.8% at 1 turn to 89.0% at 25 turns, while cost only rose 2.5–7×. On easier tasks like HLE, extra turns barely moved the needle—GPT-5.6 Sol scored similarly at 1 and 25 turns but cost 3× more. The catch: when models can't find an answer, they burn through the full budget, making worst-case costs spike. The leaderboards update live; OpenRouter recommends testing against your own workload. I'd focus on the BrowseComp cost curves for hard fact-finding tasks—extra turns on easy benchmarks just waste money.