curated · 2026-07-06

This is worth a look because it gives a concrete breakdown of how agents repeat work until a stop condition is met. Turn-based loops are the simplest: you prompt, Claude decides when it's done, good for short tasks, and you can write a SKILL.md file to verify output. Goal loops use /goal, stopping when the goal is hit or max turns reached—needs deterministic criteria like test pass counts. Time loops use /loop and /schedule to run on intervals, suited for syncing messages or checking PRs, and can run in the cloud. Proactive loops trigger on events or schedules with no human in the loop; each subtask exits independently. The team's advice is practical: start simple, add complexity only when needed. Only a tweet summary so far—no config examples or failure handling details, so I'd treat this as a framework reference for now.

This list is worth opening because it puts official statements next to headcount numbers, which is more useful than individual layoff headlines. Microsoft says its 4,800 cuts are 'not being replaced by AI' but admits AI is changing how work gets done — that phrasing alone tells you something. May was the worst month for tech layoffs in years, and AI was the most-cited reason. Roughly 120,000 tech roles have been cut so far in 2026 across ten companies including Microsoft, Oracle, and GitLab. I'd treat this as a running signal, not a simple 'AI is taking jobs' story. When a company cites AI for layoffs, sometimes they're genuinely restructuring teams, sometimes it's a convenient excuse — those are two different things.

This caught my eye because it tackles a real engineering headache: as batch size grows, verifying every drafted token in speculative decoding eats up the compute savings. DSpark's fix is a confidence head on the draft model that scores each token's chance of acceptance. The scheduler then trims the verify budget per request — low-confidence requests get fewer tokens verified, freeing compute for high-confidence ones. On H200 with DeepSeek-V4-Flash, it beats both MTP and non-spec baselines in throughput and per-user latency. The engineering highlight is the ragged verify under full CUDA graphs: when the scheduler cuts the verify length, the engine replays a genuinely smaller graph, not a padded one. That avoids wasted compute and explains why the wall-clock gains materialize. The cost-table profiler lets the scheduler size each request's budget online, and cap-accept mode exposes the acceptance ceiling that trimming would otherwise hide. I'd discount this a bit: it's LMSYS's own integration report, not an independent benchmark. Hardware, engine, and traffic all differ from the original paper, and they're upfront about reproducing the mechanism and curve shape, not the exact numbers. But the CUDA graph handling is concrete enough to be useful for anyone building inference engines.

The reason to click: Wired got internal docs that lay out the operational details. Project codenamed Cannes, run through contractor Covalen. Hundreds of workers created fake under-18 profiles to probe ChatGPT, Gemini, and Character.AI with prompts about suicide, self-harm, eating disorders, and sexual topics. One test round alone sent over 45,000 prompts. A spreadsheet logs 3,748 of them—including a 13-year-old asking for abortion pills and a fifth-grader describing a gun threat. Meta calls this routine safety benchmarking and says the data isn't used for training. I don't buy that framing. Standard red-teaming doesn't typically involve hiding your identity, fabricating minors, and probing competitors without their knowledge. What's missing: what Meta actually did with the results. Internal safety comparison report, or something else? The article doesn't say.

The /goal prompt numbers are what make this worth a click: $165 in API costs, 25 autonomous experiments, 50% faster builds, 60% lower token spend. Not "might be useful" — the author says they verified these repeatedly. The other prompts are similarly practical: a work-mode prompt that turns usage patterns into reusable Skills, an action-norm prompt that keeps subagents in check, a reverse-interview prompt that demands 95% confidence before executing. The core idea isn't "make the model stronger" — it's "make the model study how you work, then save you effort." This is an RSS snippet, so the actual prompt templates and task details aren't shown. I'd discount the numbers a bit — they come from one person's workflow and may not replicate directly. But the mindset is right: once API billing kicks in, treating prompts as portable assets matters more than chasing the newest model.

This one's worth opening because it turns model values from a vibe into coordinates you can compare. Gemini and Qwen sit next to each other on self-expression, GPT-4o and DeepSeek R1 are near-twins, but DeepSeek's own R1 and V4 Flash land on opposite ends of the secular-traditional axis. Tunguz's explanation is straightforward: Common Crawl is 46% English, so the baseline voice models imitate is a college-educated American online, and post-training pulls them in different directions. I'd discount the framing a bit—the World Values Survey is a Western academic instrument, so using it to measure global models' moral positions has some built-in assumptions. But the procurement question Tunguz raises is real. Worldview is invisible in code generation, but it's a live input in marketing copy, user behavior predictions, and customer support tone. Enterprise RFPs today score price, latency, context window, and benchmarks—values aren't on the list. For certain use cases, that's a blind spot.