---
date: 2026-10-13
title: Redesigned session view
description: Read user and assistant messages across traces in one continuous conversation, with a sidebar to navigate messages, traces, and tool usage.
author: Ben
ogImage: /images/changelog/2026-10-12-session-view.jpg
---

> **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).

The redesigned session view brings user and assistant messages across traces into **one continuous conversation**, with a sidebar for navigating messages, traces, and tool usage.

- **Debug conversations:** Follow the user's requests and the assistant's responses to find where an interaction went off track, then jump to the relevant trace.
- **Inspect tool usage:** Use the sidebar to see which tools an agent called and where those calls fit into the conversation.
- **Evaluate responses in context:** Review each response alongside earlier messages to assess whether the assistant understood the user and built on previous turns.

## Further improvements

The sessions table now includes filters for tool usage, making it easier to find conversations to investigate:

- **Tool Names (Available):** Find sessions where a particular tool was available to the model.
- **Tool Names (Called):** Find sessions where a particular tool was actually called.
- **Tool Calls:** Filter by the number of tool calls, for example to find sessions with no calls or unusually frequent tool usage.

## Get started

Open **Sessions** in your project and select a session to explore its conversation. If you are not grouping traces into sessions yet, [set up a shared `sessionId`](/docs/observability/features/sessions#set-up-sessions) for observations belonging to the same interaction.

<!-- agent-instructions -->

---

## 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-10-13-redesigned-session-view.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**: <https://langfuse.com/llms.txt>, 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 <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.