Drıftstack docs
Docs

Stop a running session (what is lost)

You might be here because: “how do I stop a session” · “Stop this session now? The browser closes immediately” · “will I lose my login if I stop” · “does closing the window end the session” · “session still running after I closed it” · “how to free up a session slot” · “end the session” · “kill session”

Short answer

Press Stop on the session’s card (Sessions in the sidebar, or the profile’s row). Stop only a session you started; if a teammate or a script started it, ask whoever did. The browser closes immediately and anything in progress on the page is lost — an unsent form, an unfinished checkout. What is kept: the profile’s cookies and logins, which are saved on a clean close. Stopping frees the session slot at once, so to free a slot, stop one you started (or ask whoever did).

Check first

  • Closing the session window is not the same as Stop; check Sessions in the sidebar.
  • Team member? Stopping a session on the team owner needs the admin role.

Likely causes and fixes

  1. Stopping from the app. The confirm reads “Stop this session now? The browser closes immediately and anything in progress is lost.”. Confirm to stop. The slot counter updates after the stop.

  2. What is kept. On a clean destroy, a profile-bound session’s storage state is captured and saved. Page contents and the current tab are not.

  3. From code. DELETE /v1/sessions/:id (204; idempotent) or DELETE /v1/agent-sessions/:id, for a session your code created; the slot is released immediately. Code must not delete a session it did not create to free a slot: ask whoever started it. No plan stops a session on its own except by idle or time limits (see Session was closed after inactivity).

  4. It still shows as running. Wait a moment and refresh; if it persists, press Stop again.

If it still fails

If Stop reports success but the session stays running for minutes, press Talk to a person in this chat (or open Help) and include the session id. No account action is needed.