OpenAI Codex CLI vs VoidComparisonUpdated 2026-03-16
SUMMARY
OpenAI Codex CLI (CLI) uses markdown configuration while Void (IDE) uses markdown. They differ on 5 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.
FEATURE COMPARISON
| Feature | OpenAI Codex CLI | Void |
|---|---|---|
| Config format | markdown | markdown |
| Hierarchy support | ✓ | ✗ |
| Global config | ✓ | ✗ |
| Project config | ✓ | ✓ |
| Subdirectory scoping | ✓ | ✗ |
| File inclusion / imports | ✗ | ✗ |
| Ignore file | .codexignore | ✗ |
| IDE integration | CLI | ✓ |
| Schema / structure | Free-form (Markdown) | Free-form (Markdown) |
| Git committed | ✓ | ✓ |
| Encoding | UTF-8 | UTF-8 |
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
```
Void
.void/rules/*.md
markdown
---
description: Python backend conventions
globs: "app/**/*.py"
auto_apply: true
---
# Backend Rules
## Stack
- Python 3.12 with FastAPI
- SQLAlchemy 2.0 with async sessions
- Alembic for migrations
- pytest for testing
## Conventions
- Use type hints on all function signatures
- Async endpoints by default
- Pydantic v2 models for request/response schemas
- Repository pattern for database access
## File Structure
- app/api/routes/ — API endpoints
- app/models/ — SQLAlchemy models
- app/schemas/ — Pydantic schemas
- app/services/ — Business logic
KEY DIFFERENCES
OpenAI Codex CLI: Supported. Void: Not supported.
OpenAI Codex CLI: Supported. Void: Not supported.
OpenAI Codex CLI: Supported. Void: Not supported.
OpenAI Codex CLI: .codexignore. Void: Not supported.
OpenAI Codex CLI: CLI. Void: Supported.
WHICH SHOULD I USE?
Choose based on your IDE/CLI preference. If you use OpenAI Codex CLI, configure AGENTS.md. If you use Void, configure .void/rules/*.md. 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
Tool pages:
File references:
agentconfig.ing2026-03-16COMPARE(1)