CS2680 Modern AI Systems: Agents and System Optimizations
News from the watchlist

This page collects what the sources on blogs to watch have published recently and groups them by subject rather than by publisher. It is rebuilt every hour, so a post usually appears here within an hour of going up. Nothing on this page is required reading.

Grouping by subject is the point. A reader gives you 45 separate streams and leaves you to notice that four companies wrote about the same scheduling problem this week; this page puts those four posts under one heading. Topics come from the filter terms already listed on the blogs-to-watch page, so the vocabulary is the course's.

How a post is filed. Each post is scored by keyword against every topic, using its title and its summary, and it is filed under the topic it scores highest against. A term that names a subject on its own counts for more than one that merely co-occurs with it, and a match in the title counts for three times a match in the summary. Any second topic a post also matches is shown as a label beside it. The method is keyword matching rather than a model, which makes it predictable, cheap, and occasionally wrong.

You are reading one topic, agent harnesses and orchestration, over the last 120 days. Show every topic.

Agents

Agent harnesses and orchestration

How an agent loop is built, driven, and kept on task.

Sources and the last run

The index covers 45 sources from the watchlist. 37 publish a feed and are read from it; the other 8 publish none, so their index pages are scraped and each new post's own page supplies the title and date its card omits.

Last run finished 28 Aug 2026 at 00:08 UTC. The index holds 710 posts, keeps them for 120 days, and shows 125 posts on this page.

2 sources failed on the last run. Netflix TechBlog (HTTP 429); Replit (HTTP 403)

The last run read 833 posts across every source and added nothing new.

4 sources on the watchlist are not aggregated here, so check them by hand.

  • Intel Developer. The Lithium community platform answers 403 to every automated request, feed paths included.
  • Uber Engineering. The index renders client-side, there is no feed, and the only sitemap is the whole-site marketing index.
  • LinkedIn Engineering. The index renders client-side and there is no feed.
  • Artificial Analysis. A standing benchmark dashboard rather than a blog, so it publishes no post stream.

A date shown as "first seen" is not a publication date. Some sources publish no date at all, so the page records when the post entered the index instead of guessing.