Use the StoreFront CLI with Codex
Codex CLI is OpenAI's coding agent for the terminal. It reads project skills from the workspace's .agents/skills/ folder. Status: Supported.
Prerequisites
- Node.js 24 or newer, with npm (
node -v). - Codex CLI installed and signed in.
- An UltraCart account whose user has StoreFront access.
Install the CLI and the skill
npm install -g @ultracart/storefront-cli@beta
uc-storefront --version
uc-storefront init my-storefront --target codex
cd my-storefront
uc-storefront skills status
When Codex runs init for you, its shell cannot answer prompts. Have it add --no-input:
uc-storefront init my-storefront --target codex --no-input
Confirm Codex sees the skill
The skill lands in my-storefront/.agents/skills/build-ultracart-storefronts/. Google Antigravity, Gemini CLI and OpenClaw read the same folder, so one copy serves them all.
- Run
uc-storefront skills status. It should list the.agents/skillscopy with no missing or edited files. - Start Codex from inside the workspace folder (the one with
ultracart.json). - Ask it to list its skills and look for
build-ultracart-storefronts.
If it is missing, check that Codex started in the workspace folder, then see The agent does not list the skill.
Sign in
On a desktop, the sign-in goes into the operating system's keychain and no key is needed. You can run uc-storefront auth login --profile my-store yourself in a terminal, or let Codex sign in with the two-step flow, because its command tool shows output only when a command exits:
uc-storefront profile create my-store
uc-storefront auth login --profile my-store --no-wait
uc-storefront auth login --profile my-store --continue --wait
uc-storefront profile bind my-store
uc-storefront sf storefronts
auth login --no-waitprints a URL and a code and exits at once. Codex relays both to you.- You open the URL in your own browser, check the code, and approve.
auth login --continue --waitwaits up to 45 seconds. It exits0once you have approved and3while the sign-in is still waiting, so Codex runs it again until it exits0.
Running Codex in a container or CI
Without a keychain, the CLI keeps the sign-in in an encrypted file. Put the credential key in the container's secrets and keep the configuration folder on a volume, as described in Docker, Fly.io and CI runners. To bake the skill into an image, use uc-storefront init /workspace/my-storefront --target codex --no-input at build time; see Bake the CLI and skill into the image.
Caveats
skills remove --target codexkeeps the.agents/skillscopy whilegemini(used for Antigravity and Gemini CLI) is still a target, because they share it.- Updating the CLI does not update the skill. Run
uc-storefront skills installin each workspace after an upgrade. - Never paste a password, API key, token or credential key into the Codex chat.
Next steps
- Connect your store: profiles, binding and how long a sign-in lasts
- Safety and human approval: read before the first live change
- What it can do: the areas Codex can work on with the skill