GitHub Copilot vs JunieUpdated 2026-03-16

SUMMARY

GitHub Copilot (IDE) uses markdown configuration while Junie (Agent) 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

FeatureGitHub CopilotJunie
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

PurposeGitHub CopilotJunie
Project instructions.github/copilot-instructions.md.junie/guidelines.md
Project instructions.github/instructions/*.instructions.mdAGENTS.md

SIDE-BY-SIDE CODE SAMPLES

GitHub Copilot
.github/copilot-instructions.md
markdown
# Copilot Instructions

## Code Style
- Use TypeScript strict mode for all new files
- Prefer functional components with hooks over class components
- Use named exports, not default exports

## Libraries
- Use date-fns for date manipulation (not moment.js)
- Use zod for runtime validation
- Prefer fetch over axios for HTTP requests

## Testing
- Write tests using Vitest
- Use Testing Library for component tests
- Aim for integration tests over unit tests

## Conventions
- Use camelCase for variables, PascalCase for components
- Prefix interfaces with I (e.g., IUserProps)
- Keep files under 300 lines; extract if longer

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

1. Hierarchy support

GitHub Copilot: Supported. Junie: Not supported.

2. Subdirectory scoping

GitHub Copilot: Supported. Junie: Not supported.

3. IDE integration

GitHub Copilot: Supported. Junie: Agent.

WHICH SHOULD I USE?

Recommendation

Choose based on your IDE/CLI preference. If you use GitHub Copilot, configure .github/copilot-instructions.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

agentconfig.ing2026-03-16COMPARE(1)