install-studio

To bootstrap Codex studio into a Git repository, run the install-studio skill, which invokes the universal bootstrap installer at ~/.codex/bin/bootstrap.py to automatically copy studio files, hooks, and agent templates into your project.

Yes, you can preview a Codex studio installation using the dry-run mode. When existing studio artifacts are detected in the repository, the skill offers a dry-run preview to inspect conflicts before making any actual filesystem changes.

The safest way to resolve file conflicts when adding a studio layer is using the skill's conservative conflict detection. It inspects the target repository, avoids overwriting critical files without explicit approval, and provides an optional force override.

Yes, you need a reachable universal bootstrap script located at ~/.codex/bin/bootstrap.py. The installer requires filesystem access to the target repository and uses this specific path for deterministic installation.

Yes, you can use the installer to refresh the studio layer in a global Codex home installation. The skill applies to both local repositories and global installations where users need to add or update the studio layer.

Codex studio installation may fail if the universal bootstrap script is unreachable at ~/.codex/bin/bootstrap.py, if filesystem access to the target repository is denied, or if unapproved critical file conflicts are detected without an explicit force override.