Session Management
A session is one user's chat with an agent. Strongly tracks every session so you can see who's chatting right now, end a session that's gone wrong, and enforce limits like max concurrent sessions per user.
The Sessions tab on each agent's page shows them live -- the table updates as state changes, no refresh needed.
Session states
| State | Meaning |
|---|---|
| Live | Active conversation. |
| Idle | No activity recently -- the agent is still available; the user just hasn't said anything. |
| Paused | You explicitly paused the session. Resume it any time. |
| Ended | Closed. Either the user / admin ended it, or it hit idle / max-duration limits. Terminal. |
Sessions move from live to idle to ended automatically based on your session policy.
Session policy
Set on the wizard's Session step when building an agent and editable later in Agent Settings → Session Policy. Five settings:
| Setting | What it does | Default |
|---|---|---|
| Idle timeout | After this much inactivity a live session goes idle, then ends after the same period. | 30 minutes |
| Max duration | Hard cap on total session length. | 4 hours |
| Max concurrent sessions per user | How many active sessions one user can have with this agent. Blank means unlimited; excess attempts are rejected. | Unlimited |
| Auto-archive after | Days after a session ends before its row moves to the archive. 0 keeps rows indefinitely. | 30 |
| Allow per-session model override | When on, an admin (or a user with permission) can use a different model for a single session without changing the agent's default. | Off |
Runtime
The Agent Settings → Session Policy tab also holds the agent's runtime mode:
- Always-on -- one replica stays live.
- On-demand -- the agent sleeps when idle and wakes on the next message. You pick the sleep-after-idle period in minutes.
Actions on a session
From the Sessions tab, for each non-ended row:
- End -- close the session. The chat history stays on the thread; only the session lifecycle row closes.
- Pause / Resume -- temporarily put a session on hold.
- Transfer -- hand a session to another agent. The source session ends; the target agent picks up on the user's next turn.
When to end a session manually
- Compliance -- pull a misbehaving user's active session.
- Cost -- long-running summary chains pile up; ending and starting a new session gives the agent a fresh start.
- User confusion -- sometimes the cleanest path is a clean slate.
Permissions
- The user owning the session can end / pause / resume / transfer their own session.
- The agent owner sees and controls every user's session.
- Admins see and control every session.
See also
- Agent Builder wizard
- Agent Settings → Session Policy tab