Amp vs VoidUpdated 2026-03-16

SUMMARY

Amp (CLI) uses markdown configuration while Void (IDE) 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

FeatureAmpVoid
Config formatmarkdownmarkdown
Hierarchy support
Global config
Project config
Subdirectory scoping
File inclusion / imports
Ignore file
IDE integrationCLI
Schema / structureFree-form (Markdown)Free-form (Markdown)
Git committed
EncodingUTF-8UTF-8

FILE MAPPING

PurposeAmpVoid
Project rules.agents/checks/*.md.void/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

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. Hierarchy support

Amp: Supported. Void: Not supported.

2. Global config

Amp: Supported. Void: Not supported.

3. Subdirectory scoping

Amp: Supported. Void: Not supported.

4. IDE integration

Amp: CLI. Void: Supported.

WHICH SHOULD I USE?

Recommendation

Choose based on your IDE/CLI preference. If you use Amp, configure AGENTS.md. 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

Tool pages:
File references:
agentconfig.ing2026-03-16COMPARE(1)