Choose what happens to idle sessions
Pause idle sessions to resume them later, or end them, and set how long to wait.
An agent's sessions go idle when nothing happens for the inactivity limit. You decide whether Blaise keeps the session's environment for the next message or ends the session.
In the dashboard
- Open Settings → Agents and choose Edit on the agent. You need to be an admin or owner of the workspace.
- Under When a session goes idle, choose:
- Pause it and resume on the next message: the environment is kept. This is the default.
- End it: the session is completed and its environment torn down at once.
- With Pause, choose how long to keep a paused session for. After that long without a message, the session is completed and torn down.
- Choose Save Changes.
The change applies to sessions from then on. A session that is already paused expires at the time it was given when it paused.
When to pause, and when to end
Pause when a conversation continues over hours or days and setting up is slow: a checkout with installed dependencies, a container, a cloud sandbox. The next message continues where the last stopped.
End when the work is a single task, when you pay for what a plug leaves running, or when a plug cannot resume. A runner with a plug that cannot resume (see make a plug resumable) does not start while the policy is Pause, and tells you which plug.
What the runner does when the policy changes
blaise-agent listen reads the policy when it starts, so a change that makes a runner's plugs
unsuitable is noticed at the next restart. A running runner cannot be caught out: every run tells
Blaise whether its plugs can resume, and Blaise ends a session whose plugs cannot, whatever the
policy says.
Through the API
The agents.update procedure of the SDK takes idlePolicy (pause or end) and
pausedLifetimeMs. The server caps the lifetime at its maximum (SESSION_MAX_PAUSED_LIFETIME_MS, 7
days by default).