Competitive Analysis

Where This Fits

repo-context-hooks sits between two categories:

• platform-native agent primitives such as hooks, rules, or checked-in instructions
• broader memory products that optimize for long-term retrieval across sessions or systems

The project is strongest when described as repo-native continuity, not a universal memory layer.

Adjacent Approaches

Claude Code Hooks

• Focus: lifecycle primitives on a single platform
• Difference: useful foundation, but not a repo-packaged continuity workflow on its own

thedotmack/claude-mem

• Focus: session capture, compression, and retrieval
• Difference: stronger on memory archive behavior than repo-native continuity across tools

mem0ai/mem0 and OpenMemory

• Focus: long-term memory infrastructure
• Difference: stronger on retrieval and memory services than on a repo contract teams can inspect in git

Positioning Rule

Keep the public story narrow:

• repo-native continuity is the promise
• checked-in handoff state is the mechanism
• platform surfaces differ, so support claims must differ too

That is why this project should stay honest about partial platforms and should not be described as a universal memory layer.