Skip to main content
AEP is agent-agnostic. Any agent that reads files and follows instructions can use AEP — there is no runtime, no server, and no SDK required. Packs are plain JSON stored inside your repo, and the agent loads them before starting a task.

​
Agent-aware install targets

In v1.0-exp, AEP installs into the directory that matches your active agent rather than a generic .agent/ folder. Each agent has its own preferred location:
AgentAEP directory
Claude.claude/aep/
Codex.codex/aep/
Gemini.gemini/aep/
OpenCode.opencode/aep/
Cursor.cursor/aep/
Fallback (v0.1).agent/aep/
Do not create .agent/ for new installs. The fallback path is only retained for backwards compatibility with v0.1 repos. Always prefer the agent-specific directory when initializing AEP in a fresh repo.

​
How the agent chooses a directory

When creating or updating AEP files, the agent resolves the install target in this order:
  1. Directory explicitly referenced by the user — if you tell the agent to use .claude/aep/, it will.
  2. Directory that already contains aep/ files — the agent prefers an existing AEP installation over creating a new one.
  3. Directory matching the currently active agent — detected automatically from the agent environment.
  4. Ask the user — if the situation is still ambiguous after the steps above.

​
Instruction file updates

After creating an AEP pack or initializing AEP in a repo, you should update the relevant agent instruction files so future sessions know to load AEP by default. Update or create these files when present:
  • AGENTS.md
  • CLAUDE.md (for Claude sessions)
  • Codex instructions file
  • Gemini instructions file
  • OpenCode agent config file
  • Cursor project rules file
The minimum instruction to add (adapt the path to the active agent directory): 
Before starting tasks, load relevant AEP packs from <agent-dir>/aep/.
Apply task packs first, then project, then user packs.
After successful tasks, save new or updated AEP packs.

​
Setup by agent

AEP installs into .claude/aep/. Claude reads CLAUDE.md at session start, making it the right place to add AEP loading instructions.Directory structure:
.claude/
  aep/
    index.json
    project.aep.json
    user.aep.json
    tasks/
CLAUDE.md
Minimum CLAUDE.md addition:
Before starting tasks, load relevant AEP packs from .claude/aep/.
Apply task packs first, then project, then user packs.
After successful tasks, save new or updated AEP packs.
Claude Code can also use future MCP servers that expose structured AEP operations understanding strength, metrics, and history.

Setting up a repo

Wire AEP into any repository in three steps

Matching and scoring

How agents rank packs for every task

Schema reference

Full field definitions for v1.0-exp packs

Compatibility

Backwards compatibility with v0.1 packs

Build docs developers (and LLMs) love

Get started for freeTalk to us