Sessions, profiles and the session window

Launching and stopping sessions, profiles and devices, the live view, cookies and uploads, and the AI agent. Back to the Help center.

• The AI agent paused to ask you, or a site check paused the session — The agent stops for one of three reasons: it needs an answer from you, the next step has consequences and is held until you approve it, or the page showed a verification check a…
• AI chat cannot start: choose a proxy / none of your proxies can carry a chat — Every AI chat runs in a session, and every session goes out through a proxy you chose — the app never picks one for you.
• 'Still finishing the previous task' — Send is held — Send is held for a moment while the AI view catches up: either it is reattaching to a session that was already running, or the task you stopped is still finishing on the server.
• AI step failed: couldn't find it on the page / screenshot failed — When a step fails, the AI view shows a card with a plain headline and, where it makes sense, a suggested next instruction.
• '3 AI tasks are already running' (AI task limit) — At most 3 AI tasks can run at the same time across all of your sessions.
• 'This session stopped answering automated steps' (session_unresponsive) — The session had already failed to answer a step, and a quick check just before the next step got no answer either, so nothing more was sent. The live view may still show the page. End the session and launch a new one.
• Concurrent session limit reached (429 concurrency-limit) — Your plan allows a fixed number of sessions open at the same time, and you already have that many.
• Import or export cookies for a profile — Cookies are imported and exported from the session window's cookies pane while a session on the profile is running: Export saves the jar as JSON; Import reads a file in any common…
• Cookie jar too large for this session (413) — The cookie file is bigger than the browser running this session can accept in one go, so nothing was imported.
• Create a profile and pick a device — A profile is a saved iPhone Safari identity: a name, one device (iPhone model + iOS + Safari), and the proxy it launches through.
• What happens to a deleted profile (trash, restore, purge) — Deleting a profile moves it to a recycle bin (Trash).
• Which iPhone devices a plan can choose — Every paid plan can choose any device open for new profiles; the Trial includes the iPhone 13 and iPhone 13 mini, and a new trial profile uses the iPhone 13.
• Profile's device is 'On hold' and cannot launch — Some device profiles (a specific iPhone model, iOS and Safari version) are shown in the picker but temporarily not offered, because they are still being checked against a real…
• Uploaded file is empty or too large for the session — A file you send into a session travels to the session in one message, so each session has a per-file limit — often around 2.9 MiB, and never more than 64 MiB.
• Launch a session from a profile (what must be true first) — A profile launches when: you are signed in and online; the profile has one of your saved proxies chosen (the app never picks one for you); its device is not on hold; you are under…
• Live view connected but no video arrived — The window reached the streaming server but no picture came through.
• Manual, Agent and Pair modes; 'another client is taking over' — A session runs in one of three modes.
• 'No Mac was free to start this session' — None of the Macs that run sessions could take a new one at that moment, so your session was closed before it started.
• After a downgrade only the most recently used profiles/proxies can launch — If your account holds more saved profiles (or proxies) than your current plan includes, nothing is deleted, but only the most recently used ones — up to the plan's number — can…
• Page didn't load in the session (proxy slow, DNS, 403/404/429, TLS) — The page failed to load inside the session.
• 'Profile already in use': its other live session has to end first — A profile can run in only one session at a time.
• Export and import profiles (with or without their proxy) — Export writes a profile to a JSON file that holds its name, device, description and notes — not its cookies or logins — and Import reads that file and creates a fresh profile, in…
• Cannot create a profile: plan's saved-profile limit reached — Each plan includes a fixed number of saved profiles, and you have reached it.
• Couldn't save the note / profile edit — check your connection — The edit did not reach your account, usually because the connection dropped for a moment.
• Restoring a snapshot counts as a profile (limit) — A snapshot is a frozen record of a profile's device, name and description, and keeping snapshots costs nothing against your profile limit — restoring one creates a new profile…
• Profile storage is full (storage-quota-exceeded) — The total size of all your live profiles has reached your plan's storage allowance, so launching a session that uses a profile is refused.
• Recipe limit reached / session already saved as a recipe — A recipe is a saved copy of the steps a finished AI session took (not its transcript), and two rules stop a save: each plan keeps a fixed number of recipes, and a session is saved once.
• 'Reconnect to make changes' — the app is offline and view only — Everything in the app lives on your account, so a change needs a connection to it.
• A saved credential was not typed: 'this page is on … and it may only be typed on …' — Driftstack types a saved credential only on a secure page of a website it was saved for. Anywhere else the step is refused before anything is typed, and the task stops there.
• Saved credentials: save a password for the AI agent, use it in a task, delete it — Save the value once on the dashboard, locked to the websites it is for, and write its handle in an agent task. The AI is given the handle, never the value.
• Session was closed after inactivity — The session was ended because nothing happened in it for a while.
• 'The part of this session's connection that we run did not start / stopped' — A part of the session's network path that we operate failed — before the session ran, or while it was running.
• 'This session has ended and can no longer be used' (410) — The session you sent that action to is over — it was stopped, timed out, or ended on our side — and a session cannot be brought back.
• 'Session ended' overlay, 'Couldn't reach the live-stream server', Reconnect — "Session ended" means the browser behind this window really stopped — the overlay's recap line says why (inactivity, time limit, no Mac free, and so on).
• 'The session is still starting. Try again in a few seconds.' (409 session-not-ready) — A message reached a session whose browser had not finished starting, even after waiting for it. Nothing ran; send the same message again a few seconds later.
• 'Session time limit reached' (sessions have a time limit) — The session ran for as long as a single session may run, or the trial ran out of session time, and it was closed.
• Session operation exceeded its timeout (504) — One action on a running session did not finish inside the time limit the request allowed; the session itself is usually still running.
• Session window is view only: keyboard/device input unavailable — You can see the session but cannot tap or type.
• The session window could not open — The desktop app could not open the session window.
• Stop a running session (what is lost) — Press Stop on the session's card (Sessions in the sidebar, or the profile's row).
• 'requires admin role on that team' when launching or stopping — In a team owner's workspace your role is member or admin: a member can look at the owner's saved things but cannot change them, so launching, creating and stopping sessions need…
• Watch a session you started from code — A session your program started (POST /v1/agent-sessions) is listed under Sessions in the desktop app's sidebar as an "API session"; press Watch to open its live iPhone window.
• 'Starting the VPN tunnel… the address bar unlocks once the session is live' — The address bar stays locked until the session is live.