VPN & Firewall Compatible

Test Behind Your Firewall

The Ai2QA Local Agent runs on your machine, enabling tests against internal applications that are protected by VPNs, firewalls, or corporate networks.

The Problem

Cloud-based testing tools can't access your staging servers, internal tools, or applications behind corporate VPNs. You're stuck with manual testing or complex proxy setups.

The Solution

The Local Agent runs on your machine with VPN access. It connects outbound to Ai2QA Cloud, so no firewall rules need to change. Your browser session stays local.

How It Works

Install the Agent

Download and install the CLI on your machine with VPN access.

Connect to Cloud

The agent connects outbound to Ai2QA (no inbound firewall rules needed).

Run Tests Locally

Tests execute on your machine's browser with full network access.

Installation

Option 1: Install via npm (Recommended)

Terminal

npm install -g @ai2qa/local-agent

Setup Steps

1. Register an agent in your dashboard

Go to Dashboard → Agents → Register Agent. You'll receive a device token.

2. Login with your device token and agent ID

ai2qa-agent login YOUR_DEVICE_TOKEN --agent-id YOUR_AGENT_ID

Both values are displayed after registering your agent in the dashboard.

3. Start Chrome for debugging

Start a separate Chrome instance for the agent. Your regular Chrome stays open!

ai2qa-agent chrome

This opens a new Chrome window dedicated to testing — no need to close your regular browser.

✓ Agent Chrome is separate

Uses its own profile at ~/.ai2qa/chrome-agent-profile. Your regular Chrome tabs and sessions are completely untouched.

Other chrome commands

ai2qa-agent chrome --status — Check if agent Chrome is running

ai2qa-agent chrome --stop — Stop agent Chrome when done

ai2qa-agent chrome --restart — Restart agent Chrome

4. Start the agent in cloud mode

ai2qa-agent start --cloud

The agent will connect to Ai2QA Cloud and appear as "Online" in your dashboard.

Security Note

• The agent only connects outbound to Ai2QA — no inbound ports needed
• Your browser session stays on your machine — credentials never leave
• Device tokens are scoped to your tenant and can be revoked anytime
• All communication is encrypted via WebSocket Secure (WSS)