Where Does Auggie CLI Store Settings?
Auggie CLI settings, commands and skills on Windows, macOS and Linux, global versus project scope.
Last updated
Auggie stores User settings in ~/.augment/settings.json on macOS and Linux and the equivalent .augment path on Windows. Project overrides live in <workspace>/.augment/settings.json. MCP servers, shell choice and permissions resolve through those files.
Commands and skills follow the same split. Global markdown sits in ~/.augment, project markdown in ./.augment. The wizard writes the same files a hand edit would touch.
Where Auggie CLI stores this, by platform
%USERPROFILE%\.augment\settings.json
Wizard and hand edits target this file. Project file at <workspace>/.augment/settings.json wins on conflict. Restart after manual changes.
~/.augment/settings.json
Global commands in ~/.augment/commands, skills in ~/.augment/skills and .claude/skills. Project copies under ./.augment take precedence.
~/.augment/settings.json
Same layout as macOS. MCP flags from the command line override file values for that run only.
Frequently asked questions
Where do Auggie custom commands live?
Put shared prompts in ./.augment/commands/*.md inside the repo. Personal ones belong in ~/.augment/commands. Auggie resolves project paths first, then global, then Claude Code fallbacks.
How do I change Auggie settings safely?
Open the /config wizard in interactive mode. Changes save to the User settings file below, or the project file when one exists. Restart Auggie after hand edits.
Notice an outdated path? Let us know.