Junie vs OpenCodeUpdated 2026-03-16

SUMMARY

Junie (Agent) uses markdown configuration while OpenCode (CLI) uses markdown. They differ on 4 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.

FEATURE COMPARISON

FeatureJunieOpenCode
Config formatmarkdownmarkdown
Hierarchy support
Global config
Project config
Subdirectory scoping
File inclusion / imports
Ignore file
IDE integrationAgentCLI
Schema / structureFree-form (Markdown)Free-form (Markdown)
Git committed
EncodingUTF-8UTF-8

FILE MAPPING

PurposeJunieOpenCode
Project instructions.junie/guidelines.mdAGENTS.md
Project instructionsAGENTS.mdCLAUDE.md

SIDE-BY-SIDE CODE SAMPLES

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

OpenCode
AGENTS.md
markdown
# Project Instructions

## Overview
This is a TypeScript monorepo using pnpm workspaces.

## Code Style
- Use strict TypeScript with no implicit any
- Prefer functional components with hooks
- All exports should be named (no default exports)

## Architecture
- /packages/core — shared business logic
- /packages/ui — React component library
- /apps/web — Next.js frontend

## Build & Test
Run tests with: pnpm test
Build all packages: pnpm build
All PRs must have >80% coverage on changed files.

## Conventions
- Use conventional commits (feat:, fix:, chore:)
- Prefer composition over inheritance
- See @docs/api-guidelines.md for API design patterns

KEY DIFFERENCES

1. Hierarchy support

Junie: Not supported. OpenCode: Supported.

2. Global config

Junie: Not supported. OpenCode: Supported.

3. Subdirectory scoping

Junie: Not supported. OpenCode: Supported.

4. IDE integration

Junie: Agent. OpenCode: CLI.

WHICH SHOULD I USE?

Recommendation

Choose based on your IDE/CLI preference. If you use Junie, configure .junie/guidelines.md. If you use OpenCode, 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

agentconfig.ing2026-03-16COMPARE(1)