How Sessions Work
Automatic Creation
Sessions are created automatically when:- WebSocket connects - New session per connection
- First message arrives - If session doesn’t exist, create one
Session ID
Each session has a unique identifier:- Generated by client - Client generates session ID
- Server confirms - Server may provide its own session ID
- Used for all messages - All messages in a conversation use same session ID
Session State
Conversation History
Each session maintains its own conversation history:User Metadata
Store user information in sessions:Session Lifecycle
Creation
Usage
Cleanup
Sessions are cleaned up when:- WebSocket disconnects - Connection closed
- Session expires - After inactivity timeout
- Server restarts - All sessions cleared
Best Practices
Session IDs
- Generate on client - Client generates session ID
- Reuse for continuity - Same session ID = same conversation
- New session for new topic - Start new session for new conversation
Session State
- Store user preferences - Use session metadata
- Maintain context - Conversation history is automatic
- Track activity - Last activity is tracked automatically
Next Steps
- Conversation History → - Understand history
- Multi-turn Conversations → - Learn about multi-turn
- Context → - Understand conversation context

