Connect Codex to the extension's workspace MCP server, then give it SFCC project skills for routes, overrides, templates, logs, and other recurring tasks. Keep the VS Code workspace open while Codex uses the server.
Connect from B2C MCP
Select Codex
Open B2C MCP → Connect AI and choose Codex. Confirm the correct workspace folders and running local server in Start.
Choose the configuration destination
Select the project .codex/config.toml or shared user ~/.codex/config.toml target in Save configuration in. The generated TOML uses a workspace-scoped entry under mcp_servers.
Create or review the entry
Use the available Hosted HTTP or stdio bridge setup shown by the panel. Select Create config for a missing target. If a configuration already exists, use Open config and Copy config to review and merge this workspace's entry.
Reload and verify
Follow the panel's reload guidance: restart Codex and inspect /mcp. The generated setup also provides codex mcp list for CLI verification. Run the safe verification prompt below, then check its timestamp in B2C MCP → Activity.
Use intellijsfcc.project.context and tell me whether this is an SFCC
workspace, all included workspace folders, and the detected cartridge
count. Do not change files or remote state.Check that the returned folders belong to this checkout. Copying or creating the configuration does not establish that Codex loaded it; the fresh request is the verification step.
Generate Codex skills
In Skills & Guidance, select Codex / Agent Skills and the destination workspace folder. Find a skill, open its details and preview, then select Add to project.
For SFRA Controller Routes & Overrides, the extension creates:
.agents/skills/sfcc-sfra-controller-routes/
SKILL.md
agents/openai.yaml
references/mcp-tool-map.md
scripts/print-mcp-workflow.mjsSKILL.md contains the workflow, agents/openai.yaml contains Codex skill metadata, and the reference maps the workflow to MCP tools. The helper prints the gates and recommended tools. Existing files are preserved.
For common MCP guidance across tasks, select Codex skill in Project instruction file and use Add to project. Its destination is .agents/skills/sfcc-lsp/SKILL.md.
Try a cartridge-aware task
Use the SFRA controller skill to inspect Product-Show. Confirm the
workspace, find every indexed implementation, and follow the cartridge
override chain. Explain which file would own a change to the response
and show its middleware order. Do not edit or deploy anything yet.After reviewing the explanation, ask for the concrete change and a diagnostics check. Check Activity to see the tool calls behind the answer.
Troubleshooting
| Symptom | Next step |
|---|---|
| Codex cannot see the server | Confirm the workspace server is running, restart Codex, and inspect /mcp or codex mcp list. |
| The server reports a different checkout | Use this workspace's generated server entry and verify its returned folders. |
| Setup shows Stale — generate again | Copy the current configuration, review the saved entry, and run a new verification request. |
| Tools are missing after an access change | Review Tools & Access, then reconnect or restart the Codex session to refresh its tool list. |
| A generated skill keeps old content | Open the installed file and compare the preview; generation preserves existing files. |
