--- name: ppp-setup description: Setup of ppp on this computer - checks what ppp needs (Python, git, pac, Playwright with Edge and ffmpeg, python-docx, Word, the packages of bi-design, the extensions and settings of VS Code, the model of the Agents view), installs the missing Python packages and sets up VS Code. Use when the user asks to check or set up ppp, on a new computer, or when a command reports a missing package or program. --- # Set up ppp on this computer The commands of `ppp setup` (outside a ppp project, `ppp` is the session's `Tool call`, else the line in `~/.ppp/tool-call.txt`): - `--check` lists each part ppp uses with `ok` or `missing` and the command that needs it; it changes nothing. - `--install` installs the missing Python packages with pip into the Python that runs ppp, then the ffmpeg of Playwright, and checks again. - `--vscode` sets up VS Code without a profile import: GPT-6.1 Sol, thinking level high, the context of 272K and the marketplace in `~/.copilot/settings.json`, which new sessions of the Agents view take; the settings of ppp in `settings.json` of the Default profile, whose settings and extensions the Agents view uses; the extensions with `code --install-extension`; the model list of VS Code, which then shows only GPT-6.1 Sol, Claude Opus 5.5, Claude Sonnet 5.5, Claude Haiku 5.5 and GPT-6 Astra (`--models`; while VS Code runs, a helper writes it once every window is closed). It backs each file up and keeps every other key and every value the user chose. - Programs (Python, git, pac, Edge, Word) the user installs; the report names where each comes from. 1. **Check.** Run `ppp setup --check` as the first call. Show in the chat which parts are missing and which command each one serves, grouped by the last line of the report: `RESULT: complete`, `ppp works; missing for single commands`, or `incomplete, required` (Python or git: ppp cannot work without them). 2. **Fix on one card.** When the report ends with `ppp setup --install installs: …` or `ppp setup --vscode sets: …`, ask on one decision card with an option per line: install the packages (pip downloads them from the internet into the Python that runs ppp), set up VS Code (extensions from the Marketplace, settings, the model and the model list of the Agents view), both (recommended), or not now. Run what the user chose. When pip fails, show its message; behind a proxy the user sets it once with `pip config set global.proxy http://:`, then run `ppp setup --install` again. When the report or `ppp setup --vscode` says the command line of VS Code is blocked by a group policy or not found, the extensions come by hand: give one card with the `vscode:extension/…` links it printed, one per line; the user pastes each into the address bar of the browser, lets it open VS Code and clicks Install there. Then step 3. 3. **Restart, enable, sign in, new chat.** When `ppp setup --vscode` printed `Installed the extension …`, or the check shows pac `missing` while `VS Code extensions` is `ok`, the setup goes on in VS Code itself, and the rest of this chat runs on the old state. Give the user one card for this step, with the answers "All as expected", "Deviation – I describe it", "Not possible", these steps in order and the expected result: the six extensions show as enabled in the Agents view, and Power Platform Tools shows the signed-in account. - Close every window of VS Code and open it again. - Agents view › Customizations › Extensions: enable each extension ppp installed for the Agents view (Power Platform Tools, Python, Python Environments, Pylance, Python Debugger, PowerShell). An installed extension stays off in the Agents view until it is enabled there; pac comes with Power Platform Tools. - When Power Platform Tools asks, sign in with the Microsoft work account. Without it pac finds no environments and no solutions. - Start a **new chat** in the Agents view and say "check ppp" there. Continuing in this chat can fail, since it started before the restart. - When the model picker still shows more than the five models: close every window of VS Code and run in PowerShell `python -I "$env:USERPROFILE\.copilot\installed-plugins\ppp\ppp\tools\ppp.py" setup --models`, then open VS Code again. End this chat's setup with that card; the check in the new chat confirms the result. 4. **Programs.** For each missing program, name where it comes from as the report says and which command lacks it until then. Python and git are required; Edge, Word and pac serve single commands (`ppp walk`, `ppp guide --word`, `ppp unpack` and `ppp pack`). pac is missing on a first run until Power Platform Tools is enabled for the Agents view (step 3). When the user reports a program installed, run `ppp setup --check` again. 5. **Hooks in VS Code.** When the report shows `missing` for `Python of the VS Code hooks` (Python from a conda or mamba environment, off `PATH`), run `ppp setup` once without an option: it records this Python for the hooks in `~/.ppp/python.txt`. Then the user runs "Developer: Reload Window". Done when the last `ppp setup --check` of this chat ended with `RESULT: complete`; or this chat ended with the card of step 3; or the user read each part still missing with the command it serves and where it comes from.