Browser and terminal issues
Resolve blocked hosts, navigation failures, shared-control stalls, missing shells, and PTY fallback.
On this page
Browser host is blocked
Open Settings → Tools → Browser domain allowlist. Confirm the destination is an exact listed hostname or matches a *.suffix entry. Redirect targets are checked too.
Empty removes the extra allowlist, but built-in URL and SSRF protections still reject unsafe destinations. Do not disable a restriction without verifying the target.
Browser navigation or tool reference fails
- Confirm the panel has an active tab.
- Use Reload once.
- After navigation or mutation, take a fresh snapshot before the agent uses element references.
- Check whether You have control of the browser is shown. Choose Return to agent if an agent step is waiting.
- Preserve Browser state unavailable or the navigation error text.
Element references belong to a current snapshot and can become stale after page changes.
Clear session data
Use Clear Browsing History, Clear Cookies, or Clear Cache only for the relevant symptom. Clearing cookies signs out browser sessions. These controls affect the embedded browser, not the operating system’s default browser.
Terminal shell does not start
Open Settings → Tools → Terminal shell. Choose an installed shell. Auto prefers PowerShell on Windows; selecting Bash does not install Bash.
Confirm the active workspace exists and the shell executable is available on PATH.
PTY unavailable or interaction is degraded
The app can use a pipe fallback when the native PTY is unavailable. Preserve the warning and test a simple non-interactive command. Features requiring full terminal emulation may remain unavailable until native dependencies are valid.
A command appears stuck
Use the named terminal session or run Stop control. Do not terminate broad Electron, Node, or pnpm process groups. Check whether the command is legitimately waiting for input, an approval, network, or a child process before closing it.