migrate-to-codex

Migrates Claude Code instructions, skills, agents, hooks, and MCP config to Codex.

779|80|Updated Jun 20, 2025
One-click install
npx skills add https://github.com/Haohao-end/openagent --skill migrate-to-codex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-to-codex
Source: https://github.com/Haohao-end/openagent/tree/main/api/internal/core/skills/catalog/migrate-to-codex
Command: npx skills add https://github.com/Haohao-end/openagent --skill migrate-to-codex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Migrate an existing Claude/agent configuration into Codex project/global conventions without losing important instruction, skill, agent, hook, or MCP setup—while clearly marking parts that require manual review.

Core Features & Use Cases

  • Scans instruction files and configuration roots: Detects supported instruction sources (e.g., AGENTS.md/CLAUDE.md) and associated Claude Code artifacts.
  • Converts skills, commands, and supported resources: Rewrites or symlinks instruction content, converts Claude skills/commands into Codex .agents/skills/SKILL.md artifacts, and copies required SKILL entry points.
  • Migrates MCP/server and Codex config: Generates .codex/config.toml from Claude MCP/settings (including enabled/disabled server mapping).
  • Migrates subagents to Codex custom agents: Converts .claude/agents into .codex/agents/*.toml with preserved intent and manual-review caveats.
  • Plans, validates, and reports: Supports scan-only, plan, dry-run, doctor/readiness reporting, and target validation with collision/orphan reporting.

Quick Start

Run migrate-to-codex with your source root and Codex target root, selecting the components you want to migrate and using plan and dry-run first to review the staged changes.

Frequently Asked Questions about migrate-to-codex

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

FAQPage Schema
How do I migrate Claude Code instructions and MCP configuration to Codex conventions?

Migrating Claude Code instructions and MCP configuration to Codex involves scanning source roots like .claude scopes and rewriting or symlinking them into Codex-compatible .codex and .agents artifacts. This preserves runtime intent for skills, hooks, and servers.

Can I convert Claude subagents into Codex custom agents without losing their original intent?

Converting Claude subagents into Codex custom agents rewrites .claude/agents into .codex/agents/*.toml files. This preserves the original operational intent while clearly marking any generated caveats that require manual review.

Does migrating agent setup to Codex support a dry-run mode to preview changes before writing?

Migrating agent setup to Codex supports scan-only, plan, and dry-run modes. These modes generate planned artifacts and collision or orphan reports without performing actual writes to the target Codex directory.

What is the best way to convert Claude skills and commands into Codex .agents artifacts?

Converting Claude skills and commands into Codex .agents artifacts involves rewriting instruction content into SKILL.md files. The process copies required SKILL entry points to maintain functional parity within the .agents/skills directory.

How do I validate a Codex migration and check for orphaned configuration files?

Validating a Codex migration uses built-in doctor and readiness reporting features to scan the target directory. This process identifies collision or orphan reports, ensuring the migrated .codex artifacts match expected runtime structures.