Recorder/local-agent issues

Recording is handled by the browser extension; local execution is handled by the Local Agent. Most issues here are connection or permission related.

Local AgentAgent not connected

The UI shows the agent as disconnected. Make sure the Local Agent is launched and running, and that your machine is reachable on the network.

WebRecording isn't capturing actions (browser extension)

Recording is handled by the BitAssert browser extension, not the Local Agent — the extension captures your actions and passes them to the platform. If nothing is captured, the extension is disabled, missing host permissions on the target site, or out of date. Enable the extension, grant it access to the site, reload the page, and start a new recording session.

WebThe site is blank in the recorder and won't load

The recorder opens the target site in an embedded frame. Sites that block embedding (via X-Frame-Options or a Content-Security-Policy frame-ancestors rule) refuse to render, so the recorder pane stays blank and no actions can be captured. This is enforced by the target site, not the platform — record against a page/environment that allows embedding, or use a test/staging build without the framing restriction.

Local AgentLocal run fails immediately

A local run ends as soon as it starts. The agent is not connected — start it and confirm the connection indicator before running.

Local AgentLocal results not saved

You can't find a local run afterwards. This is expected — local runs show live status only. Use Cloud execution for stored results.

Local AgentUI cannot reach the agent (port blocked or in use)

The platform connects to the Local Agent over a local WebSocket port. If the agent shows as running but the UI never connects, the port may be blocked by a firewall/VPN or already taken by another process. Allow the agent's port locally, close any duplicate agent instance, and restart the agent.

Local AgentAgent drops the connection mid-run

If the machine sleeps, the network changes, or the agent process is closed, the WebSocket disconnects and the live run is lost (local runs are not persisted). Keep the machine awake for the run's duration and reconnect the agent before retrying.

See Connect Local Agent and Recording.