OpenAI Codex CLI vs FusionUpdated 2026-03-16

SUMMARY

OpenAI Codex CLI (CLI) uses markdown configuration while Fusion (IDE) uses mdc. They differ on 7 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.

FEATURE COMPARISON

FeatureOpenAI Codex CLIFusion
Config formatmarkdownmdc
Hierarchy support
Global config
Project config
Subdirectory scoping
File inclusion / imports
Ignore file.codexignore
IDE integrationCLI
Schema / structureFree-form (Markdown)Hybrid (MDC frontmatter + Markdown)
Git committed
EncodingUTF-8UTF-8

FILE MAPPING

PurposeOpenAI Codex CLIFusion
Project instructionsAGENTS.mdAGENTS.md

SIDE-BY-SIDE CODE SAMPLES

OpenAI Codex CLI
AGENTS.md
markdown
# AGENTS.md

## Project Overview

This is a Next.js 14 e-commerce application using the App Router,
Server Components, and Drizzle ORM with PostgreSQL.

## Code Conventions

- Use TypeScript strict mode throughout
- Prefer Server Components; use "use client" only when necessary
- Name files with kebab-case: `product-card.tsx`, not `ProductCard.tsx`
- Co-locate tests: `product-card.test.tsx` next to `product-card.tsx`

## Architecture

- `app/`           — Next.js App Router pages and layouts
- `components/`    — Shared UI components
- `lib/`           — Utilities, database client, auth helpers
- `actions/`       — Server Actions for mutations

## Testing

- Use Vitest for unit tests, Playwright for E2E
- Mock database calls using `lib/test-utils.ts` helpers
- Every new component needs at least one test

## Build Commands

```bash
pnpm dev          # Start dev server
pnpm build        # Production build
pnpm test         # Run Vitest
pnpm test:e2e     # Run Playwright
pnpm lint         # ESLint check
```
Fusion
.builder/rules/*.mdc
mdc
---
description: React component conventions
globs: src/components/**/*.tsx
alwaysApply: false
---

# React Component Rules

## Structure
- Use functional components with TypeScript
- Define props interface above the component
- Export components as named exports

## Styling
- Use the project design system tokens for spacing and colors
- Prefer utility classes over custom CSS
- Keep component-specific styles colocated

## Patterns
- Wrap async data in Suspense boundaries
- Use forwardRef for reusable interactive components
- Keep components under 150 lines; extract hooks for logic

## Accessibility
- All interactive elements need aria-labels
- Use semantic HTML elements (nav, main, section)
- Ensure keyboard navigation works for custom widgets

KEY DIFFERENCES

1. Config format

OpenAI Codex CLI: markdown. Fusion: mdc.

2. Hierarchy support

OpenAI Codex CLI: Supported. Fusion: Not supported.

3. Global config

OpenAI Codex CLI: Supported. Fusion: Not supported.

4. Subdirectory scoping

OpenAI Codex CLI: Supported. Fusion: Not supported.

5. Ignore file

OpenAI Codex CLI: .codexignore. Fusion: Not supported.

6. IDE integration

OpenAI Codex CLI: CLI. Fusion: Supported.

7. Schema / structure

OpenAI Codex CLI: Free-form (Markdown). Fusion: Hybrid (MDC frontmatter + Markdown).

WHICH SHOULD I USE?

Recommendation

Choose based on your IDE/CLI preference. If you use OpenAI Codex CLI, configure AGENTS.md. If you use Fusion, configure .builder/rules/*.mdc. Many projects include config files for multiple tools so each team member can use their preferred editor.

PORTABILITY TIP

sync-instructions.sh
bash
# Maintain a single source of truth:
cp AI-INSTRUCTIONS.md CLAUDE.md
cp AI-INSTRUCTIONS.md .cursorrules
cp AI-INSTRUCTIONS.md AGENTS.md

SEE ALSO

agentconfig.ing2026-03-16COMPARE(1)