Continue vs VoidComparisonUpdated 2026-03-16
SUMMARY
Continue (IDE) uses markdown configuration while Void (IDE) 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
| Feature | Continue | Void |
|---|---|---|
| Config format | markdown | markdown |
| Hierarchy support | ✓ | ✗ |
| Global config | ✓ | ✗ |
| Project config | ✓ | ✓ |
| Subdirectory scoping | ✓ | ✗ |
| File inclusion / imports | ✗ | ✗ |
| Ignore file | ✗ | ✗ |
| IDE integration | ✓ | ✓ |
| Schema / structure | Free-form (Markdown) | Free-form (Markdown) |
| Git committed | ✓ | ✓ |
| Encoding | UTF-8 | UTF-8 |
FILE MAPPING
| Purpose | Continue | Void |
|---|---|---|
| Project rules | .continue/rules/*.md | .void/rules/*.md |
| Project rules | .continuerules | .void/rules |
SIDE-BY-SIDE CODE SAMPLES
Continue
.continue/rules/*.md
markdown
# Code Style Rules
- Use TypeScript strict mode for all files
- Prefer named exports over default exports
- Use async/await over .then() chains
- Keep functions under 30 lines
- Use descriptive variable names (no single letters except loop counters)
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
Continue: Supported. Void: Not supported.
Continue: Supported. Void: Not supported.
Continue: Supported. Void: Not supported.
WHICH SHOULD I USE?
Choose based on your IDE/CLI preference. If you use Continue, configure .continue/config.yaml. 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
SEE ALSO
agentconfig.ing2026-03-16COMPARE(1)