GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Augment home page
  • Status
  • Blog
  • Support
  • Introduction
  • Getting Started
  • Configuring Cosmos
  • Sessions
  • Keyboard shortcuts
  • Overview
  • What's new in 1.x
  • Settings
  • Subagents
  • Rules & Guidelines

This view

  • Original page
  • New address

GeezerVison is showing docs.augmentcode.com — Settings - Augment

​
The /settings menu

The /settings slash command opens an interactive menu for common options. It replaces the /config command from Auggie 0.x.
# Start Auggie in interactive mode
auggie

# Then type the slash command
/settings
Type to filter the list, use the arrow keys to move, and press Enter to change a value. Press Escape to go back. Changes made in /settings are always saved to your user settings file, ~/.augment/settings.json (C:\Users\<username>\.augment\settings.json on Windows). Auggie 1.x does not prompt you to choose a settings file. To change project or local settings, edit those files directly.

​
Available options

​
General

OptionSettingDescription
Auto-compactcompaction.enabledAutomatically summarize the conversation when the context window fills up
Steering modesteeringModeSend steering messages one-at-a-time or all at once
Follow-up modefollowUpModeSend queued follow-up messages one-at-a-time or all at once
Double-escape actiondoubleEscapeActionWhat pressing Escape twice does: tree, fork, or none
Tree filter modetreeFilterModeDefault filter for /tree
Auto-resize imagesimages.autoResizeResize images to at most 2000x2000 before sending. Images fetched by the web-fetch tool are always resized
Block imagesimages.blockImagesNever send images to the model
Skill commandsenableSkillCommandsRegister skills as /skill:name commands
MCP tool discoverydisableToolSearchTurn off automatic MCP tool discovery, which hides MCP tools behind find-tool and execute-tool when their definitions take up too much context. Appears only when automatic discovery is available

​
Display

These options only change how the terminal UI looks.
OptionSettingDescription
ThemethemeColor theme: dark, light, ansi, or a custom theme
Hide thinkinghideThinkingBlockHide reasoning blocks in the transcript
Quiet startupquietStartupHide the startup header
Collapse changelogcollapseChangelogShow a condensed changelog after updates
Collapse prompt commandscollapsePromptCommandsShow custom command invocations as a single collapsed line
Show imagesterminal.showImagesRender images in terminals that support it
Show hardware cursorshowHardwareCursorShow the terminal cursor
Editor paddingeditorPaddingXHorizontal padding for the input editor (0-3)
Autocomplete max itemsautocompleteMaxVisibleNumber of visible autocomplete suggestions (3-20)
Clear on shrinkterminal.clearOnShrinkClear empty rows when content shrinks
Some options only appear when the related feature is available. To change the reasoning effort, use /effort or press Shift+Tab.

​
Themes

Auggie 1.x ships with dark, light, and ansi themes. Use ansi if your terminal does not support true color. The legacy default-dark value from 0.x is treated as dark.
{
  "theme": "ansi"
}

​
Settings files

Auggie reads settings from these files, from highest to lowest precedence:
  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
  2. Local project settings: <workspace>/.augment/settings.local.json
    • Personal, per-project overrides that should not be committed
  3. Project settings: <workspace>/.augment/settings.json
    • Shared, per-project configuration that should be committed to source control
  4. User settings: ~/.augment/settings.json
    • Personal defaults that apply across projects, and the file /settings writes to
Higher-precedence files override lower-precedence files. Tool permission rules from all files are combined. Some commands still write to project or local settings when you ask them to, for example auggie mcp add --project or auggie mcp add --local. See Integrations and MCP. The files support JSON with Comments (JSONC), so comments and trailing commas are allowed. After editing a file manually, restart Auggie for the changes to take effect.

​
Example settings.json

{
  "defaultModel": "sonnet",
  "theme": "dark",
  "shellPath": "zsh",
  "shellCommandPrefix": "source ~/.augment/startup.sh",
  "notificationMode": "desktop_notification",
  "autoUpdate": true
}

​
Common settings

SettingDescription
defaultModelDefault model for new sessions
defaultThinkingLevelDefault reasoning effort: off, minimal, low, medium, high, or xhigh
themeColor theme
shellPathShell used by the bash tool: a full path, or bash, zsh, fish, sh, or powershell. shell (the 0.x name) still works
shellCommandPrefixShell code run before every bash tool command, for example source ~/.augment/startup.sh. It’s shell text, not a file path. startupScript (the 0.x name) still works
notificationModeNotify when the agent finishes or asks a question: off, bell, or desktop_notification
autoUpdateAutomatically update Auggie in interactive mode. See Automatic Updates
updateTerminalTitleSet the terminal title automatically
verboseExpand tool output by default
See Permissions for toolPermissions and Integrations and MCP for mcpServers.

​
Keybindings

Customize keyboard shortcuts in ~/.augment/keybindings.json, then run /reload to apply them. Run /hotkeys to see all current shortcuts.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.