Amp vs Windsurf | agentconfig.ing

Amp vs WindsurfComparisonUpdated 2026-03-16

SUMMARY

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

FEATURE COMPARISON

Feature	Amp	Windsurf	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	✗	.codeiumignore
IDE integration	CLI	✓
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	Amp	Windsurf
Project rules	.agents/checks/*.md	.windsurf/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

Windsurf

.windsurf/rules/*.md

markdown

---
trigger: glob
globs: "**/*.test.ts"
---

# Testing Conventions

- Use Vitest as the test runner
- Colocate test files next to source files
- Use describe blocks organized by function/component name
- Prefer userEvent over fireEvent in component tests
- Mock external services; never hit real APIs in unit tests

KEY DIFFERENCES

1. Ignore file

Amp: Not supported. Windsurf: .codeiumignore.

2. IDE integration

Amp: CLI. Windsurf: Supported.

WHICH SHOULD I USE?

Recommendation

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