You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 23, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 23, 2026. It is now read-only.
[Feature Request] Support global ~/.kimi/AGENTS.md for multi-project shared conventions #2152
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)
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.
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.
Reacted by chengh-git, lNeverl, Wang Weiyi, Danila and ChrisDoufu
Activity
chengh-git commentedon May 6, 2026
Conldn' t agree more, global ~/.kimi/AGENTS.md is realy important and helpful.
DRYN07 commentedon May 8, 2026
I've been looking for this for about two days now. Are you saying there is no option to set global rules???? omg.
chengh-git commentedon May 8, 2026
Yes, no global memory like the CLAUDE.md in ~/.claude/, just for project. Hope Kimi team can make it
cezaronx commentedon May 16, 2026
also lost hours looking for the global agents.md ! this is really needed.