Amp vs JetBrains AI / JunieComparisonUpdated 2026-03-16
SUMMARY
Amp (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 | Amp | JetBrains AI / Junie |
|---|---|---|
| Config format | markdown | markdown |
| Hierarchy support | ✓ | ✗ |
| Global config | ✓ | ✗ |
| Project config | ✓ | ✓ |
| Subdirectory scoping | ✓ | ✗ |
| File inclusion / imports | ✗ | ✗ |
| Ignore file | ✗ | .aiignore |
| IDE integration | CLI | ✓ |
| Schema / structure | Free-form (Markdown) | Free-form (Markdown) |
| Git committed | ✓ | ✓ |
| Encoding | UTF-8 | UTF-8 |
FILE MAPPING
| Purpose | Amp | JetBrains AI / Junie |
|---|---|---|
| Settings / configuration | settings.json | .noai |
| Project rules | .agents/checks/*.md | .aiassistant/rules/*.md |
SIDE-BY-SIDE CODE SAMPLES
Amp
AGENTS.md
markdown
# Agent Instructions
## Project Context
Go microservices monorepo using Bazel for builds.
## Build & Test
- Build all: bazel build //...
- Test all: bazel test //...
- Integration tests: docker compose up -d && bazel test //integration/...
- Lint: golangci-lint run ./...
## Code Conventions
- All services follow standard layout in /cmd and /internal
- Use structured logging with slog
- Error wrapping with fmt.Errorf("op: %w", err)
- See @docs/api-style-guide.md for API conventions
## Cross-Repo References
- Shared proto definitions in sourcegraph/proto
- Common Go libraries in sourcegraph/lib
## Security
- Never log sensitive data (tokens, passwords, PII)
- All external inputs must be validated
- Use parameterized queries for database access
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
Amp: Supported. JetBrains AI / Junie: Not supported.
Amp: Supported. JetBrains AI / Junie: Not supported.
Amp: Supported. JetBrains AI / Junie: Not supported.
Amp: Not supported. JetBrains AI / Junie: .aiignore.
Amp: CLI. JetBrains AI / Junie: Supported.
WHICH SHOULD I USE?
Choose based on your IDE/CLI preference. If you use Amp, 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
Tool pages:
File references:
agentconfig.ing2026-03-16COMPARE(1)