Para Studiodocs

Para Studio on Windows

Two ways to start Para Studio on a Windows PC, both with a plain yes or no before anything is installed:

  • The portable zip (new, the one to try first). Download one zip, extract it, double-click Paraloop-Studio.exe. Nim and the C compiler are inside the zip, so there is nothing to detect or install for them. See The portable zip. A signed version comes later; for now the program is not signed and Windows warns once.
  • The batch file. In a folder you already have, double-click Paraloop-Studio.bat. It checks what your PC has, offers to install a missing C compiler, git or Nim (saying exactly what, from where and into which folder, and installing it only after you answer y), builds the para tool, prints the same startup checks as the Studio page, starts Studio and opens it in your browser. The rest of this page is about the batch file, after the zip section. Like the Mac launcher (mac.md), any answer but y stops with what to install by hand.

Status: unverified. Both launchers were written and their text was checked on Linux only. Nobody has run them on a real Windows PC yet, so you are the first: please send the captain what you see if anything differs from this page. In particular these have never been checked: the Windows warning about a downloaded file, the double-click itself, the winget installs and the Nim install the batch file offers, and whether Studio and its game window work from a plain Windows window at all (opening the game window on Windows has never been checked either; see platforms.md). The other route, typing commands in Git Bash, is windows-first-game.md; it is also not fully checked.

Something went wrong? Go to Windows troubleshooting: it has the Windows warning screens, the antivirus, the PowerShell "running scripts is disabled" message, a compiler that is "not found", administrator prompts and the Codex setup step, each with what to do.

Starting from nothing and want the batch file? The one-line installer (Install with one line) makes the parastudio folder and runs the same launcher for you. Testing the zip for the captain? The zip test is a short checklist for what to time and write down.

The portable zip

What it is. One zip, Paraloop-Studio-<version>-windows-x64.zip (about 135 MB), holding one folder, Paraloop-Studio:

In the folder What it is
Paraloop-Studio.exe The launcher: a native program (no cmd, no PowerShell, no execution policy) that does what Paraloop-Studio.bat does.
nim-2.2.10\ Nim 2.2.10 and nimble, unmodified, from nim-lang.org.
mingw64\ The MinGW-w64 C compiler that Nim's own Windows installer sets up (GCC 11.1), from nim-lang.org, minus the parts a C build never runs (Fortran, D and Objective-C compilers, a debugger).
parastudio\ Para Studio at one exact commit, with its .git folder, so save points work.
licenses\ What Nim and MinGW are licensed under, and where their source is.
README.txt The three steps below.

