PearAI vs Void | agentconfig.ing

PearAI vs VoidComparisonUpdated 2026-03-16

SUMMARY

PearAI (Editor) uses markdown configuration while Void (IDE) uses markdown. They differ on 1 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.

FEATURE COMPARISON

Feature	PearAI	Void	Notes
Config format	markdown	markdown
Hierarchy support	✗	✗	Whether config files can be placed at multiple directory levels
Global config	✗	✗	User-wide configuration outside any project
Project config	✓	✓
Subdirectory scoping	✗	✗	Config files in subdirectories that apply only to that subtree
File inclusion / imports	✗	✗	Ability to include or reference other files from config
Ignore file	✗	✗
IDE integration	Editor	✓
Schema / structure	Free-form (Markdown)	Free-form (Markdown)	Whether config uses structured schema or free-form content
Git committed	✓	✓	Whether primary config files are intended to be version-controlled
Encoding	UTF-8	UTF-8

FILE MAPPING

Purpose	PearAI	Void
Project rules	.pearai/rules	.void/rules/*.md

SIDE-BY-SIDE CODE SAMPLES

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

Void

.void/rules/*.md

markdown

---
description: Python backend conventions
globs: "app/**/*.py"
auto_apply: true
---

# Backend Rules

## Stack
- Python 3.12 with FastAPI
- SQLAlchemy 2.0 with async sessions
- Alembic for migrations
- pytest for testing

## Conventions
- Use type hints on all function signatures
- Async endpoints by default
- Pydantic v2 models for request/response schemas
- Repository pattern for database access

## File Structure
- app/api/routes/ — API endpoints
- app/models/ — SQLAlchemy models
- app/schemas/ — Pydantic schemas
- app/services/ — Business logic

KEY DIFFERENCES

1. IDE integration

PearAI: Editor. Void: Supported.

WHICH SHOULD I USE?

Recommendation

Choose based on your IDE/CLI preference. If you use PearAI, configure .pearai/rules. If you use Void, configure .void/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