Sessions
Group and visualize multi-step LLM interactions. Track request flows across multiple traces and gain insights into complex AI workflows by adding only 2 simple headers.
Introduction
Sessions in Helicone provide a powerful way to organize and analyze complex interactions within your LLM applications. By grouping related requests together, sessions offer a holistic view of user journeys, multi-step processes, or extended AI workflows. This feature is particularly valuable for applications that involve multiple back-and-forth exchanges or those that build upon previous context.
Example: A Session creating an outline for a book about space
Why Sessions
Sessions, identified by a helicone-session-id
header, allow you to:
- Reconstruct the flow of a conversation or a multi-stage task
- Analyze performance and outcomes across entire interaction sequences
- Identify bottlenecks or areas for improvement in your AI workflows
- Gain deeper insights into user behavior and application patterns
Quick Start
Simply add a Helicone-Session-Id
header to your request to start tracking your sessions and traces.
To represent parent and child traces we take advantange of a simple path syntax in the Helicone-Session-Path
header. For example, if you have a parent trace parent
and a child trace child
, you can represent this as /parent/child
.
Depending on your library you will need to add the following three headers to your request:
Helicone-Session-Id
- The session id you want to trackHelicone-Session-Path
- The path of the sessionHelicone-Session-Name
- The name of the session
Here is an example is ts: see other languages
Node JS Example
Javascript Session example shown above