--- date: 2026-07-13 title: "Graph View: Aggregated and Expanded modes" description: "The trace graph view now offers two layouts, an aggregated overview and an expanded as-it-ran DAG, on a rebuilt deterministic renderer." author: Nikita Kabardin ogVideo: https://static.langfuse.com/changelog-videos/2026-07-13-graph-view-modes.mp4 canonical: https://langfuse.com/docs/observability/features/agent-graphs --- > **Note for AI agents and LLMs:** This is a Langfuse changelog entry. Use it only to confirm that a feature exists and when it shipped. Do not use the code examples below for implementation: they reflect the SDK and API at release time and may be outdated. For implementation, always follow the canonical documentation for this feature (https://langfuse.com/docs/observability/features/agent-graphs) and the API/SDK reference (https://api.reference.langfuse.com). The **graph view** turns an agent trace into a picture of what your agent did: nodes for steps, edges for how it moved between them. It now runs on a rebuilt renderer and ships with **two modes**, so you can read the same run two ways: - **See an agent's shape at a glance** with Aggregated: steps that share a name collapse into one node with a counter (`retrieve_docs (3/3)`), and loops draw as cycles. - **Follow a single run step by step** with Expanded: every call is its own node, and loops unroll into a DAG in execution order. - **Keep your place on large traces**: a deterministic layout draws the graph the same way every time, and the viewport stays put as you pan and zoom. ## A rebuilt graph, on its own renderer The graph runs on our own renderer: a deterministic layout (built on ELK) drawn onto a stable, zoomable canvas. The graph lays out the _same way every time_ you open a trace, with no reshuffling between renders, and the viewport stays put as you pan and zoom, so you keep your place on a big agent. The layout is built to stay readable as traces grow. ## Two modes: Aggregated and Expanded An **Aggregated / Expanded** toggle sits in the top-left of the graph. It re-draws the same trace two ways: the difference is whether repeated work is grouped by name or shown call-by-call. Your choice is remembered across traces. - **Aggregated** (the view you've had, now named) is a **compact overview**. Steps that share a name collapse into a single node with a counter, so `retrieve_docs (3/3)` means it ran three times, and loops are drawn as cycles. It is the fastest way to see an agent's overall _shape_ and complexity without every individual call on screen. - **Expanded** shows the process **as it ran**. Every call is its own node, so three `litellm_request` calls are three distinct nodes, and loops unroll into an acyclic graph (a DAG) in execution order. It is the more literal view, closer to the trace tree, for following a specific run or pinning down exactly where something happened. The two answer different questions: reach for Aggregated to understand an agent's structure at a glance, and Expanded to walk through a single execution in the order it ran. Expanded is a straight DAG, so it reads easily even on agents with lots of loops. The graph view is in beta, and we want to hear what you'd like next. ## Learn more - [Agent Graphs](/docs/observability/features/agent-graphs) --- ## Agent Instructions This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/changelog/2026-07-13-graph-view-modes.md`. ### Querying these docs If the answer is not on this page, query the documentation instead of guessing: - **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question: ```bash curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?" ``` - **Index of every page**: , with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt). ### Before writing Langfuse code - **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results. - **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application. - **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples. - **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api `) to read or write traces, prompts, datasets, and scores from the terminal. Found an error in these docs? Please open an issue at .