--- date: 2026-08-28 title: "Responsive Timeline" description: "The trace Timeline now fits any trace on one screen — twelve spans or twelve hundred — and zooms like a map. Colour carries the observation type, names come back when there is room." author: Nikita Kabardin ogVideo: https://static.langfuse.com/changelog-videos/2026-08-28-dense-timeline.mp4 --- > **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 current documentation (https://langfuse.com/docs) and the API/SDK reference (https://api.reference.langfuse.com). Agent traces only get bigger. A run that was twelve spans last year is six hundred today — a fan-out of tool calls, a queue of embeddings, four retries, and a twenty-minute wait on a human somewhere in the middle. The old Timeline answered that by scrolling: you paged through a trace hoping to recognise the part that mattered. The new **Responsive Timeline** fits the whole trace into the space you have, on both axes. You see the shape of the run first, then zoom into the part that matters like a map. ## Geography of your time Zoomed out, a trace reads as terrain: rows shrink to a single line and colour carries the observation type, so a fan-out, a wall of embeddings and one long generation are recognisable before you read a label. - **Scroll to pan, pinch or ⌘-scroll to zoom** — both axes together, time and rows. - **Double-click any observation** to fly to it at a readable size. Names, the tree gutter and the duration labels come back on the way in. - **Drag to select a time range**, or hit **Fit** to go back to the whole trace. - **Hover the left edge** to peek at names without moving a single bar. ## It fits your screen too The same view runs in the trace panel, in the side peek, and on a phone — the layout adapts to the box it is given rather than assuming a desktop. A 320-pixel peek and a 4K pane are the same renderer at different densities. ## Feedback Traces will keep growing, and this view is built to keep up with whatever 2026 ships next. Tell us where it stops keeping up — what you look for in a big trace, and what you still cannot find — in our [feedback discussion](https://github.com/orgs/langfuse/discussions). --- ## 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-08-28-responsive-timeline.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 .