Install a Windows Environment
Install an agent host with a visible Chrome browser on Windows.
Run Misanthropic agents on your Windows desktop with up to four dedicated Chrome profiles. The installer downloads the runtime and prepares Chrome and Tailscale. No Docker, Node or .NET installation is needed beforehand.
Before you start
- Use a fresh Windows x64 machine and PowerShell 5.1+ in the intended user's desktop session.
- Get a protected Infisical bootstrap file and Misanthropic enrollment key from the operator.
- Allow access to the control plane, Infisical and official package downloads. Approve installation prompts.
Windows does not need registry credentials. Keep the desktop user signed in while agents run.
Infisical keys to provision for this host
| Key | Value |
|---|---|
WindowsEnvironment__ApiToken | Unique API token for this host. |
WindowsEnvironment__ControlPlaneMcpToken | Current control-plane MCP root. |
WindowsEnvironment__CertPassword | Password for the generated TLS certificate. |
The installer reads the explicitly selected project, environment and folder; it does not create secrets.
Install
Download the script, review it, then run:
Use the path to your protected bootstrap file. Enter the enrollment key at the hidden prompt;
do not put secrets in command history. The installer protects the installed Bootstrap\infisical.json
with access limited to the current user, SYSTEM and Administrators. Bootstrap credentials are not
placed in the Environment process environment.
If prompted to join Tailscale, sign in through the Tailscale desktop app, approve the host, then
repeat the install command. Keep port 5154 reachable from the control plane over the private
network only. The default control plane is https://misanthropic.astrixion.ai.
Verify
Expect Host is healthy after installation and your hostname marked healthy under Console
Environments. Create a disposable Room, select this host for an agent, and ask it to open
example.com and write a Room file. Expect a visible browser with a separate profile and the
file in the Room. Stop and delete the test Room when finished.
If startup fails, check the Misanthropic Windows Environment Scheduled Task and
%LOCALAPPDATA%\Misanthropic\WindowsEnvironment\Logs\host.stderr.log.
Update an installer-managed host
Download the current installer, then stage the desired release:
Staging does not interrupt work. Before activation, ensure protected Bootstrap\infisical.json
exists. An existing BWS-backed host needs an operator-approved bootstrap migration first, preserving
credential values. Stop all agents using this host, then stop the task and confirm
no managed Pi or Chrome processes remain before activation:
Activation preserves credentials, certificate, profiles and data. Existing legacy hosts, including Acerzarp, need their separate maintenance procedure; do not delete the installation to bypass refusal.
Need help? For Infisical/enrollment errors, check the operator-provided credentials and scope. For network errors, check Tailscale and private firewall rules. If the host disappears after sign-out, sign back in.
Release files and checksums. Fresh-host runtime acceptance remains pending operator verification.