In agent-graph-engineering, a reference-implementation repository that builds LLM agent systems as LangGraph graphs and adds types to agents with Pydantic AI, the commit 6b195cce of October 31, 2026 touched the tracing side. It removed the conversation history (messages_json) from the graph.state dump that was attached to every node, and instead left a placeholder string stating that the content is elsewhere.
The scope of this repository is broader than a single agent loop. The repository description says it declares the flow as a graph, defines agents as typed structures, generates WebSocket and REST contracts, subjects irreversible actions to human approval, and packages tracing and evaluation together. This commit touched only the tracing slot among them. The commit message pointed out that the state dump repeated the same content nine times per node within a single run, and that the conversation history accounted for roughly 70 percent of it. Since the content actually sent is already retained in the model call records nested under the node, the history now keeps only its name and points elsewhere. The same message stated that, on a script run basis, the number of characters in the state attributes fell from 15,997 to 6,868.
The implementation was confined to agent/assistant/tracing/nodes.py and two test files. When _as_json converts the state into a JSON string, it substitutes only the messages_json value with <on the model call spans>, leaving the remaining fields intact without fine-grained trimming. If the conversation history is an empty string, it is left empty, so that it is not misread as saying the content is elsewhere when there is none. Three new tests lock in this behavior.
That said, the figure of 15,997 characters down to 6,868 characters is based on the script run stated in the message of commit 6b195cce. It only said the gap would be wider in actual conversations, and there are no other measurements. The conversation content cannot be seen from the state attributes alone, so one has to move on to the nested model call records to check the content. The change ended narrowly, with 45 added lines and 2 deleted lines, and as of the October 31, 2026 commit 6b195cce no release version indication was given. It is an improvement that can be applied right away in environments that need to shrink the state size left in tracing, but pipelines that presuppose keeping the conversation history as a state value need to examine alternatives separately.