What you do.

  1. Download the zip. See Where the zip comes from. It is about 135 MB. If you were asked to time the warnings (see the zip test), do not unblock it. Otherwise you may right-click the zip, choose Properties, tick Unblock at the bottom and click OK: that removes Windows' "from the internet" mark, so most of the warnings below do not appear.
  2. Extract it to a short folder. Right-click the zip, Extract All, and extract into a short folder such as C:\ParaStudio (a long path can make a build fail; the launcher warns when the folder's path is longer than 90 characters). Not into Downloads, and not into a folder in a folder in a folder. Do not double-click from inside the zip: it will not find the rest.
  3. First run. Open C:\ParaStudio\Paraloop-Studio and double-click Paraloop-Studio.exe. If Windows shows a blue "Windows protected your PC" screen, see The blue "Windows protected your PC" screen.
  4. Wait for the first start. A black window prints seven numbered steps. The first start fetches the game libraries and builds Studio, which takes several minutes; it says so and is working even when nothing moves. Later starts take seconds. Studio opens in your browser. Keep the black window open while you use Studio; press Ctrl+C in it or close it to stop Studio.
  5. Do the setup checklist in Studio's top bar: see The setup checklist.

Where the zip comes from

The zip is published on the project's GitHub Releases page, https://github.com/PDepaula/parastudio/releases, as Paraloop-Studio-<version>-windows-x64.zip with a .sha256 file beside it. A release is created as a draft by the portable workflow when a person pushes a tag called portable-v..., and a person publishes it by hand. No release had been published when this page was written, so the Releases page may be empty: until it is not, the person who invited you sends you the zip. (The workflow also keeps every build for 14 days as a workflow artifact, which only people with access to the repository can download.)

To check that a download is the one that was built, open PowerShell and run Get-FileHash .\Paraloop-Studio-<version>-windows-x64.zip -Algorithm SHA256; the hash must equal the one in the .sha256 file. This is optional, and the commands have not been tried on a real PC.

The blue "Windows protected your PC" screen

The program is not signed yet, so Windows' SmartScreen may stop it the first time with a blue screen titled Windows protected your PC and "Microsoft Defender SmartScreen prevented an unrecognized app from starting". That is the only reason for it; it does not mean the zip is damaged. To go on:

  1. Click the small words More info on that screen. (Until you do, there is no way to run it.)
  2. A Run anyway button appears. Click it.

You see this once per copy of the program. If you unblocked the zip before extracting it, you may not see it at all. If there is no More info, or Run anyway is missing, your PC is managed by an organization or Smart App Control is on: see Windows blocks it with no Run anyway.

Signing will remove this screen later. The project plans to sign the launcher, and the build already has a marked place for it (SIGNING HOOK in .github/workflows/portable.yml), but there is no date, and nothing is promised. Even a signed program may show the screen for a while, until Windows has seen enough people run it. Until then, More info, then Run anyway is the way in.

Windows Security (Defender) may scan or flag it

Windows Security (Microsoft Defender) may scan the zip when you download it and the program when you first run it, and an unsigned program from a new place is flagged more often than most. What you may see:

  • A short scan the first time, which delays the black window by a few seconds. Wait.
  • A notice that something was blocked or removed ("Threats found", "Virus & threat protection"). The zip is made by a public build on GitHub, so do not assume it is a real threat, but only you decide. If you trust it, see Defender removed or blocked a file.

Which of these appears on a real PC has not been checked: nobody has run the zip on a real Windows PC yet.

The setup checklist: Claude or Codex

Studio's chat needs one of two programs installed on your PC and signed in by you: Claude Code (claude) or Codex (codex). Studio never installs them and never asks for a login. The checks run before any chat (the pill in Studio's top bar; the black window prints the same lines at step 6 and never stops Studio from opening):

