Catalog Systems File-backed / editor paradigms Aider CONVENTIONS.md / .aider.conf.yml

Aider CONVENTIONS.md / .aider.conf.yml

https://aider.chat/docs/usage/conventions.html

CONVENTIONS.md (any name, loaded via --read or read: in config); .aider.conf.yml (home / git-root / cwd, last wins); .aiderignore (gitignore-syntax).

Active · Verified 2026-10-22 · fresh as of 2026-10-22 · 29 cited facts, 0 with a third-party source · Suggest a correction

At a glance

Type
Multi-file convention pattern vendor fix
Tier
T2
Section
File-backed / editor paradigms
Created
2023-06 (Aider launched June 2023 by Paul Gauthier; CONVENTIONS.md pattern included from early versions) vendor fix
Latest release
not applicable — not OSS fix
License
not applicable — not OSS fix
GitHub
not applicable — no GitHub repo fix
Pricing
not applicable — not commercial fix
Funding
not applicable — not commercial fix
Freshness
2026-10-22 fix
Layer
agent-infra repo fix
Licensing
commercial vendor fix
Deployment locus
local vendor fix
Platform vs product
product vendor fix

Memory taxonomy

storage
file
retrieval
injection
persistence
cross-session
update
overwrite
unit
document
governance
user-controllable
conflict
manual

When to use

Optimised for: simplicity / git-versioned / human-readable

Anti-fit: not for non-coding / non-IDE use cases

Pros & cons

Pros

Plain-text + git-versioned conventions file — the most CLAUDE.md-like memory pattern outside Anthropic's tools.

Cons

Aider-only; manual curation required; no semantic recall.

Claims & capabilities

Mature, widely used.

Technical surface

API surface
not applicable — config
Backend storage
file
Deployment
not applicable — not a deployable product
Embedding model
not applicable — config file
Multi-tenancy
not applicable — local
MCP
not applicable — file-as-memory paradigm (no API surface)
A2A
not applicable — file-as-memory paradigm
OpenTelemetry
not applicable — file-as-memory paradigm

Alternatives to Aider CONVENTIONS.md / .aider.conf.yml → live options ranked by shared design, licence, hosting and MCP support

Similar systems

Other file-backed / editor paradigms in the catalog, ranked by inbound references.

  • Cline .clinerules T2

    Markdown rule files in a workspace .clinerules/ (or .cline/rules/) directory plus global rules in ~/Documents/Cline/Rules; workspace wins on conflict. Per-rule toggles, conditional rules via YAML 'paths' globs, and AGENTS.md / .cursorrules / .windsurfrules are also read.

  • OpenClaw memory T3

    Memory system of the viral OpenClaw personal agent: plain Markdown files (USER.md, MEMORY.md, daily memory/YYYY-MM-DD.md notes, DREAMS.md) with memory_search/memory_get tools, automatic pre-compaction flush and a 'dreaming' sweep that distils daily notes into long-term memory; pluggable engines (LanceDB, Honcho, wiki). spawned an ecosystem of memory plugins (memory-lancedb-pro, gbrain, MemClaw)

  • AGENTS.md T1

    Open Markdown 'README for agents' at repo root; nested files in subprojects take precedence (closest wins). Holds build/test commands, conventions and PR rules. Stewarded by the Agentic AI Foundation (Linux Foundation); supported by Codex, Jules, Cursor, Copilot, Gemini CLI, Devin/Windsurf and others.

  • Basic Memory T3

    Local-first MCP memory where each memory is a Markdown note with observations and wikilink relations that form a traversable knowledge graph, indexed with SQLite (optional Postgres vectors), plus an optional hosted cloud. widely used MCP memory server with a paid cloud tier

  • CLAUDE.md T1

    CLAUDE.md files (managed, user, project, local scopes) concatenated into context at session start, with @imports and path-scoped .claude/rules/; complemented by Claude-written auto memory (MEMORY.md index). Project-root file re-injected after /compact.

  • Cline Memory Bank T2

    memory-bank/ directory of Markdown: projectBrief.md , productContext.md , activeContext.md , systemPatterns.md , techContext.md , progress.md . Loaded in full at start of every task. Compensates for context-window reset between sessions.

Sources (28 cited facts, 0 third-party)

Each fact links to the page it came from; the badge says who published it (how to read sources).