Skip to main content

What Counts as a Browser Console Session? (Time, Pausing, and Resuming)

Updated over 2 months ago

What is a Browser Console Session?

A Browser Console session is any period of time when the automated browser is actively running actions on your behalf - navigating sites, logging in, filling forms, or uploading documents. Think of it as your virtual browser “coming online” to do work for you.

You’re only billed for the time the browser is actually working on your Problem - not while you’re thinking, editing instructions, or waiting for approvals.


How Does Session Time Work?

  • Session time accrues only when Browser Console is active and working.

    • The timer starts when you approve an action and Browser Console launches.

    • The timer pauses as soon as Browser Console completes the action, hits a checkpoint, or is waiting for your next instruction.

    • If you step away or take time to review/approve the next action, your session time is not running in the background.

  • Session time can be split across multiple “rounds” or actions within the same Problem.

    • You don’t lose time if you pause mid-way. Each Problem keeps track of your unused browser minutes.

    • Example: If you use 5 minutes today, you’ll have 15 minutes left for more Browser Console work under the same Problem before you need another tool action credit.


Pausing and Resuming Sessions

  • You control when each session starts.
    After each step, you can review progress, update instructions, or wait as long as you need.
    The session resumes when you approve the next Browser Console action.

  • No background billing:
    Time does not accrue while you’re waiting on emails, gathering documents, or thinking through your next move. You only use credits when Browser Console is actively automating a step you approved.


How Billing Works: Tool Action Credits (TACs) & Sessions

  • 1 Tool Action Credit (TAC) = 20 minutes of cumulative Browser Console time, used across any number of sessions within the same Problem.

  • Unused session minutes roll over within that same Problem. If you split your automation across several days or steps, you still get the full value of your TAC.

  • As long as you’re working on the same Problem, you can use up your minutes at your own pace.

Tip:
You’re never charged for time spent reading instructions, approving steps, or troubleshooting - just the time your cloud browser is “on and working.”


Example: How Session Time Adds Up

Let’s say your Problem requires three separate Browser Console actions:

  1. First step: Log in and navigate to a portal (2 minutes)

  2. Second step (next day): Fill out a multi-page form (4 minutes)

  3. Third step (after your approval): Upload evidence files (2 minutes)

Total time used: 8 minutes
TACs used: 1 (since you’re still under the 20-minute window for this Problem)
Remaining time: 12 minutes left for additional actions before another TAC is used.


Questions?

If you have questions about session timing or billing, contact support or check your problem logs for detailed time logs.

Did this answer your question?