Check For What it means What to do if it fails
installed Claude, Codex The program is on your PC Install it from its own page (https://code.claude.com/docs/en/setup or https://developers.openai.com/codex/cli), then press Check again
signed in Claude, Codex You are signed in Open a terminal, run claude (or codex) and follow its sign-in, then Check
trusts this folder Claude, Codex You answered "Yes, I trust this folder" in that program, in this folder Open a terminal in the parastudio folder, run claude (or codex) and choose Yes, I trust this folder (the highlighted choice is "No, exit": move down first)
may change files in games/ Claude only The project's .claude/settings.json lets it Put the file back with git checkout -- .claude/settings.json

Claude is the default. To choose Codex instead, or Claude when Claude does not work for you: if the one in use is not installed or not signed in and the other is installed, the checklist shows a Use Codex instead (or Use Claude instead) button right there, before you have a game. That pick is for the whole Studio; each game can still pick its own later. Using either costs your own plan or credit. A Speed menu under Pip's name picks how hard the producer thinks, and a small line shows the model and effort it reported for the last message (The Studio page).

On Windows the "trusts this folder" check for Claude cannot answer "no" (the key format in Claude's settings file has not been checked on a real PC), so a missing trust shows as amber Could not check, not red. For Codex it is always amber unless trust is recorded. Treat amber as a reason to do the trust step once. If one of the two fails and you do not want to fix it, use the other one. If both fail, you can still press Play and use Check and Save; only the producer's chat is unavailable.

Codex on Windows needs one more step, which Studio does not show yet. On Windows, Codex only lets its helper change files after it has set up its own safety sandbox once. Studio does not trigger that setup and does not yet show the step: you do it in Codex yourself, see The Codex sandbox step. This is the likely reason for a Codex producer that says it cannot edit anything. Claude has no such step.

How long until the first game

Unverified. Nobody has timed the zip on a real Windows PC; the zip test is how it gets timed, and this page will say the number once there is one. What the code says:

  • Download and extract: depends on your connection; the zip is about 135 MB.
  • First start of Paraloop-Studio.exe: "several minutes" (the launcher's own words), because it fetches the game libraries and builds Studio. Later starts take seconds.
  • Setting up Claude or Codex: a few minutes if you have to install and sign in.
  • Pressing Play the first time builds the game, which takes "a few minutes on Windows" per the step-by-step page; later builds are quick.
  • A producer turn that makes a game depends on the model and effort; a big model on high effort is the usual reason a turn is slow, and the Speed menu's Quick is the first thing to try (The Studio page).

The first start is the long wait. If it seems stuck, or stops with a block of text, see Windows troubleshooting.

What it asks, and what it never does.

  • The only thing it can offer to install is git (nimble fetches the game libraries with it), and only when your PC has none: it prints what (Git for Windows), from where (winget's catalog), the exact command (winget install --id Git.Git -e --source winget --scope user), where it goes (your user folder) and that it needs no administrator password, then asks (y/n, Enter means no). Only y or yes is yes. If you say no it stops with what to install by hand.
  • It never downloads Nim or a compiler (they are in the zip), never runs a downloaded script, never asks for an administrator password, never changes your Windows settings or PATH (it extends the PATH of its own window and the programs it starts, nothing else), and never reads, copies or changes any login or setting of Claude or Codex. The only things it fetches are the game libraries (nimble, through git) and whatever you said y to.
  • tmp\launcher.log in the parastudio folder records what each step printed, with the time, and how long the start took. It never holds Studio's own output (that carries a private key).
  • Paraloop-Studio.exe --dry-run (or --check) shows what it would do and changes nothing. --no-studio sets up and builds but does not start Studio; --no-open starts Studio without opening a browser tab.

If something is missing or fails. The launcher stops with a block to send the captain (the same as the batch file's, below). If it says the compiler or Nim folder is missing, the zip was not fully extracted: use Extract All again.

Where git comes from. The zip does not carry git (it is much larger than the rest, and bundling it would be the next step if the git question turns out to be the one prompt left).

Updates. There is no auto-update. A new zip is a new download; the captain can also update the parastudio folder inside with git pull.

Building it yourself, and what is checked. python tools/launcher/build_portable.py assembles the zip on a Windows PC that has Nim 2.2.10 and a C compiler on PATH (to compile the launcher); it checks both downloads against the SHA-256 pinned in the script and the one nim-lang.org publishes beside each file. The portable workflow (.github/workflows/portable.yml) builds it on a GitHub Windows machine on every change to the launcher, then unpacks it into C:\ps, and runs it with a PATH that has Windows and git on it and nothing else (no compiler, no Nim), in a clean home folder: the launcher must find the zip's own tools, fetch the libraries, build para, start Studio, and Studio's page must load with its key. That proves the zip works on a clean machine; it does not prove a window opens (a hosted machine has no graphics card), the SmartScreen prompt, or a person's double-click. The zip is kept as a workflow artifact on every run. A release is made only when a person pushes a tag called portable-v..., and then only as a draft that a person publishes. Signing is a marked hook in that workflow (SIGNING HOOK): once the captain has an Azure Artifact Signing account it signs the launcher before the zip is made, and the workflow can be set to fail on an unsigned build.

Windows troubleshooting

Find your message, do what is under it. Everything here is tied to what the launcher and Studio do in code and in their tests; nothing has been run on a real Windows PC yet, so each entry says what is known and what is not. When you send a report, send the block the launcher prints between the ==== lines and the file tmp\launcher.log (see If something fails).

Windows blocks it with no Run anyway

You see "Windows protected your PC" with no More info, or More info shows no Run anyway, or a box says an administrator or your organization blocked the app.

  • Your organization manages the PC (work or school): an administrator set the rule, and you cannot change it. Ask them to allow Paraloop-Studio.exe (a SmartScreen or app-control exception for the file, or for the folder you extracted it to).
  • Smart App Control is on (Windows 11, Settings, Privacy & security, Windows Security, App & browser control): it blocks apps that are not signed, with no override. Turning it off is permanent on that Windows install, so do not do it casually; asking for the signed version later is the other way. Unverified: whether it blocks this program has not been tried.
  • Extracted from the wrong place: extract with Extract All to a normal folder such as C:\ParaStudio, not from inside the zip.

Defender removed or blocked a file

Windows Security shows "Threats found", or the black window says gcc.exe, nim.exe or Paraloop-Studio.exe is missing after you extracted everything.

  1. Open Windows Security, Virus & threat protection, Protection history, and find the item that names the file. If it is from the folder you extracted, and you trust where the zip came from, choose Actions, then Restore (or Allow on device).
  2. To stop it happening again, under Virus & threat protection settings, Manage settings, Exclusions, Add or remove exclusions, add the folder C:\ParaStudio. Opening these settings may ask for an administrator's OK. On a PC an organization manages, an administrator has to do this for you.
  3. Extract the zip again (Extract All, into a fresh folder), because a removed file stays missing.

Unverified: which files, if any, Defender flags in this zip has not been seen on a real PC. If it flags one, send the captain or the person who invited you the exact name it shows.

"running scripts is disabled on this system" (PowerShell)

PowerShell's execution policy refuses to run a saved .ps1 file; the Windows default (Restricted) allows individual commands but no script files. You can hit it by saving install.ps1 and running .\install.ps1, or from another program's own installer.

  • With the zip, it does not apply: Paraloop-Studio.exe is a native program that does not use cmd or PowerShell, so there is no policy to change. Use the zip.
  • The one-line installer (Install with one line) pastes the script as text: irm https://pdepaula.github.io/parastudio/install.ps1 | iex needs no policy change. If you downloaded it first, run it the way that page shows (Get-Content -Raw .\install.ps1 | iex), not by file name.
  • The Claude Code or Codex installer may hit the same message. Run the exact line their page gives (https://code.claude.com/docs/en/setup, https://developers.openai.com/codex/cli), which is a pasted command, not a saved file. If you must change the policy, do it for one window only: Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass lasts until you close that window. Do not change it for the whole PC, and an organization's policy may forbid even this.

A script or .bat is blocked ("Security Warning", "blocked")

The zip does not need any script. If you are on the batch file (Paraloop-Studio.bat) and Windows shows a "Security Warning" box, click Run; to stop it for good, right-click the file, Properties, tick Unblock, OK. A .bat or .cmd that came from the internet is blocked with no override when Smart App Control is on (see Windows blocks it with no Run anyway); the zip's .exe is the way around that. Never run a script file you were not expecting.

"No C compiler was found", or the producer says it cannot find the compiler

  • With the zip, the compiler is mingw64\bin\gcc.exe inside the Paraloop-Studio folder, and the launcher uses it ahead of anything on your PATH. If it says no compiler was found, the zip was not fully extracted, or Defender removed a file: extract again (Extract All) and see Defender removed or blocked a file. If it says the Nim folder is missing, the same.
  • With the batch file, the launcher looks for gcc, cc or clang on PATH and in a few usual folders, and offers winget install --id BrechtSanders.WinLibs.POSIX.UCRT -e --source winget. Any MinGW-w64 gcc works. Visual Studio's cl.exe is not used. After installing, close the window, restart the PC once and try again.
  • The producer's chat says "no compiler" although the launcher found one. The producer no longer runs its own compiler check: tmp\para.exe producer-context looks for gcc, then cc, then clang (Windows compilers such as WinLibs have gcc.exe and no cc.exe) and tells the producer which it found. If it still says it cannot find one, start Studio from the launcher again, since the launcher puts the zip's compiler on PATH for the programs it starts, and send the report. Unverified on Windows.

Administrator prompts ("Do you want to allow this app to make changes?")

The launcher never asks for an administrator password and the zip needs none. Three other programs can, and each is a prompt you can say no to:

  • Git for Windows, if you have no git and answer y to the launcher's question. Its winget package says it elevates itself even with --scope user, so an administrator prompt can appear once. If you cannot approve it, install git by hand from https://git-scm.com/download/win (ask an administrator if you cannot), then start the launcher again.
  • winget may need elevation for some packages and asks you first.
  • Codex's Windows sandbox setup (next entry). This is the one most often hit.

Only approve a prompt that names a program you were expecting. A person trying the zip for the captain should write each prompt down (the zip test).

The Codex sandbox step

Symptom: you picked Codex as the producer, it answers, and then says it cannot change any file or run any command, or every action is refused. Cause (from Codex's source and documentation, not yet reproduced on a real PC): on Windows, Codex only lets itself write files and run commands after a Windows sandbox is set up; Studio runs Codex without its own screen where that happens, so nothing ever asks you.

What to do (in Codex, not in Studio; Studio does not trigger this setup, and Studio does not show the step yet, a later version will):

  1. Open a terminal in the parastudio folder and run codex.
  2. If Codex offers to set up its Windows sandbox, follow it. Codex documents three modes (https://learn.chatgpt.com/docs/windows/windows-sandbox): mxc, the recommended one on newer Windows 11, which needs no administrator-approved setup; elevated, a fallback whose setup needs an administrator's OK (the Windows prompt "Do you want to allow this app to make changes to your device?"); and unelevated, a weaker last fallback. Choose what Codex recommends for your PC. Your organization's rules may decide for you.
  3. If you are not an administrator and the mode you need asks for one, ask an administrator to approve it or to provision it for your user. Codex's page describes the command and settings; read it there, since they change with Codex's versions.
  4. Close Codex, then in Studio press Check and try the producer again.

If you cannot or do not want to set up Codex's sandbox, use Use Claude instead in the setup checklist, which has no such step.

Studio does not open in my browser

The black window prints a link starting http://127.0.0.1:. Copy it into your browser yourself. If Windows Firewall asks whether to let the program through, Studio only listens on your own computer: Cancel or Allow should both work; tell the person you are working with which prompt you saw.

"Windows can stop a build when a path gets too long"

You extracted into a deeply nested folder. Delete it and extract again to a short folder such as C:\ParaStudio.

I closed the black window and now Studio is gone

That stops Studio. Double-click Paraloop-Studio.exe again; it takes seconds the second time.

If your problem is not here, If something fails says exactly what to send.

The batch file

Everything from here to the end of this page is about Paraloop-Studio.bat, the route for a folder you already have (the zip above does the same without it).

What you need

Studio needs three things. The launcher checks for each and offers to install what is missing (see "If something is missing" below), so you can let it do that. To install them yourself instead, in this order, saying yes to the defaults (these are also the instructions it shows when you answer no):

  1. A C compiler (the game is turned into a program by one). In a normal terminal (press the Windows key, type terminal, press Enter) run:

    winget install --id BrechtSanders.WinLibs.POSIX.UCRT -e --source winget
    

    Any MinGW-w64 gcc works.

  2. git (keeps your save points): download Git for Windows from https://git-scm.com/download/win, or run winget install --id Git.Git -e --source winget --scope user.

  3. Nim 2.2.10 (the language the games are written in; nimble, its package tool, comes with it): download https://nim-lang.org/download/nim-2.2.10_x64.zip, unzip it somewhere permanent such as C:\nim, run finish.exe inside the unzipped folder and let it add the Nim folders to your PATH. It must be exactly 2.2.10; another Nim on the PC is left alone.

Also needed: the parastudio folder from the captain, fully unpacked (if it came as a zip file, right-click it and choose Extract All; double-clicking from inside the zip does not work), in a folder with a short plain path such as C:\Users\you\parastudio, and an internet connection. The first run downloads the game libraries and builds para, which takes several minutes; later starts take seconds.

First time

  1. Open the parastudio folder in File Explorer and double-click Paraloop-Studio.bat (it may show as just Paraloop-Studio).

  2. If Windows shows "Windows protected your PC" (SmartScreen), click More info, then Run anyway. Windows warns about any program file that came from the internet; this is how you tell it you trust the captain's copy. If the file's Properties (right-click it) show an Unblock box at the bottom, tick it and click OK once; that stops the warning for good.

  3. A black window opens and prints numbered steps. Each says what it is doing:

    Step What you see What to do
    1 C compiler "ok", or "MISSING" If missing, see "If something is missing" below.
    2 git "ok", or "MISSING" Same.
    3 Nim 2.2.10 "ok", or "MISSING" Same. All three are checked before anything is offered, so every offer comes in one go.
    4 Game libraries "Nothing is printed here while it works" Wait a few minutes. It is working even when nothing moves.
    5 Building para the same Wait a few minutes.
    6 Claude or Codex The same startup checks the Studio page shows (installed, signed in, folder trusted), each "ok" or with one fix line See "The producer's chat" below. They never stop Studio from opening.
    7 Starting Studio Studio opens in your browser Keep the black window open while you use Studio.
  4. To stop Studio, press Ctrl+C in the black window (answer Y if it asks "Terminate batch job"), or just close the window.

Next times

Double-click Paraloop-Studio.bat. Steps that are already done say "ok" and are skipped (the libraries) or take seconds (only what changed is rebuilt), so it goes straight to Studio.

If something is missing

After the three checks, for each missing one the launcher prints what it would install, from where, into which folder and how big, then asks a question ending in (y/n, Enter means no). Type y and press Enter to install it; just Enter, n or anything else installs nothing.

Missing What it offers From Where it goes
C compiler WinLibs GCC (MinGW-w64), with winget install --id BrechtSanders.WinLibs.POSIX.UCRT -e --source winget winget's own catalog (winget is the app installer that comes with Windows); the files come from github.com/brechtsanders/winlibs_mingw your user folder, %LOCALAPPDATA%\Microsoft\WinGet\Packages; no administrator password. winget shows the size as it downloads (a few hundred MB) and adds the compiler to your user PATH itself
git Git for Windows, with winget install --id Git.Git -e --source winget --scope user winget's own catalog; the installer comes from github.com/git-for-windows your user folder, %LOCALAPPDATA%\Programs\Git; no administrator password. Its installer adds git to your user PATH itself
Nim 2.2.10 the official release zip https://nim-lang.org/download/nim-2.2.10_x64.zip (about 28 MB), downloaded with curl.exe; its SHA-256 must match the .sha256 file nim-lang.org publishes next to it and the value written in the launcher, or it stops and installs nothing unpacked with tar.exe into %USERPROFILE%\.paraloop\nim-2.2.10; no administrator password; added to the PATH of this window only, Windows settings are not changed

winget may first ask you to agree to its catalog's terms; answer Y there if you agree. If winget is not on the PC (it comes with Windows 10 and 11), the launcher cannot offer the C compiler and git and lists the steps to do by hand. The Nim offer is only made on a 64-bit Intel or AMD PC (AMD64), the PC the official zip is built for.

When you answer no, or an install did not finish, the launcher stops with a block like this, listing only what is still missing, followed by the steps in "What you need":

------------------------------------------------------------------------------
Studio cannot start yet: something it needs is still not on this computer.
Nothing you said no to was installed. To install it yourself, follow what is
listed below, then close this window and double-click Paraloop-Studio.bat again
(or double-click it again now and answer y).
------------------------------------------------------------------------------
  • Installed it and it still says MISSING? Windows only hands a new program's location to windows opened after the install, and sometimes only after you sign out and back in. Restart the PC once and try again. If it still does not find it, send the captain a photo of the window.
  • "Found a different Nim (...)" means another Nim version is installed. The launcher leaves it alone and needs 2.2.10 next to it.
  • "I cannot find tools\launcher\launch.bat" means the folder is not fully unpacked (see "What you need").

The producer's chat

Studio's chat needs the claude (Claude Code) or codex program installed and signed in on your PC. The launcher never installs it and never handles sign-in. Before it opens the page it runs tmp\para.exe studio --check, the same read-only startup checks the Studio page shows: whether Claude or Codex is installed, signed in and trusts this folder, each "ok" or with one plain fix line. Whatever they say, Studio still opens. Whether the chat runs from the launcher's plain Windows window, rather than Git Bash, has never been checked.

If the game window does not open

Press Play in Studio. If the PC cannot open the game window, Studio says "Your computer could not open the game window. This is usually a graphics or display problem..." Click Show the details and send the captain that message and the lines under it. On a virtual machine this is expected: it often has no OpenGL (see the top of windows-first-game.md).

If something fails

The launcher stops and prints a block like this (a missing tool is not this block; it has its own message above):

==============================================================================
Something went wrong. Please send the captain everything between these lines.
------------------------------------------------------------------------------
Step:     5 of 7, build para
Problem:  Building para failed. The log has the compiler's words.
Computer: Microsoft Windows [Version 10.0.22631.4460], AMD64
Log file: C:\Users\you\parastudio\tmp\launcher.log   (attach this file too)
Last lines of the log:
  | ...
==============================================================================

Send the captain that whole block (click the window's icon, Edit, Select All, then press Enter to copy, and paste), and attach the file named on the Log file: line. The log is plain text: what each step printed, and nothing secret (Studio's own output, which carries its private link, is not in it).

What the launcher does and does not do

  • It installs nothing without asking first, and only y or yes counts as yes. If the window cannot take an answer at all, that counts as no.
  • It never asks for an administrator password, never runs a script downloaded from the internet, and does not change your PATH or any Windows setting itself. It looks for Nim, a C compiler and git on your PATH and in the usual folders (for example %USERPROFILE%\.paraloop\nim-2.2.10, C:\nim, %USERPROFILE%\.nimble\bin, C:\Program Files\Git\cmd, the WinLibs folder winget uses), and extends the PATH inside its own window only. (When you say yes to a winget install, winget and Git's installer add their program to your user PATH, as they always do.)
  • It talks to the internet only to download Nim (and its checksum) from nim-lang.org, through the winget installs you said yes to, to let nimble fetch the game libraries, and through git. No telemetry.
  • It does not read, copy or change any login or setting of Claude or Codex.
  • To see what it would do and what it would offer without installing, building, opening or asking anything, open a Command Prompt in the parastudio folder and run Paraloop-Studio.bat --dry-run (or --check, the same). The checks still really look; the offers and the later steps only say what they would do.

What was and was not checked

Same steps and wording as the Mac launcher (tools/launcher/launch.sh), with two differences: it checks all three tools before it offers anything, and it leaves finding the chat program to para studio --check.

  • Checked on Linux: the shape of both files and the rules of the offers, by tests/test_launcher_bat.nim, reading the script's text: plain ASCII, Windows line endings, every goto and call has its label, no label twice, no parenthesised blocks; --dry-run and --check both make a dry run; the one question takes only y or yes as yes; every install command comes after the dry-run exit and a yes; each offer names what, from where, where to and how big; the Nim zip is checked against the published and a pinned SHA-256 before it is unpacked; nothing runs sudo, runas, setx, reg add, PowerShell or finish.exe. That says nothing about what the script does when cmd.exe runs it.
  • The offers to install have never run anywhere: not on Windows, and not under Wine (Wine was not available when they were written). In particular whether winget accepts --scope user for Git.Git on a given PC, certutil's output on a real PC, and the curl.exe and tar.exe that come with Windows were not checked.
  • Run once under Wine on Linux, on an earlier version of the script (before the library check also looked at the --path folders, before the chat-program step was removed and put back as para studio --check, and before the offers to install; those parts were not rerun): the whole script (a first run and a second run, Nim of the wrong version, everything missing, a failing build, a failing Studio, --dry-run, --help, a bad option) was driven through Wine's cmd.exe with stand-in programs for nim, nimble, git, a C compiler and para, and printed the messages in this page. Wine is a re-implementation of Windows, not Windows: real cmd.exe and the real where and findstr can differ (Wine's findstr ignored the /i /x /l switches, and its where had to be replaced by a stand-in), and the stand-ins never ran a real compiler.
  • Set up to run on a hosted Windows machine: the windows-launcher job in .github/workflows/platform-check.yml runs Paraloop-Studio.bat --dry-run there, once with Nim installed (it must finish ok), once pretending everything is missing (it must print the offers above, ask nothing and install nothing), and three times more with the dry-run-only hook PARALOOP_LAUNCHER_DRY_ASK=1, which asks each offer's real question and says what it would do for the answer it got, still running no winget, curl.exe or tar.exe: with only Enter typed, with the input closed and with y typed for each question. Enter and a closed input must print "Okay, nothing was installed." and never a "would: install" line, y must print "would: install" for all three, each offer (what, from where, the winget ids, where to, how big) must come before its question, and nothing may be created in %USERPROFILE%\.paraloop. It is started by hand only (workflow_dispatch), and had not been run when this page was written (the hosted runners are paused; see platforms.md). If it has run, it proves that cmd.exe really runs the script, its checks, its messages, the question and the yes/no default on a hosted Windows runner. It still cannot prove a real download or install, winget, SmartScreen, a real user PATH, or a person typing.
  • Also set up to run on a hosted Windows machine: the installer workflow (.github/workflows/installer.yml, install.md) runs launch.bat --check --no-studio there with the offers faked and PARALOOP_LAUNCHER_UNATTENDED=1 (every offer must be answered no without asking, nothing installed, Studio not started), and runs it for real through install.ps1 with Nim already installed. Same limits as the job above.
  • The portable zip, checked on Linux: tests/test_launcher_exe.nim compiles tools/launcher/launch.nim and runs it against a throwaway folder shaped like the zip with stand-ins for nim, nimble, gcc, git, winget and para: the seven steps in order with the zip's own tools ahead of anything on PATH, a second run skipping the libraries, a failure printing the block to send, a half-extracted zip stopping with the way out, the git offer asking first (only y or yes, nothing run otherwise, nothing asked unattended), --dry-run doing nothing, and the log never holding Studio's output. tests/test_portable.nim keeps the zip script, the launcher and the workflow in agreement. The zip itself was assembled on Linux with a stand-in launcher to check its layout (a clean git status inside it, one top folder, no finish.exe).
  • The portable zip, set up to run on a hosted Windows machine: the portable workflow (above). It had not been run when this page was written.
  • Never checked: the SmartScreen prompt, the real double-click, a real winget or Nim install from this script, a yes or no typed by a person, a friend's PATH, nimble and the para build from this script, Studio's browser and chat from a plain Windows window, and the game window.