syncing-codex-harness

Name: syncing-codex-harness
Availability: InStock
Author: greenhead

Generate .agents and .codex artifacts from Claude Code harnesses.

4|Updated Dec 21, 2025

Search Tags:#automation #codex #mcp #sync #claude-code #harness

Ready to run

npx skills add https://github.com/greenheadHQ/nixos-config --skill syncing-codex-harness

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: syncing-codex-harness
Source: https://github.com/greenheadHQ/nixos-config/tree/main/modules/shared/programs/claude/files/skills/syncing-codex-harness
Command: npx skills add https://github.com/greenheadHQ/nixos-config --skill syncing-codex-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The synchronization of Claude Code harness components to Codex CLI, enabling a consistent projection of skills, agents, and MCP configurations into a Codex-ready structure.

Core Features & Use Cases

Projects CLAUDE code harnesses into a Codex-compatible layout with .agents and .codex directories.
Supports local and plugin-provided skills, AGENTS.md/AGENTS.override.md generation, and MCP config integration.
Ensures idempotent syncing with safe merging of user settings while updating only necessary MCP sections.

Quick Start

Run the harness synchronization script to perform a full sync.

Frequently Asked Questions about syncing-codex-harness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I sync Claude Code harness configurations to Codex CLI?▼

To sync Claude Code harness configurations to Codex CLI, run the harness synchronization script. It performs a full, idempotent projection that generates .agents and .codex artifacts while aligning plugin and local skills.

Does syncing MCP configurations to Codex CLI preserve user customizations?▼

Yes, syncing MCP configurations to Codex CLI preserves user customizations. The process applies safe merging across project-scope and user-scope configurations, updating only the necessary MCP sections without overwriting your existing settings.

What is the best way to generate Codex-compatible .agents and .codex directories from Claude Code?▼

The best way to generate Codex-compatible .agents and .codex directories is using a full harness synchronization script. It reads SKILL.md frontmatter, discovers references, and executes safety checks to project your Claude Code setup into a Codex-ready structure.

Can I use plugin-installed MCPs when projecting my harness to a Codex-compatible structure?▼

Yes, you can use plugin-installed MCPs when projecting your harness to a Codex-compatible structure. The synchronization process explicitly supports plugin-provided skills and integrates their MCP configurations alongside local setups.

Why does the Codex CLI sync process need to read SKILL.md frontmatter?▼

The Codex CLI sync process reads SKILL.md frontmatter to extract the accurate name and description of your skills. This metadata ensures the projected .agents and AGENTS.md artifacts correctly represent your harness components in the Codex environment.

Is the Claude Code to Codex CLI projection idempotent across multiple runs?▼

Yes, the Claude Code to Codex CLI projection is idempotent. Running the synchronization script multiple times yields the same result without duplicating artifacts, because it executes safety checks and only updates necessary MCP sections during the merge.