SUMMARY
OpenAI Codex CLI (CLI) uses markdown configuration while JetBrains AI / Junie (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 | JetBrains AI / Junie |
|---|---|---|
| Config format | markdown | markdown |
| Hierarchy support | ✓ | ✗ |
| Global config | ✓ | ✗ |
| Project config | ✓ | ✓ |
| Subdirectory scoping | ✓ | ✗ |
| File inclusion / imports | ✗ | ✗ |
| Ignore file | .codexignore | .aiignore |
| IDE integration | CLI | ✓ |
| Schema / structure | Free-form (Markdown) | Free-form (Markdown) |
| Git committed | ✓ | ✓ |
| Encoding | UTF-8 | UTF-8 |
FILE MAPPING
| Purpose | OpenAI Codex CLI | JetBrains AI / Junie |
|---|---|---|
| Settings / configuration | ~/.codex/config.toml | .noai |
| Ignore patterns | .codexignore | .aiignore |
SIDE-BY-SIDE CODE SAMPLES
# 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
```
# Kotlin Conventions
## Language Features
- Use Kotlin 2.x with coroutines for async work
- Prefer data classes for DTOs and value objects
- Use sealed classes/interfaces for domain errors
- Extension functions over utility classes
## Spring Boot
- Constructor injection (no field injection)
- Use @ConfigurationProperties over @Value
- Prefer WebFlux for reactive endpoints
- Use Spring Security with method-level security
## Testing
- JUnit 5 with Kotest assertions
- MockK for mocking (not Mockito)
- Testcontainers for integration tests
- Use @Nested for test organization
KEY DIFFERENCES
OpenAI Codex CLI: Supported. JetBrains AI / Junie: Not supported.
OpenAI Codex CLI: Supported. JetBrains AI / Junie: Not supported.
OpenAI Codex CLI: Supported. JetBrains AI / Junie: Not supported.
OpenAI Codex CLI: .codexignore. JetBrains AI / Junie: .aiignore.
OpenAI Codex CLI: CLI. JetBrains AI / Junie: Supported.
WHICH SHOULD I USE?
Choose based on your IDE/CLI preference. If you use OpenAI Codex CLI, configure AGENTS.md. If you use JetBrains AI / Junie, configure .aiassistant/rules/*.md. Many projects include config files for multiple tools so each team member can use their preferred editor.
PORTABILITY TIP
# Maintain a single source of truth:
cp AI-INSTRUCTIONS.md CLAUDE.md
cp AI-INSTRUCTIONS.md .cursorrules
cp AI-INSTRUCTIONS.md AGENTS.md