Augment Code vs JetBrains AI / JunieUpdated 2026-03-16

SUMMARY

Augment Code (IDE) uses markdown configuration while JetBrains AI / Junie (IDE) 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

FeatureAugment CodeJetBrains AI / Junie
Config formatmarkdownmarkdown
Hierarchy support
Global config
Project config
Subdirectory scoping
File inclusion / imports
Ignore file.aiignore
IDE integration
Schema / structureFree-form (Markdown)Free-form (Markdown)
Git committed
EncodingUTF-8UTF-8

FILE MAPPING

PurposeAugment CodeJetBrains AI / Junie
Project rules.augment/rules/*.md.aiassistant/rules/*.md

SIDE-BY-SIDE CODE SAMPLES

Augment Code
AGENTS.md
markdown
# Project Rules

## Architecture
- Clean architecture with domain, application, and infrastructure layers
- Domain models must not import from infrastructure
- Use dependency injection for all services

## Code Style
- TypeScript strict mode, no implicit any
- Use Result<T, E> for error handling in domain layer
- Prefer composition over inheritance
- Maximum 3 parameters per function; use options objects for more

## Testing
- Unit tests for domain logic (no mocking frameworks)
- Integration tests for API endpoints
- E2E tests for critical user journeys with Playwright

## Dependencies
- Do not add new dependencies without discussing first
- Prefer standard library over third-party for simple tasks

JetBrains AI / Junie
.aiassistant/rules/*.md
markdown
# 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

1. Hierarchy support

Augment Code: Supported. JetBrains AI / Junie: Not supported.

2. Global config

Augment Code: Supported. JetBrains AI / Junie: Not supported.

3. Subdirectory scoping

Augment Code: Supported. JetBrains AI / Junie: Not supported.

4. Ignore file

Augment Code: Not supported. JetBrains AI / Junie: .aiignore.

WHICH SHOULD I USE?

Recommendation

Choose based on your IDE/CLI preference. If you use Augment Code, 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

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)