Prerequisites for Using Codex CLI with the AI Website Cloner Template

You need Node.js 24 or newer and a working Codex CLI installation on your PATH to run the AI Website Cloner Template with OpenAI's Codex agent.

The JCodesMore/ai-website-cloner-template repository is designed to work with multiple AI coding agents, including Codex CLI. Understanding the prerequisites for using Codex CLI with this template ensures you can execute the /clone-website skill without environment errors.

System Requirements

The template requires Node.js 24 or newer to execute its build, lint, and type-checking scripts. According to the repository's README.md at lines 74-78, this specific Node version is mandatory. Attempting to run the project with earlier versions will cause dependency installation failures or runtime errors during script execution.

Codex CLI Installation

You must have a working Codex CLI installation reachable on your $PATH. The CLI enables the agent to start and invoke the /clone-website skill. The README.md lines 60-62 confirm Codex CLI as a supported agent in the Supported Platforms table.

Install the CLI globally using npm:

npm i -g @openai/codex-cli

Verify the installation by ensuring the codex command is available in your terminal before proceeding.

Project Setup Steps

Follow these steps to prepare the template for Codex CLI execution:

1. Clone your own copy of the template (do not clone the original repository directly):

git clone https://github.com/<YOUR-USERNAME>/<YOUR-REPO>.git
cd <YOUR-REPO>

2. Install dependencies using Node.js 24+:

npm install

3. Install Codex CLI if you haven't already:

npm i -g @openai/codex-cli

4. Start the Codex agent with Chrome integration:

codex --chrome

5. Execute the cloning skill against your target:

/clone-website https://example.com

How the Template Recognizes Codex CLI

The template automatically detects Codex CLI support through several key files:

• AGENTS.md: Serves as the central source-of-truth for supported agents, marking Codex CLI as compatible.
• scripts/sync-skills.mjs: Regenerates the /clone-website skill for all platforms, ensuring Codex CLI receives the latest skill definition.
• .github/skills/clone-website/SKILL.md: Contains the actual skill definition that Codex CLI executes when you run the /clone-website command.

No additional environment variables or secret keys are required for the template itself.

Summary

• Node.js 24+ is mandatory for running the template's build and validation scripts according to README.md lines 74-78.
• Codex CLI must be installed globally and available on your $PATH to invoke the /clone-website skill.
• The template recognizes Codex CLI as a supported platform via AGENTS.md and README.md lines 60-62.
• No extra configuration variables or API keys are needed within the template repository itself.

Frequently Asked Questions

Do I need API keys to use the template with Codex CLI?

No. The template itself does not require additional environment variables or secret keys. You only need Node.js 24+ and a working Codex CLI installation. Your OpenAI API keys are typically configured within the Codex CLI tool itself, not in the template configuration files.

Can I use an older version of Node.js with this template?

No. The build, lint, and type-checking scripts specifically require Node.js 24 or newer as documented in README.md at lines 74-78. Using older versions will result in dependency installation failures or runtime errors during script execution.

Where is the /clone-website command defined?

The command is defined in .github/skills/clone-website/SKILL.md. The scripts/sync-skills.mjs script synchronizes this definition across all supported agents, including Codex CLI, ensuring the skill is automatically available when you start the agent.

Why should I clone my own copy instead of the original repository?

You should clone your own copy to https://github.com/<YOUR-USERNAME>/<YOUR-REPO>.git rather than the original JCodesMore/ai-website-cloner-template repository to ensure you have write permissions and can customize the configuration for your specific use case without affecting the upstream template.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}