Augment Code vs PearAIUpdated 2026-03-16

SUMMARY

Augment Code (IDE) uses markdown configuration while PearAI (Editor) 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 CodePearAI
Config formatmarkdownmarkdown
Hierarchy support
Global config
Project config
Subdirectory scoping
File inclusion / imports
Ignore file
IDE integrationEditor
Schema / structureFree-form (Markdown)Free-form (Markdown)
Git committed
EncodingUTF-8UTF-8

FILE MAPPING

PurposeAugment CodePearAI
Project instructionsAGENTS.mdAGENTS.md
Project rules.augment/rules/*.md.pearai/rules

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

PearAI
.pearai/rules
markdown
# PearAI Project Rules

## Framework
- Next.js 15 App Router with TypeScript
- Drizzle ORM with PostgreSQL
- TailwindCSS v4 for styling

## Patterns
- Use server actions for mutations
- Colocate loading.tsx and error.tsx with page routes
- Prefer RSC; add "use client" only when needed

## Naming
- Components: PascalCase (UserProfile.tsx)
- Utilities: camelCase (formatDate.ts)
- Database tables: snake_case

## Dependencies
- Do NOT add new dependencies without asking
- Use date-fns for date manipulation
- Use zod for all validation

## Commands
- Dev: pnpm dev
- Build: pnpm build
- Lint: pnpm lint

KEY DIFFERENCES

1. Hierarchy support

Augment Code: Supported. PearAI: Not supported.

2. Global config

Augment Code: Supported. PearAI: Not supported.

3. Subdirectory scoping

Augment Code: Supported. PearAI: Not supported.

4. IDE integration

Augment Code: Supported. PearAI: Editor.

WHICH SHOULD I USE?

Recommendation

Choose based on your IDE/CLI preference. If you use Augment Code, configure AGENTS.md. If you use PearAI, configure .pearai/rules. 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)