Come To Think of It...

AI-generated apps have had an awkward little secret: they are pretty good at producing disposable interfaces, but the moment you want one to remember anything, the infrastructure starts looking like a junk drawer. Cloudflare's new Durable Object Facets are interesting because they attack exactly that problem. Dynamic Workers already let developers run generated code inside lightweight isolates instead of heavier container-style setups, which is why Cloudflare keeps stressing the speed and memory advantage. The new piece is persistence. A platform can now let AI-written code run as a facet inside a supervised Durable Object, with its own SQLite-backed storage attached locally to that object. In plain English, each tiny generated app can get a small brain and a memory without the platform owner handing over the keys to a giant database buffet. That detail matters more than the demo-friendly phrase "give each app its own database" suggests. The clever part is not just storag...

My working theory about AI agents is that most of the industry keeps trying to solve a software design problem by shoving more tokens at it. Bigger context windows are useful, sure, but they are not magic. Past a certain point, they become the digital equivalent of stuffing every receipt, sticky note, and half-baked thought into one backpack and then acting surprised when you can’t find your keys. That is why Cloudflare’s new Agent Memory announcement caught my attention. The interesting part is not the usual “agents are the future” throat-clearing. It is the much more practical claim: long-running agents need a managed way to remember what matters, forget what does not, and retrieve useful context without dragging their whole life story into every prompt. Cloudflare is pitching this as a private beta service that ingests conversations, stores memories in profiles, and lets an agent explicitly remember, recall, list, or forget information. In plain English, it is trying to turn memory...

One of the more interesting signals this week is not a shiny new model, but a quieter infrastructure move: Cloudflare is pushing the idea that websites now need to be readable not just by humans and search engines, but by AI agents. Its new Agent Readiness score is basically a report card for whether a site exposes the right clues for machine-driven visitors—things like robots preferences, markdown responses, authentication guidance, and emerging standards for machine-readable access. Cloudflare’s own numbers are the useful part here: across 200,000 popular domains, only 4% had declared AI usage preferences via Content Signals, about 3.9% supported markdown negotiation, and some newer standards barely registered at all. That is a polite way of saying the so-called agentic web is still mostly held together with wishful thinking, vibes, and whatever random HTML a bot feels like chewing on. What makes this worth watching is the practical follow-through. Cloudflare also rolled out Redirec...

One of the more interesting tells in this week’s AI news cycle is that the flashy part is no longer the model demo. The real fight is moving down a layer, into execution, persistence, browsers, checkpoints, and all the boring-sounding machinery that suddenly becomes very un-boring the moment you try to ship an agent that has to survive longer than a coffee break. OpenAI says its updated Agents SDK now adds a model-native harness, configurable memory, MCP support, shell and file-edit tooling, plus native sandbox execution with checkpointing and rehydration across providers. On the same day, Cloudflare rolled out Project Think, which leans hard into long-running agents with durable execution, sub-agents, persistent sessions, and sandboxed code execution, while separately expanding the control plane behind Workflows to handle much higher concurrency and creation rates. If you squint a little, the industry is rediscovering a fairly old lesson: once software has to act in the world instead ...

AI-generated apps have had an awkward little secret: they are pretty good at producing disposable interfaces, but the moment you want one to remember anything, the infrastructure starts looking like a junk drawer. Cloudflare's new Durable Object Facets are interesting because they attack exactly that problem. Dynamic Workers already let developers run generated code inside lightweight isolates instead of heavier container-style setups, which is why Cloudflare keeps stressing the speed and memory advantage. The new piece is persistence. A platform can now let AI-written code run as a facet inside a supervised Durable Object, with its own SQLite-backed storage attached locally to that object. In plain English, each tiny generated app can get a small brain and a memory without the platform owner handing over the keys to a giant database buffet. That detail matters more than the demo-friendly phrase "give each app its own database" suggests. The clever part is not just storag...