Claude Code vs JunieComparisonUpdated 2026-03-16
SUMMARY
Claude Code (CLI) uses markdown configuration while Junie (Agent) uses markdown. They differ on 6 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.
FEATURE COMPARISON
| Feature | Claude Code | Junie |
|---|---|---|
| Config format | markdown | markdown |
| Hierarchy support | ✓ | ✗ |
| Global config | ✓ | ✗ |
| Project config | ✓ | ✓ |
| Subdirectory scoping | ✓ | ✗ |
| File inclusion / imports | ✓ | ✗ |
| Ignore file | .claudeignore | ✗ |
| IDE integration | CLI | Agent |
| Schema / structure | Free-form (Markdown) | Free-form (Markdown) |
| Git committed | ✓ | ✓ |
| Encoding | UTF-8 | UTF-8 |
FILE MAPPING
| Purpose | Claude Code | Junie |
|---|---|---|
| Project instructions | CLAUDE.md | .junie/guidelines.md |
SIDE-BY-SIDE CODE SAMPLES
Claude Code
CLAUDE.md
markdown
# Project Name
> TypeScript + React monorepo. Deployed on Vercel.
## Code Style
- TypeScript strict mode — no `any`, no `ts-ignore`
- Named exports only (no default exports)
- Prefer functional patterns: map/filter/reduce over for-loops
- Error handling: use Result<T, E> from `src/lib/result.ts`
## Architecture
- `src/routes/` — Route handlers (thin layer, delegates to services)
- `src/services/` — Business logic, one file per domain entity
- `src/db/` — Drizzle ORM schema and query helpers
- `src/lib/` — Shared utilities (logger, result type, validation)
## Commands
```bash
pnpm install # Install dependencies
pnpm dev # Start dev server (port 3000)
pnpm test # Run Vitest suite
pnpm test:e2e # Run Playwright tests
pnpm lint # ESLint + Prettier check
pnpm db:migrate # Run pending Drizzle migrations
```
## Git Conventions
- Conventional Commits: `feat:`, `fix:`, `chore:`, `docs:`
- Branch naming: `feat/short-description`, `fix/issue-number`
- Squash merge to main; delete branches after merge
## Notes
- The `src/legacy/` directory is being migrated. Do not add new code there.
- All dates are stored as UTC. Never use local time.
@docs/api-patterns.md
@docs/database-conventions.md
Junie
.junie/guidelines.md
markdown
# Project Guidelines
## Language & Framework
- Kotlin with Spring Boot 3.x
- Gradle with Kotlin DSL
- JDK 21 with virtual threads
## Architecture
- Hexagonal architecture (ports & adapters)
- Domain events for cross-module communication
- CQRS for read-heavy endpoints
## Code Standards
- Follow Kotlin coding conventions
- Use data classes for DTOs
- Prefer sealed classes for domain errors
- Extension functions over utility classes
## Testing
- JUnit 5 with Kotest assertions
- Testcontainers for integration tests
- MockK for mocking (not Mockito)
## Build & Run
- Build: ./gradlew build
- Test: ./gradlew test
- Run: ./gradlew bootRun
KEY DIFFERENCES
Claude Code: Supported. Junie: Not supported.
Claude Code: Supported. Junie: Not supported.
Claude Code: Supported. Junie: Not supported.
Claude Code: Supported. Junie: Not supported.
Claude Code: .claudeignore. Junie: Not supported.
Claude Code: CLI. Junie: Agent.
WHICH SHOULD I USE?
Choose based on your IDE/CLI preference. If you use Claude Code, configure CLAUDE.md. If you use Junie, configure .junie/guidelines.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)