Junie vs TraeUpdated 2026-03-16

SUMMARY

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

FEATURE COMPARISON

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

FILE MAPPING

PurposeJunieTrae
Project instructions.junie/guidelines.mdAGENTS.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

Trae
.trae/rules/*.md
markdown
---
description: React component conventions and patterns
globs: "*.tsx,*.jsx"
alwaysApply: false
---
# React Component Rules

1. Use functional components with TypeScript interfaces for props
2. Prefer server components by default — add "use client" only for interactivity
3. Colocate component tests in adjacent __tests__/ directories
4. Use named exports, not default exports
5. Extract custom hooks into hooks/ directory when reused across components

## Styling
- Use Tailwind CSS v4 utility classes
- Follow mobile-first responsive design
- Keep component-specific styles colocated

## State Management
- Use React 19 use() for async data in server components
- Prefer URL state (searchParams) over client state where possible
- Use Zustand for complex client-side state

KEY DIFFERENCES

1. Hierarchy support

Junie: Not supported. Trae: Supported.

2. Global config

Junie: Not supported. Trae: Supported.

3. IDE integration

Junie: Agent. Trae: Supported.

WHICH SHOULD I USE?

Recommendation

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

agentconfig.ing2026-03-16COMPARE(1)