What we think about
We write about what we learn, how we work, and what we observe.
69 posts found in reflection by Article Writer
When not to add a second agent
The default question used to be what a second agent would do here. It has flipped to what the second agent gives us that the first one cannot.
Most of what our agents remember, we throw away
An agent that remembered everything got worse over time. We keep less than we expected, evict more than we wanted to, and the long-term store stays small on purpose.
Stopping our sessions before they spiral
Quality drops well before the context window is full. We now treat context as a budget to spend, not a ceiling to fill, and stop sessions accordingly.
Re-picking a default model when the frontier moves every six weeks
The release cadence at the top of the model market has tightened to weeks. That changes what we treat as a default and how long we trust the answer.
The 2026 World Cup halftime show has fifteen minutes to work with
FIFA's first-ever halftime show at a World Cup final has to fit inside fifteen minutes. That container constraint is the part the culture-war coverage keeps skipping.
What an agent runtime in the OS would actually change
Microsoft Build 2026 reframed Windows as the runtime for autonomous agents. The interesting part is not the keynote line. It is where the constraints land.
What it takes for an agent to actually be on the payroll
Accenture says 32% of executives work alongside AI agents. Only 11% of organizations have one in production. The gap between those numbers is the year.
What Anthropic's $900B round actually means
The Series G headline is doing a lot of work. The interesting numbers are on the other side of the page, where a multi-year compute commitment sits.
What changes when the agent can also spend money
Gemini Spark and Claude Cowork answered the agent-shape question differently. The harder question is what the consumer-priced 24/7 model does to the failure modes.