Primary-runtime presentation helpers resolve node_modules from cwd when HOME is unset on Windows

Open 💬 0 comments Opened Aug 4, 2026 by jeonking80

Environment

  • Windows 11
  • codex-cli 0.144.1
  • primary-runtime plugin cache version 26.801.11242
  • HOME is unset; USERPROFILE is C:\Users\jeonk

Problem

The presentations runtime helpers resolve the primary-runtime node_modules root with:

process.env.HOME || process.cwd()

Affected managed files include:

  • presentations/.../container_tools/artifact_tool_utils.mjs
  • presentations/.../container_tools/rasterize_svg.mjs

On Windows, HOME may be unset even though USERPROFILE and os.homedir() are valid. The fallback then points under the current working directory instead of the user runtime cache, so runtime packages such as sharp may not resolve.

The same primary-runtime bundle already uses the safer pattern HOME ?? USERPROFILE ?? os.homedir() in the template-creator code.

Expected

Resolve the home directory with a Windows-aware source such as os.homedir() / USERPROFILE, or use the host runtime dependency resolver before a filesystem fallback. Do not use the current working directory as the implicit home.

Scope and evidence

This was confirmed by source inspection in the managed 26.801.11242 runtime cache. The managed cache was not modified because no public canonical checkout for this package was available.

View original on GitHub ↗