Skip to content
English - United States
  • There are no suggestions because the search field is empty.

What are Sessions?

Sessions are continuous interaction sequences between a user and an AI model or agent. Sessions encompass:

  • Multiple related prompts and responses in a conversation thread
  • Events and participant interactions across an agentic workflow 

Learn more about Events here.

How Sessions are Created

Sessions are automatically grouped using two methods:

  • The same user sends another prompt within 45 seconds of their previous prompt 
  • Prompts sent via the API that include the same Session ID

The first or header input in a Session must originate from either a User or Agent Participant. If the first prompt comes from another Participant type, the Session will have no header. Learn more about Participants here

How to View Sessions

To view your Sessions, navigate to the Monitoring page and tap on the filters icon.

Screenshot 2025-07-25 at 10.03.59 AM

Tap into the Settings menu at the top right and ensure that the Session column is enabled.

Screenshot 2025-07-25 at 10.06.25 AM

To filter out "child" prompts and show only the first prompt in a Session, tap into the filters and mark to "Show only sessions." 

Screenshot 2025-07-25 at 9.25.51 AM

On the Monitoring page, single prompts are a Session of one and will show even when the setting to filter out child inputs is enabled. 

Now there is a Sessions column in the Monitoring view. Tap the Sessions icon to view the whole conversation.

Screenshot 2025-07-25 at 10.15.37 AM

Prompts are filtered to only those that are in a Single session. The threading on the left shows the hierarchy of inputs by time and the top input will always be the Session header. Increased threading depth beyond one child is a future feature. 

To navigate back to the regular Monitoring view, tap the back arrow next to the Bookmarks tab at the top. 

Screenshot 2025-07-25 at 10.18.55 AM

Sessions will "close" if 24 hours elapse between inputs. Any additional content sent with the same Session ID via the API will result in an error.