faint-gold-41196
09/19/2025, 12:51 PMtall-airline-16756
09/19/2025, 12:51 PMtall-airline-16756
09/19/2025, 12:52 PMsession.history along with add_shutdown_callback to save the entire conversation history to a local file once the session ends. This is usually the best way to handle server-side storage.
• Real-Time Logging: Another option is to listen for events like user_input_transcribed to capture user inputs as they happen. Just be sure to check for final transcriptions before saving to keep things accurate.
• Frontend Storage: If you’re looking to store data on the client side, browser-based options like localStorage or IndexedDB can work well. Keep in mind, though, that this isn’t part of the official LiveKit SDK and is better suited for demo or simpler applications.
If you'd like, I’d be more than happy to walk you through detailed steps for any of these methods or help tailor a solution to your specific needs. Just let me know!
Sources: tools/server/public_legacy/index-new.html | Sending text | LiveKit Docs | Session recording and transcripts | LiveKit Docs | Recording agent sessions | LiveKit Docs | pipeline-stt/transcriber.py