Reference

Configuration

REAP projects are configured through .reap/config.yml. This file is created during reap init and controls project settings, strict mode, and agent integration.

Config File Structure

yaml
# .reap/config.yml
project: my-project           # Project name
language: english              # Artifact/prompt language
autoSubagent: true             # Auto-delegate to subagent in evolve
strictEdit: false               # Restrict code changes to REAP lifecycle
strictMerge: false              # Restrict direct git pull/push/merge
agentClient: claude-code       # AI agent client
# cruiseCount: 1/5             # Present = cruise mode (current/total)

Fields

FieldDescription
projectProject name (set during init)
languageLanguage for artifacts and user interactions (e.g. korean, english, japanese). Default: english
autoSubagentAuto-delegate /reap.evolve to a subagent via Agent tool (default: true)
strictEditRestrict code changes to REAP lifecycle (default: false). See Strict Mode below.
strictMergeRestrict direct git pull/push/merge — use REAP commands instead (default: false). See Strict Mode below.
agentClientAI agent client (claude-code | opencode | codex). Controls adapter layer — slash command location, manifest file (CLAUDE.md vs AGENTS.md), plugin/hook strategy. Default: claude-code. Codex is currently unsupported.
cruiseCountWhen present, enables cruise mode. Format: current/total (e.g. 1/5). Removed automatically after cruise completes
evaluatorOpt-in independent reviewer. When true, launches reap-evaluate as an advisor during validation and fitness phases. High-severity concerns abort cruise mode. Default: false.

Strict Mode

Strict mode controls what the AI agent is allowed to do. Two independent settings:

yaml
strictEdit: true    # Restrict code changes to REAP lifecycle
strictMerge: true   # Restrict raw git pull/push/merge

strictEdit — Code Modification Control

When enabled, the AI agent cannot modify code outside the REAP workflow.

ContextBehavior
No active generation / non-implementation stageCode modifications are fully blocked
Implementation stageOnly modifications within the scope of 02-planning.md are allowed
Escape hatchUser explicitly requests "override" or "bypass strict" — bypass applies to that specific action only, then strict mode re-engages

strictMerge — Git Command Control

When enabled, direct git pull, git push, and git merge commands are restricted. The agent will guide users to use REAP slash commands instead (/reap.pull, /reap.push, /reap.merge).

Both are disabled by default. Reading files, analyzing code, and answering questions are always allowed regardless of strict mode.

Entry Modes

ModeUse case
greenfieldNew project starting from scratch
adoptionApplying REAP to an existing codebase
migrationMigrating from an existing system to a new architecture