Where Does Junie Store Config and Guidelines?
Junie stores global config in a .junie folder at home and project rules in .junie at the repo root.
Last updated
Junie splits config the way modern agents do. User scope lives in ~/.junie (%USERPROFILE%\.junie on Windows): config.json, settings.json, AGENTS.md, and an mcp folder. Project scope lives in .junie at the repo root with the same files, and it travels with the code.
MCP servers follow the split exactly. Global servers added through IDE settings land in ~/.junie/mcp/mcp.json; project servers go in .junie/mcp/ by hand. CLI flags beat user settings, which beat project config, in that order. Extra files load via --config-location.
Where Junie stores this, by platform
~/.junie
config.json, settings.json, AGENTS.md, mcp/mcp.json. JUNIE_HOME relocates the whole tree. Project overrides live in .junie/ per repo.
~/.junie
Same layout as macOS. IDE plugin and CLI share these files.
%USERPROFILE%\.junie
Same files under your profile. Global guidelines path is %USERPROFILE%\.junie\AGENTS.md.
Frequently asked questions
How do I share Junie guidelines with my team?
Commit the project's .junie/AGENTS.md and .junie/mcp/mcp.json. Global ~/.junie stays personal. Teammates get rules and servers on checkout with no extra sync step.
Can I keep separate Junie profiles?
Yes. Set JUNIE_HOME to another directory before launching. It overrides the default ~/.junie for config, agents, and sessions, which keeps client setups isolated.
Notice an outdated path? Let us know.