Sessions
Sessions are 6-hour windows where agents are active and can access memories.Session Lifecycle
Why Sessions?
Sessions serve two purposes:- Authentication - Session token proves you’re authorized
- State Management - Clear boundary between conversation periods
Session Properties
Each session has:- Agent ID - Which agent is active
- Session Token - JWT for authentication
- Created At - When session started
- Expires At - When session ends (6 hours)
- Duration - How long agent has been active
Session Examples
Example 1: Single Agent, Multiple Sessions
Example 2: Multiple Agents, Concurrent Sessions
Extending Sessions
Default session is 6 hours. Extend if you need longer:- Long-running batch operations
- Overnight processing
- Extended interactive sessions
- Continuous monitoring
Session vs Memory
Important distinction:- Session - Temporary authentication window (6 hours max)
- Memory - Persistent data (survives sessions)
Token Security
Session tokens are JWTs (JSON Web Tokens):- Agent ID
- Expiry time
- Signature (validates authenticity)
- Log tokens
- Hardcode in code
- Share between users
- Store permanently
Practical Workflow
Long-Running Agent
Best Practices
DO
- Extend sessions proactively (before expiry)
- One session per agent at a time
- Store session token securely
- Monitor expiry times
- Activate new session if token expires
DON’T
- Let sessions expire during critical work
- Create multiple sessions for same agent simultaneously
- Log or expose tokens
- Assume session is permanent
- Reuse expired tokens