Repository navigation
Feature request: project-level codebase-memory integration #2672
Description
What problem does this solve?
Currently codebase-memory integration requires user-global files (~/AGENTS.md, global hooks, MCP config). Projects need repo-local versions that override per project. This is impossible today, the repo has no project-level AGENTS.md, hooks, or MCP config, and no mechanism exists to redirect integration files to a project-local location.
Proposed solution
Support project-level integration: detect repo-root .pi/agent/AGENTS.md, .mcp/, and hooks/ with priority over user-level files. This would let a project ship its own codebase-memory configuration that overrides the user-global defaults, enabling multi-user/multi-repo scenarios and portable, version-controlled integration setup.
Alternatives considered
Manual environment overrides per session (not portable or persistent).
Confirmations
- I searched existing issues and this is not a duplicate.
Activity
DeusData commentedon Oct 19, 2026
Thank you for explaining the team and multi-repository use case. Repository-local integration with explicit precedence over user-global settings is a clear proposal. It still needs a maintainer direction decision, including which clients and files should participate; there is no implementation commitment yet.