Configure targets
Fleet exposes the local machine, separate browser profiles, supported VMs, and remote app-servers. On macOS, VM integration uses Tart; on Windows, Hyper-V is supported. VM command execution uses SSH and, where available, guest-agent or remote-control surfaces. There is no Fleet guest install path for research commands.
In Fleet settings, configure a VM's SSH/run/clone options or add an app-server on a Tailscale network. Browser settings choose the default page and enabled browsers. In a workspace's Targets view, select which of those targets may appear in New Research; a session can only choose targets allowed for that workspace.
Keep the boundary explicit
Local target execution uses the current host's privileges. A VM or remote host is an operator-provided execution environment; Beale does not claim to manage network isolation or destination control. Verify SSH identity, scope, and reachability before sending research work to a machine.
Remote app-servers expose their own workspaces and runs. Pairing and remote access are configured per server; do not assume a local workspace is automatically synchronized to a remote host.