codex-environmentslisted

# Codex Environments Bundled commands use `$PLUGIN_ROOT` (`$env:PLUGIN_ROOT` in PowerShell; same path suffix) for the plugin root. Set it once: the host's plugin-root variable when defined (Claude Code: `PLUGIN_ROOT="$CLAUDE_PLUGIN_ROOT"`), otherwise this plugin's absolute root path. Manages repo-local Codex app environments: usually `.codex/environments/environment.toml` plus optional project scripts called by actions. For long-running action patterns, port cleanup, detailed editing rules, verification depth, and common failure modes, read `$PLUGIN_ROOT/references/environment-actions.md`. ## Decide Whether To Create Or Edit Create or edit a Codex environment when the user wants a repeatable Codex app action — Run, Test, Preview, Open Simulator, Start Dev Server, Launch Browser — or a stable local workflow behind a Codex Run button. Prefer a repo-local environment when: - the command must run from a specific project root; - the workflow needs stable env vars, ports, simulators, devices, URLs, or log paths; - the user repeatedly pastes the same long command; - Codex Run should start an app or local service without manual shell assembly. Do not create an environment for a one-off command, destructive operation, secret setup, or workflow that still needs product decisions. Give the command directly unless repeatability is the point. If the environment file already exists, update it instead of creating a parallel file. Preserve unrelated actions and setup script content.