Windows installer field test

Use an ordinary Windows 11 account. Record only technical pass/fail evidence.

Scope: this tests the developer-tools bootstrap only. It does not prove Financial Brain provisioning, a physical Brain passkey, Plaid, or QuickBooks.

1. Baseline

Start: Windows edition:

Architecture: ☐ x64 ☐ ARM64   Admin requested: ☐ No ☐ Yes

  • Claude Desktop initially present
  • Claude Code initially present
  • Git initially present
  • GitHub CLI initially present
  • Node 22+ initially present
  • Wrangler initially present

2. Exact download

jamesguldan.com/installer/downloads/Claude-Developer-Tools-Setup.exe

Get-FileHash "$HOME\Downloads\Claude-Developer-Tools-Setup.exe" -Algorithm SHA256

Expected: 0c6dc36aa9ca72635f88af16aa6b5a1baf5f373025b214222f8b4fdd3296b78b

  • Hash matches exactly
  • Executable opens normally

3. Setup and sign-in

  • Run Claude-Developer-Tools-Setup.exe normally
  • No developer shortcut or preconfigured shell used
  • Complete the installer's Claude, GitHub, and Wrangler sign-ins interactively
  • Any required administrator approval occurred before installation
  • Close PowerShell, reopen it, run the Verify script
  • Claude Desktop, Claude Code, Git, Node, npm, gh, and Wrangler pass

4. Recovery and repeatability

  • Run the executable again and confirm a clean idempotent pass
  • During that second run, close it after checks begin, then restart Setup
  • In PowerShell, save $savedPath=$env:Path
  • Temporarily filter entries containing \.local\bin or DeveloperCLI, then run Verify and record the expected PATH failure
  • Restore with $env:Path=$savedPath, reopen PowerShell, and confirm Verify passes

5. Result

Finish: Elapsed: Aggregate: ☐ Pass ☐ Fail

Error and recovery result:

Do not record: credentials, auth codes, tokens, browser URLs, email addresses, or account IDs.