Skip to main content
Every Komos run happens in a managed browser session. Choose the environment that fits the job so your automations stay reliable and compliant.
The legacy Chrome extension path is fully retired—runs only execute in the Cloud Sandbox or a managed self-hosted runner (Windows or macOS host).

​
Komos Cloud Sandbox

  • Cloud-hosted Chromium that spins up instantly, even when your team is offline.
  • Fresh session for every run - no risk of leftover cookies or cached data leaking between automations.
  • Perfect for schedules, API-triggered runs, and long flows that need guaranteed uptime.

​
Self-hosted Runner (Windows or macOS)

  • Installs a lightweight Komos agent on any desktop you control (physical or virtual).
  • Reuses domain-joined sessions, hardware tokens, Okta/SAML credentials, and any thick-client apps already present.
  • Ideal for flows that require intranet access, customer-specific VPNs, or desktop-only software.
  • Keep the host online and allow the Komos service to run in the background so tasks can claim it when needed.
  • Windows tips: run the provided PowerShell script (.\\start.ps1) from an elevated session, keep the VM unlocked, and let the Komos agent stay active so recordings and runs can resume instantly.
  • macOS tips: run ./start.sh on macOS 13+ (Apple Silicon or Intel), grant screen-recording + automation permissions, and keep the Terminal session or LaunchAgent online so the CLI can reconnect automatically.
  • Download the runner: use the public bundles shown in the “Add Self-hosted Runner” modal:
    • Windows: windows-runner.zip (then run .\\start.ps1)
    • macOS: mac-runner.zip (then run ./start.sh)

​
SSO and internal sites

If your automation needs to reach an internal site behind SSO (Okta, OneLogin, or similar), run it on a Windows VM that already has the necessary browser profiles and IdP sessions. We support both Komos-provided and customer-hosted Windows runners. Configure a service account on that VM, keep the runner online, and tasks will reuse the authenticated session to load intranet pages. For enterprise setup help, contact [email protected].

​
Which environment should I use?

  • Choose Cloud Sandbox for unattended work: schedules, API launches, or anything that must run on time without a human nearby.
  • Pick the Self-hosted Runner when the automation depends on your corporate network, native software, security hardware, or any credential that only lives on your desktops (Windows or macOS).
  • Set a default on the task detail page and override it per run whenever you need to switch.

​
Setup checklist

  • Cloud Sandbox is ready to go out of the box—no installation required.
  • Self-hosted runners (Windows and macOS) need the Komos desktop runner installed, outbound access to the Komos gateway, and a signed-in session that stays unlocked for the duration of the run.
  • After picking an environment, run a quick dry run to confirm waits, prompts, and credentials behave the way you expect.