Problem
Currently AGENTS.md is only loaded from the current working directory. This creates significant friction for developers who maintain many projects in parallel.
My Pain Points
-
Multiple projects with shared rules: I routinely work with 10+ different projects across unrelated directories. Most of them share the same baseline conventions (coding style, commit message format, security guidelines, etc.).
-
Duplicate-and-sync hell: Every new project needs a manual copy of the same AGENTS.md. When our team updates a convention, I have to remember and sync every single project's file. This is tedious and error-prone — some repos inevitably get outdated rules.
-
Skills are not a replacement: Skills are loaded on-demand, so they cannot guarantee baseline rules are always followed. I need certain rules (like "always use 4-space indentation" or "never commit secrets") to be injected at session start, not left to the AI's discretion.
Proposed Solution
Load a global AGENTS.md from ~/.kimi/AGENTS.md (or ~/.kimi/agents.md) before the project-level one. The project-level file can then override or extend the global rules.
Example precedence:
~/.kimi/AGENTS.md — global baseline (optional, opt-in)<project-root>/AGENTS.md — project-specific overrides
This is the same pattern used by .gitconfig (~/.gitconfig + repo-level overrides) and many other tools.
Why This Matters
In real-world enterprise/team environments, developers often work with many repos that should all follow the same standards. A global config acts as a "default floor" without forcing per-repo duplication.
Opt-in Design
This is purely optional. Users who don't need it simply don't create ~/.kimi/AGENTS.md. Zero impact on existing workflows. Those who need it get a much better multi-project experience.
Related
Please reconsider this feature. The "more compelling reasons" asked for in #439 is right here: multi-project maintenance is a daily pain point that Skills simply cannot solve.
Problem
Currently
AGENTS.mdis only loaded from the current working directory. This creates significant friction for developers who maintain many projects in parallel.My Pain Points
Multiple projects with shared rules: I routinely work with 10+ different projects across unrelated directories. Most of them share the same baseline conventions (coding style, commit message format, security guidelines, etc.).
Duplicate-and-sync hell: Every new project needs a manual copy of the same
AGENTS.md. When our team updates a convention, I have to remember and sync every single project's file. This is tedious and error-prone — some repos inevitably get outdated rules.Skills are not a replacement: Skills are loaded on-demand, so they cannot guarantee baseline rules are always followed. I need certain rules (like "always use 4-space indentation" or "never commit secrets") to be injected at session start, not left to the AI's discretion.
Proposed Solution
Load a global
AGENTS.mdfrom~/.kimi/AGENTS.md(or~/.kimi/agents.md) before the project-level one. The project-level file can then override or extend the global rules.Example precedence:
~/.kimi/AGENTS.md— global baseline (optional, opt-in)<project-root>/AGENTS.md— project-specific overridesThis is the same pattern used by
.gitconfig(~/.gitconfig+ repo-level overrides) and many other tools.Why This Matters
In real-world enterprise/team environments, developers often work with many repos that should all follow the same standards. A global config acts as a "default floor" without forcing per-repo duplication.
Opt-in Design
This is purely optional. Users who don't need it simply don't create
~/.kimi/AGENTS.md. Zero impact on existing workflows. Those who need it get a much better multi-project experience.Related
Please reconsider this feature. The "more compelling reasons" asked for in #439 is right here: multi-project maintenance is a daily pain point that Skills simply cannot solve.