Skip to content
34Five.ai / Documentation
Open Studio ↗
Documentation

Find an answer

Browse popular starting points

DocumentationAuras™ and Vibes
Auras™ and Vibes

Session History

Find previous sessions and work with their available records.

Studio / MCP v1Reviewed 2026-10-24
Documentation previewDraft content · Staging instructions · Not approved for production
On this pageWhat a record containsFind the right sessionReading through MCPData leaves Studio when read

What a record contains #

A Session History record can include a title, participants, timing, a summary, a report, and transcript content. A missing report or transcript is not proof that every processing step has completed.

Find the right session #

Search in the intended workspace and narrow by the Aura™, participant, time, or subject. Confirm the result before relying on its content.

Reading through MCP #

An external agent first calls 34five_whoami, then uses 34five_list_sessions to find a record. It calls 34five_get_session for the summary, report, participants, and a bounded transcript window. Curation interviews are excluded from these tools.

See MCP Tool Reference for filters, pagination, and transcript limits.

Data leaves Studio when read #

If an external agent reads a session, that content enters the agent provider's context. Choose the client and requested data with that in mind. See Security and Data Handling.

34Five DocumentationPrivacyContent 2b5e203ea2