Skip to main content

​
How the Configuration Wizard Works

The /config command opens an interactive configuration wizard in Auggie CLI that allows you to customize your CLI experience. This wizard provides a user-friendly interface to manage various settings without manually editing configuration files.

​
Accessing the Configuration Wizard

In interactive mode (TUI), use the /config slash command: 
# Start Auggie in interactive mode
auggie

# Then type the slash command
/config

​
Available Configuration Options

The configuration wizard allows you to customize the following settings:

​
Shell Selection

Choose your preferred shell for command execution:
  • bash
  • zsh
  • fish
  • powershell
The selected shell will be used when Auggie needs to execute shell commands in your environment.

​
Startup Script

Configure a custom startup script that runs when Auggie starts. This is useful for:
  • Setting environment variables
  • Loading custom configurations
  • Initializing tools or services

​
Chat Input Completions

Enable or disable chat input completions in the CLI. When enabled, Auggie provides intelligent autocomplete suggestions as you type in the chat interface. This setting controls the enableChatInputCompletions option in your settings file.

​
Auto-Update

Control whether Auggie automatically updates itself when running in interactive mode.
  • Enabled (default): Auggie checks for and installs updates automatically
  • Disabled: You must manually update using auggie upgrade
See Automatic Updates for more details about how auto-updates work.

​
Notifications

Choose how Auggie notifies you about important events:
  • Off: No notifications
  • Bell: Terminal bell sound
  • Desktop Notification: System desktop notifications

​
Settings File

Configuration changes made through the Configuration Wizard are saved to ~/.augment/settings.json on macOS and Linux, and C:\Users\<username>\.augment\settings.json on Windows. If you have project settings (<workspace>/.augment/settings.json), you will be prompted where to save the configuration. See Hierarchical Settings File for more details.

​
Hierarchical Settings File

Auggie also supports hierarchical settings files to allow you to configure settings at different levels of granularity. This lets you define shared settings in project settings while individual developers add their own user or local project settings without replacing the shared configuration.
  1. Managed settings (read-only)
    • /etc/augment/settings.json on macOS and Linux
    • C:\ProgramData\augment\settings.json on Windows
    • Set by organization admins and cannot be overridden by users
    • Locked settings are displayed to the user but cannot be modified
  2. Local project settings (personal, per-project)
    • <workspace>/.augment/settings.local.json
    • Best for personal project-specific overrides, such as your own MCP servers for one repository
    • Automatically added to .gitignore and should not be committed
    • Use the --local flag on settings-modifying commands to write here, for example: auggie mcp add --local
  3. Project settings (shared, per-project)
    • <workspace>/.augment/settings.json
    • Best for team-shared project configuration, such as shared MCP servers or tool permissions
    • Should be committed to source control so the team shares the same Augment configuration
    • Use the --project flag on settings-modifying commands to write here, for example: auggie mcp add --project
  4. User settings (personal, global)
    • ~/.augment/settings.json on macOS and Linux
    • C:\Users\<username>\.augment\settings.json on Windows
    • Personal defaults that apply across projects
    • This is the default target when no --project or --local flag is provided
Use project settings for shared team defaults, and local project settings for personal overrides you do not want to commit.
Settings are merged across all levels. Higher-precedence files override lower-precedence files for simple values, while objects and lists are combined across tiers.
MCP server and plugin entries are replaced, not deep-merged. If both your user settings and project settings define an MCP server with the same name, the higher-precedence file’s entire server configuration wins. Individual properties like args or env are not merged between files. To customize a shared server, copy the full configuration into your local project settings.Tool permission rules from all tiers are concatenated, with higher-precedence rules evaluated first using first-match logic. Lists like removedTools and indexingAllowDirs are unioned across all tiers and deduplicated. Both are additive only — there is no way to remove a value that a higher-precedence file contributes.Simple personal settings like verbose and vimMode are read from user settings only and are ignored if placed in project or managed files.
If more than one writable settings file is available, Auggie prompts you to choose where to save the change. You can also manually edit these files to configure settings. The files support JSON5 format, allowing comments and trailing commas for better documentation.

​
Example settings.json

{
  "shell": "zsh",
  "startupScript": "source ~/.augment/startup.sh",
  "enableChatInputCompletions": true,
  "autoUpdate": true,
  "notificationMode": "desktop_notification",
  "autoUpdateMarketplaces": true
}
See Plugins and Marketplaces for plugin-related settings like autoUpdateMarketplaces, recommendedMarketplaces, and dismissedMarketplaces.

​
Manual Configuration

While the /config wizard provides a convenient interface, you can also manually edit the appropriate Augment settings file directly. After making manual changes, restart Auggie for the changes to take effect.