OpenAI Codex CLI vs LovableComparisonUpdated 2026-03-16
SUMMARY
OpenAI Codex CLI (CLI) uses markdown configuration while Lovable (Platform) 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 | Lovable |
|---|---|---|
| Config format | markdown | markdown |
| Hierarchy support | ✓ | ✗ |
| Global config | ✓ | ✗ |
| Project config | ✓ | ✓ |
| Subdirectory scoping | ✓ | ✗ |
| File inclusion / imports | ✗ | ✗ |
| Ignore file | .codexignore | ✗ |
| IDE integration | CLI | Platform |
| Schema / structure | Free-form (Markdown) | Free-form (Markdown) |
| Git committed | ✓ | ✓ |
| Encoding | UTF-8 | UTF-8 |
FILE MAPPING
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
```
Lovable
AGENTS.md
markdown
# Project Instructions
## Stack
- React 19 with TypeScript
- Supabase for backend (auth, database, storage)
- TailwindCSS v4 + shadcn/ui components
- Vite for building
## Architecture
- Feature-based folder structure
- Each feature owns its components, hooks, and types
- Shared components in src/components/ui/
- All API calls go through src/lib/supabase.ts
## Conventions
- Use shadcn/ui components before creating custom ones
- Mobile-first responsive design
- Use Supabase RLS policies for authorization
- Prefer server-side filtering over client-side
## Brand
- Primary color: #6366F1 (indigo)
- Font: Inter for body, Cal Sans for headings
- Rounded corners (radius-lg) on all cards
KEY DIFFERENCES
OpenAI Codex CLI: Supported. Lovable: Not supported.
OpenAI Codex CLI: Supported. Lovable: Not supported.
OpenAI Codex CLI: Supported. Lovable: Not supported.
OpenAI Codex CLI: .codexignore. Lovable: Not supported.
OpenAI Codex CLI: CLI. Lovable: Platform.
WHICH SHOULD I USE?
Choose based on your IDE/CLI preference. If you use OpenAI Codex CLI, configure AGENTS.md. If you use Lovable, configure AGENTS.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:
agentconfig.ing2026-03-16COMPARE(1)