Amp vs Cursor | agentconfig.ing

Amp vs CursorComparisonUpdated 2026-03-16

SUMMARY

Amp (CLI) uses markdown configuration while Cursor (IDE) uses mdc. They differ on 4 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.

FEATURE COMPARISON

Feature	Amp	Cursor	Notes
Config format	markdown	mdc
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	✗	.cursorignore
IDE integration	CLI	✓
Schema / structure	Free-form (Markdown)	Hybrid (MDC frontmatter + 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	Amp	Cursor
Project rules	.agents/checks/*.md	.cursor/rules/*.mdc

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

Cursor

.cursor/rules/*.mdc

mdc

---
description: React component conventions and patterns
globs: "*.tsx"
alwaysApply: false
---

# React Component Rules

- Use functional components with explicit return types
- Define props interface directly above the component
- Export components as named exports, never default
- Use Tailwind CSS utility classes exclusively

KEY DIFFERENCES

1. Config format

Amp: markdown. Cursor: mdc.

2. Ignore file

Amp: Not supported. Cursor: .cursorignore.

3. IDE integration

Amp: CLI. Cursor: Supported.

4. Schema / structure

Amp: Free-form (Markdown). Cursor: Hybrid (MDC frontmatter + Markdown).

WHICH SHOULD I USE?

Recommendation

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