Onboarding
PW AI · YOUR WORKSPACE STARTS HERE
Get the tools for PW AI work and connect your work accounts. PW Setup guides you through the steps, even if you don’t have GitHub access yet.
ONE PLACE TO GET STARTED
Choose your computer below. No sign-in required to download.
Version — · Free to download · GitHub access not required
~/PW-Setup/next-steps.txt. No repository or AI conversation is automatically created. Copilot CLI remains for existing plugin setup pending app-side acceptance. Non-technical users retain the h-key CLI handoff. Live access remains pending until Copilot's Microsoft/PW-MCP and per-client checks succeed.Prefer numbered text prompts? Download and review the launcher above, then run it with --plain (Mac/Linux) or -Plain (PowerShell). No Go or .NET installation is needed. The wizard uses your terminal's font and settings.
If your device blocks the download or launch, stop and contact IT. SHA-256 checksums are available for IT to verify the files.
Choose Set up or check this computer (the default, for new or existing devices) or I'm getting started with PW. Answer four short questions and review a read-only setup plan before approving changes. PW's default apps are VS Code and the Copilot app for everyone. You can add other apps later.
Use the GitHub account approved for PW work and your Microsoft PW account. Passwords and MFA stay in official sign-in flows.
If an admin needs to grant access, Setup prepares a request for your onboarding contact. Rerun after approval to continue.
The scripts target Intel/Apple Silicon Macs, Windows x64/ARM64, and Linux x64/ARM64 with Bash. They detect the chip locally, so no browser chip detection is needed. Phones, tablets, ChromeOS and 32-bit systems are not supported. Linux distributions and managed-device policies vary; see the platform notes above. Automated checks run on Mac, Windows and Linux, but fresh-device onboarding on every OS/chip combination has not yet been verified.
The command verifies the launcher against the checksum supplied by this page. The launcher then verifies the matching terminal executable against its embedded checksum before running it. A mismatch stops setup. This is not publisher signing and does not protect against a compromised page supplying changed files and checksums. Do not disable security controls or paste commands from untrusted messages.
No. You can download and start without it. To finish, you’ll need a GitHub account approved for PW work, membership in PW’s GitHub organization and Copilot access. Setup checks access and helps you request what’s missing.
No. Setup installs tools and the PW plugin, and configures GitHub’s Git credential helper with separate confirmation. It does not modify engagement repositories. GitHub CLI and Copilot manage their own sign-in storage.
Setup checks first and keeps working installations. Choose checking/fixing your current setup to leave individual changes for later; independent checks continue, while dependent steps stay blocked. New setup requires missing or broken prerequisites to be addressed or stopped. Available software updates offer Update, Keep current version (the default), or Stop. Nothing updates automatically.
Update checks support Homebrew, winget and cached apt metadata. Other installations, including Windows/Linux Copilot app updates, may require the official updater or IT; unknown availability is never called up-to-date. Local metadata may be stale, and newer software alone does not prove PW access. Deferred steps and next actions are saved in ~/PW-Setup/maintenance-summary.txt. A pending setup is not shown as complete.
If required tools are missing, Setup names them and offers Set up Homebrew and continue, Get help from IT, or Stop here (the default). Checking/fixing an existing setup also offers Leave for later. Only install Homebrew if permitted on your computer.
Choosing installation switches to the normal terminal. Review and approve Homebrew’s official installer there; it may need your Mac administrator password or Apple developer tools. The wizard returns afterward and checks Homebrew before continuing. Each tool still requires approval. If your computer is unsupported or policy blocks installation, stop and ask IT—never bypass security.
Installing software is only the first step. Setup hands off to Copilot to finish Microsoft sign-in and call the hosted PW MCP server. Until that succeeds, live access is not verified.
Send the request draft in the PW-Setup folder in your home directory to your PW onboarding contact or engagement lead. They can route it to IT or the platform owner. Never send passwords, tokens, MFA codes or device codes.