Find your symptom, try the fix, and tell your facilitator if you’re still stuck. Escalating early is fine; it’s how we get Windows problems fixed for everyone.
Before your session
Codex app from the Microsoft Store, signed in
Node.js 18 or newernode --version
Git for Windowsgit --version
Your LedgerLoop fork cloned to a short pathC:\src\ledgerloop
Installing and opening Codex
The Microsoft Store is blocked on your laptop, so Codex won't install
Codex for Windows comes only from the Microsoft Store. On a work laptop, ask IT to allow it: the Store product ID is 9PLM9XGG6VKS.
If IT can’t do it before your session, bring a personal laptop. Don’t install copies from other sites.
EscalateTell your facilitator before the session, not on the day. We pass every policy block to OpenAI.
Codex hangs at launch: blank or frozen window
Close it fully: open Task Manager, end every Codex process, then start it again.
Update Windows and the app: Microsoft Store, Library, Get updates. Restart the laptop.
EscalateStill hangs after an update and a restart: send your facilitator your Windows version (run winver) and a screenshot. They escalate to OpenAI the same day.
Node, PowerShell and the installer
“node is not recognized”, or Codexing’s tools and nudges never run
Install Node.js LTS from nodejs.org (the .msi adds it to PATH). In a new PowerShell window, node --version should print v18 or newer; v22 is best.
Quit Codex fully and open it again. Apps only pick up a new PATH when they start.
EscalateNode prints a version but Codexing still can’t start: tell your facilitator.
“running scripts is disabled on this system” (npm or npx)
PowerShell is blocking the .ps1 wrappers. Type npm.cmd or npx.cmd instead (for example npm.cmd test, or npx.cmd -y @openai/codex plugin add codexing@id8nxt).
EscalateBypass is also blocked (IT group policy): tell your facilitator. Don’t try to switch off security software.
Commands from a Mac or Linux guide fail (rm -rf, export, &&)
Codex runs commands in PowerShell on Windows. Ask Codex to run the step for you; it writes the PowerShell version.
Optional: install PowerShell 7 (winget install Microsoft.PowerShell). Codex uses it when it’s installed, and it supports &&.
EscalateOnly if a ticket’s own instructions can’t be done in PowerShell. That’s a bug in the ticket; tell your facilitator.
Your LedgerLoop clone
“Filename too long” during git clone or npm install
Run git config --global core.longpaths true.
Clone into a short folder such as C:\src\ledgerloop, not deep inside Documents or OneDrive.
EscalateStill failing: Windows long path support needs an admin. Ask IT, and tell your facilitator.
Every line of a file shows as changed, though you only edited one
Git converted line endings on checkout. Commit or copy out any work first.
Clone again without conversion: git clone -c core.autocrlf=false <your fork URL>. The “LF will be replaced by CRLF” warning on its own is harmless.
EscalateThe visible tests fail on a fresh clone before you’ve changed anything: tell your facilitator.
EPERM, EBUSY or “operation not permitted” in node_modules
Antivirus is scanning files as they’re written. Close other editors and terminals on that folder, then run the command again.
If it keeps happening, ask IT to exclude your clone’s folder from real-time scanning.
EscalateIt fails three times in a row and IT can’t add an exclusion: tell your facilitator.
The Codexing plugin
Codexing isn’t in the @ menu after installing
Quit Codex fully (check Task Manager for leftover Codex processes) and open it again.
Still missing: in PowerShell, run codex plugin marketplace add id8nxt-hub/codexing, then codex plugin add codexing@id8nxt. No codex command? Use npx.cmd -y @openai/codex in its place. Then restart Codex.
EscalateStill not in the @ menu: tell your facilitator and send the output of those two commands.
Codexing says “Not logged in”, or its tools fail with an auth error
Type /mcp in Codex, pick codexing, then Authenticate.
Sign in to Applied AI with Codex in the browser window that opens, and approve.
EscalateThe browser never opens, or approval loops back to sign in: tell your facilitator.
No nudges from Codexing (no “That looks green” after the tests pass)
Type /hooks in Codex, review Codexing’s hooks and trust them. Codex skips plugin hooks until you do.
Trust them again after every Codexing update; a changed hook counts as new.
EscalateOptional: nudges aren’t needed to finish a ticket. Mention it if they never appear after trusting.
Usage and GitHub
Codex stops with a usage limit before your ticket is done
Your plan’s usage ran out; Codex doesn’t show a running meter as you go. Note the time and the message.
Keep to one ticket per thread, and start a fresh thread for a new ticket instead of continuing a very long one.
EscalateStraight away, if it happens before your first ticket is verified. Your facilitator tracks it and raises it with OpenAI.
We haven't confirmed where the Windows app shows remaining usage, so we don't name a menu here.
Your first cloud task can’t push a branch or open a pull request
Connect GitHub to Codex and give it access to your LedgerLoop fork, not the original repository.
On GitHub, check the Codex app’s repository access (Settings, Applications) and add your fork if it’s missing.
EscalateAccess is granted and the push still fails: tell your facilitator with the task link. They escalate to OpenAI early.
Menu names in Codex and GitHub may differ slightly from these.
What to send your facilitator
Your Windows version: run winver
The Codex app version, and whether Codex was installed from the Microsoft Store
node --version and git --version
A screenshot of the error, and the ticket number you were on
Never send passwords, tokens or your code. Screenshots of error messages are enough.