CLI flags
| Command | Description |
|---|
auggie | Start Auggie in interactive mode |
auggie --print (-p) | Output simple text for one instruction and exit |
auggie --quiet | Output only the final response for one instruction and exit |
auggie --compact | Output tool calls, results, and final response as one line each and exit |
auggie -p --output-format json | Output the response in structured JSON format. Must be used with --print (-p) mode. Useful for parsing Auggie’s output programmatically in automation workflows. |
| Command | Description |
|---|
auggie "Fix the typescript errors" | Provide an initial instruction in interactive mode |
auggie --print "Summarize the staged changes" | Provide an instruction and exit |
cat file | auggie --print "Summarize this data" | Pipe content through stdin |
auggie --print "Summarize this data" < file.txt | Provide input from a file |
auggie --instruction "Fix the errors" | Provide an initial instruction in interactive mode |
auggie --instruction-file /path/to/file.txt | Provide an instruction by file in interactive mode |
Custom Commands
| Command | Description |
|---|
auggie command <command-name> | Execute a custom command from .augment/commands/ or ~/.augment/commands/ |
~/.augment/commands/<name>.md - Global commands (user-wide)./.augment/commands/<name>.md - Project commands (workspace-specific)~/.claude/commands/<name>.md - Claude Code user commands./.claude/commands/<name>.md - Claude Code workspace commands
Commands are resolved in order of precedence, with Auggie-specific locations taking priority over Claude Code locations.
Examples:
# Execute a custom deployment command
auggie command deploy-staging
# Execute a code review command
auggie command security-review
# List available commands (shown in help output)
auggie command help
Sessions
| Command | Description |
|---|
auggie --continue (-c) | Resumes the previous conversation |
auggie --dont-save-session | Do not save the conversation to the local history |
auggie --delete-saved-sessions | Delete all saved sessions from disk |
Configuration
| Command | Description |
|---|
auggie --workspace-root /path/to/project | Specify the root of the workspace |
auggie --rules /path/to/rules.md | Additional rules to append to workspace guidelines |
auggie --model "name" | Select the model to use (accepts long or short names from the model list) |
Models
List out available models and their short names to be passed into the --model flag
| Command | Description |
|---|
auggie models list | List available models |
| Command | Description |
|---|
auggie --remove-tool <tool-name> | Remove a specific tool by name for the current session. Can be specified multiple times. |
auggie tools list | List all available tools and their current status |
auggie tools remove <tool-name> | Persistently remove a tool by adding it to the removedTools list in settings.json |
auggie tools add <tool-name> | Re-enable a previously removed tool by removing it from the removedTools list |
# Disable the web-fetch tool for this session
auggie --remove-tool web-fetch
# Disable multiple tools for this session
auggie --remove-tool web-fetch --remove-tool web-search
# Persistently disable a tool
auggie tools remove launch-process
# Re-enable a previously disabled tool
auggie tools add launch-process
# See all tools and their status
auggie tools list
Command-line
--remove-tool flags take precedence over settings. For fine-grained control over tool behavior (allow, deny, ask-user), see
Permissions.
MCP and integrations
| Command | Description |
|---|
auggie mcp add [options] <name> | Create or update a named MCP server configuration |
auggie mcp add-json <name> <json> | Add an MCP server from JSON configuration |
auggie mcp list | Display all configured MCP servers |
auggie mcp remove <name> | Remove a named MCP server configuration |
| Command | Description |
|---|
auggie --mcp-config {key: value} | MCP configuration as a JSON string |
auggie --mcp-config /path/to/mcp.json | MCP configuration from a JSON file |
You can define MCP servers persistently in the settings files: ~/.augment/settings.json. Any --mcp-config flags are applied last and override settings.
Authentication
| Command | Description |
|---|
auggie login | Login to Augment and store the token locally |
auggie logout | Remove the locally stored token |
auggie tokens print | Print the locally stored token |
Additional commands
| Command | Description |
|---|
auggie --help | Show help |
auggie --version | Show version |
Environment Variables
| Variable | Description |
|---|
AUGMENT_SESSION_AUTH | Authentication JSON. |
AUGMENT_API_URL | Backend API endpoint |
AUGMENT_API_TOKEN | Authentication token |
GITHUB_API_TOKEN | GitHub API token |
AUGMENT_DISABLE_AUTO_UPDATE | Disable automatic CLI updates |
Shell Environment
When Auggie executes shell commands using the launch-process tool, it sets the following environment variable:
| Variable | Description |
|---|
AUGMENT_AGENT | Set to 1 when a command is executed by Auggie. Scripts can check for this variable to detect if they are being run by the agent. |
if [ -n "$AUGMENT_AGENT" ]; then
echo "Running inside Auggie"
# Adjust behavior for agent execution
fi
See Also
