# Using Auggie with Automation Source: https://docs.augmentcode.com/cli/automation Auggie was designed to not just be a powerful agent to write code, but to automate all the tasks that are needed to build software at scale. ## About automation Auggie was purpose built to integrate into your software development stack. From using Auggie in your local development workflows to automatically running Auggie in your CI/CD pipelines, Auggie can help you build better software faster. ### Example use cases * **Code reviews**: Review code changes and provide feedback. * **Issue triage**: Triage incoming issues and route them to the appropriate team or individual. * **Automate on-call**: Respond to incoming alerts and create an assessment plan. * **Exception management**: Analyze incoming exceptions and create tickets. ## Integrating with your workflows In order to use Auggie in your systems, like a CI/CD pipeline, you'll need to install Auggie CLI, provide a session token, and write an instruction that will be used alongside any data from your system you want to include. ### Installation Auggie can be [installed](/cli/setup-auggie/install-auggie-cli) directly from npm anywhere you can run Node 22 or later including VMs, serverless functions, and containers. You will also need to install any dependencies for defined MCP servers in those environments. ```sh npm install -g @augmentcode/auggie ``` ### Authentication Session tokens are associated with the user that created it, and Auggie will run with integration configurations from that user. See [Authentication](/cli/setup-auggie/authentication) for full details. You can override the user's GitHub configuration by passing `--github-api-token `. ```sh # First, login to Augment with the CLI auggie --login # Next, output your token auggie --print-augment-token # Then, pass your token to auggie AUGMENT_SESSION_AUTH='' auggie --print "Summarize the build failure" ``` ### Scripts and pipes Auggie runs as a subprocess, so it can be used in any shell script. It can be used just like any command-line tool that follows the Unix philosophy. You can pipe data into Auggie and then pipe the response to another command. Data passed into Auggie through stdin will be used as context in addition to the instruction. ```sh # Pipe data through stdin cat build.log | auggie --print "Summarize the failure and open a Linear ticket" # Provide input from a file auggie --compact --instruction /path/to/instruction.md < build.log ``` ## GitHub Actions GitHub Actions makes it easy to connect Auggie to other parts of your software development pipeline, from linting, testing, build, and deploy. We've built a [simple wrapper for Auggie](https://github.com/augmentcode/augment-agent) that enables you to integrate with GitHub Action workflows and build custom tooling around Auggie. Follow the instructions to [configure Augment Agent](https://github.com/augmentcode/augment-agent/blob/main/README.md) in GitHub Actions and explore the [example-workflows](https://github.com/augmentcode/augment-agent/tree/main/example-workflows) directory to get started. ### Ready to use workflows Get started using Auggie in GitHub Actions immediately by following the instructions for setup and deploy in one of the following workflows, or use the `/github-workflow` wizard in Auggie to have the workflows generated for you. * [PR Description](https://github.com/augmentcode/describe-pr): This action automatically analyzes your PR changes and generates comprehensive, informative descriptions. * [PR Review](https://github.com/augmentcode/review-pr): This action automatically analyzes your PR changes and generates comprehensive, informative reviews Need even more help building GitHub Actions? May we suggest asking Auggie. ```sh auggie "Help me build a GitHub Action to..." ``` # Custom Slash Commands Source: https://docs.augmentcode.com/cli/custom-commands Create and manage custom slash commands for frequently-used prompts and workflows. ## About Custom Slash Commands Custom slash commands let you create reusable prompts stored as Markdown files that Auggie can run. You can organize commands by scope (workspace or user) and use directory structures for namespacing. ### Syntax ``` / [arguments] ``` ### Parameters | Parameter | Description | | :--------------- | :--------------------------------------- | | `` | Name derived from the Markdown filename | | `[arguments]` | Optional arguments passed to the command | ## Command Types and Locations Custom commands are stored in markdown files and can be placed in multiple locations with a specific order of precedence: ### Command Locations (in order of precedence) 1. **User Commands**: `~/.augment/commands/.md` (user) 2. **Workspace Commands**: `./.augment/commands/.md` (workspace) 3. **Claude Code Commands**: `./.claude/commands/.md` (.claude) ### User Commands Commands available across all your projects. These are user-wide and persist across different workspaces. **Location**: `~/.augment/commands/` ```sh # Create a global command mkdir -p ~/.augment/commands echo "Review this code for security vulnerabilities:" > ~/.augment/commands/security-review.md ``` ### Workspace Commands Commands stored in your repository and shared with your team. These are workspace-specific and can be committed to version control. **Location**: `./.augment/commands/` ```sh # Create a workspace command mkdir -p .augment/commands echo "Analyze this code for performance issues and suggest optimizations:" > .augment/commands/optimize.md ``` ### Claude Code Compatibility Auggie automatically detects and supports commands from `./.claude/commands/` for compatibility with existing Claude Code setups. This allows teams already using Claude Code to continue using their existing command libraries without modification. **Location**: `./.claude/commands/` and `~/.claude/commands/` **Migration**: While `./.claude/commands/` is supported for compatibility, we recommend migrating to `./.augment/commands/` for new projects to maintain consistency with Auggie's naming conventions. ## Features ### Namespacing Organize commands in subdirectories. Commands from nested directories can be accessed using the `namespace:command` syntax, where the namespace corresponds to the subdirectory name. For example, a file at `.augment/commands/frontend/component.md` creates the command `/frontend:component`. Conflicts between user and workspace level commands are not supported and will be defined in order of precedence above. ### Arguments Pass dynamic values to commands. ```markdown # Command definition echo 'Fix issue following our coding standards' > .augment/commands/fix-issue.md # Usage > /fix-issue 123 ``` ### Frontmatter Command files support frontmatter for metadata: | Frontmatter | Purpose | Default | | :-------------- | :------------------------------------------------------------------------- | :---------------------------------- | | `description` | Brief description of the command | Uses the first line from the prompt | | `argument-hint` | Expected arguments format that will be displayed after typing in a command | None | | `model` | Specify the model to run this command with (overrides the CLI default) | Uses the CLI default model | **File**: `~/.augment/commands/deploy-staging.md` ```markdown --- description: Deploy the application to staging with health checks argument-hint: [branch-name] model: gpt-4o --- Deploy the application to the staging environment: 1. Run all tests to ensure code quality 2. Build the application for production 3. Deploy to staging server 4. Run health checks to verify deployment 5. Send notification to team channel ``` ## Command Line Execution We also provide the ability to execute custom commands from the command line using the `auggie command ` or list them with `auggie command list`. For complete command-line reference, see [CLI Reference for Custom Commands](/cli/reference#custom-commands). ```sh # Execute a custom command auggie command deploy-staging # List all available commands (including custom ones) auggie command list ``` Custom commands appear in the help output with their descriptions: ``` Available custom commands: auggie command deploy-staging # Deploy the application to staging auggie command security-review # Review code for security vulnerabilities ``` ## Example Commands For ready-to-use examples of custom slash commands, including code review templates, bug fix guides, and feature implementation plans, see: **[Custom Commands Examples](/cli/custom-commands-examples)** ## Best Practices 1. **Use kebab-case naming** for command names (e.g., `deploy-staging`, `run-tests`) 2. **Keep names descriptive** but concise, avoiding spaces and special characters 3. **Use meaningful prefixes** for related commands (e.g., `deploy-staging`, `deploy-production`) 4. **Include clear descriptions** in frontmatter for better discoverability 5. **Break complex workflows** into numbered steps for clarity 6. **Use user commands** (`~/.augment/commands/`) for personal workflows across all projects 7. **Use workspace commands** (`./.augment/commands/`) for team-shared, project-specific tasks 8. **Organize with subdirectories** for related command groups using namespacing 9. **Document command purpose** and expected outcomes clearly 10. **Version your commands** when making significant changes ## See Also * [Custom Commands Examples](/cli/custom-commands-examples) - Ready-to-use command templates and examples * [Interactive Mode Slash Commands](/cli/interactive#slash-commands) - Learn about Auggie's interactive terminal features * [CLI Reference for Custom Commands](/cli/reference#custom-commands) - Complete reference for command-line flags # Custom Slash Commands Examples Source: https://docs.augmentcode.com/cli/custom-commands-examples Ready-to-use examples of custom slash commands for common development workflows. ## Example Commands Here are some practical examples of custom slash commands you can use in your projects: ```markdown --- description: Perform a comprehensive code review argument-hint: [file-path] --- Please perform a comprehensive code review of the specified file or current changes, focusing on: 1. **Code Quality**: Check for readability, maintainability, and adherence to best practices 2. **Security**: Look for potential security vulnerabilities 3. **Performance**: Identify potential performance issues 4. **Testing**: Suggest areas that need test coverage 5. **Documentation**: Check if code is properly documented $ARGUMENTS ``` ```markdown --- description: Generate a structured bug fix approach argument-hint: [bug-description] --- Help me fix this bug: $ARGUMENTS Please provide: 1. Root cause analysis 2. Step-by-step fix approach 3. Testing strategy 4. Prevention measures for similar issues ``` ```markdown --- description: Create implementation plan for new features argument-hint: [feature-description] --- Create a detailed implementation plan for: $ARGUMENTS Include: - Technical requirements - Architecture considerations - Implementation steps - Testing approach - Documentation needs ``` ```markdown --- description: Perform security analysis on code argument-hint: [file-path] --- Perform a security review of: $ARGUMENTS Focus on: 1. **Input validation** and sanitization 2. **Authentication** and authorization checks 3. **Data exposure** and privacy concerns 4. **Injection vulnerabilities** (SQL, XSS, etc.) 5. **Cryptographic** implementations 6. **Dependencies** with known vulnerabilities Provide specific recommendations for any issues found. ``` ```markdown --- description: Analyze and optimize code performance argument-hint: [file-path] --- Analyze the performance of: $ARGUMENTS Please examine: 1. **Algorithm complexity** and efficiency 2. **Memory usage** patterns 3. **Database queries** and optimization opportunities 4. **Caching** strategies 5. **Network requests** and bundling 6. **Rendering performance** (for frontend code) Suggest specific optimizations with expected impact. ``` ```markdown --- description: Generate comprehensive documentation argument-hint: [file-path] --- Generate documentation for: $ARGUMENTS Include: 1. **Overview** and purpose 2. **API reference** with parameters and return values 3. **Usage examples** with code snippets 4. **Configuration options** if applicable 5. **Error handling** and troubleshooting 6. **Dependencies** and requirements Format as clear, structured markdown. ``` ```markdown --- description: Generate comprehensive test cases argument-hint: [file-path] --- Generate test cases for: $ARGUMENTS Create tests covering: 1. **Happy path** scenarios 2. **Edge cases** and boundary conditions 3. **Error handling** and exceptions 4. **Integration points** with other components 5. **Performance** considerations 6. **Security** edge cases Use appropriate testing framework conventions and include setup/teardown as needed. ``` ## How to Add Commands to Your Project To use these custom slash commands in your project, you need to save them in the `.augment/commands/` directory: ### Step 1: Create the Commands Directory First, create the `.augment/commands/` directory in your project root if it doesn't exist: ```bash mkdir -p .augment/commands ``` ### Step 2: Save Command Files Save each command as a separate `.md` file in the `.augment/commands/` directory. For example: ```bash # Save the code review command cat > .augment/commands/code-review.md << 'EOF' --- description: Perform a comprehensive code review argument-hint: [file-path] --- Please perform a comprehensive code review of the specified file or current changes, focusing on: 1. **Code Quality**: Check for readability, maintainability, and adherence to best practices 2. **Security**: Look for potential security vulnerabilities 3. **Performance**: Identify potential performance issues 4. **Testing**: Suggest areas that need test coverage 5. **Documentation**: Check if code is properly documented $ARGUMENTS EOF ``` ### Step 3: Use Your Commands Once saved, your custom commands become available as slash commands in Augment: ``` /code-review src/components/Button.tsx /bug-fix "Login form validation not working" /security-review auth/middleware.js ``` ### Directory Structure Your project structure should look like this: ``` your-project/ ├── .augment/ │ └── commands/ │ ├── code-review.md │ ├── bug-fix.md │ ├── security-review.md │ └── performance-optimization.md ├── src/ └── package.json ``` ## Usage Tips * **Save these templates** in your `.augment/commands/` directory * **Customize the prompts** to match your team's coding standards and practices * **Add project-specific context** to make the commands more effective * **Combine commands** by referencing outputs from one command in another * **Use meaningful filenames** like `code-review.md`, `bug-fix.md`, etc. * **Version control your commands** by committing the `.augment/commands/` directory to your repository ## Creating Your Own Examples When creating custom commands, consider these patterns: 1. **Start with a clear description** in the frontmatter 2. **Use argument hints** to guide users on expected inputs 3. **Structure your prompts** with numbered lists or bullet points 4. **Include specific instructions** for the type of analysis or output you want 5. **Reference the `$ARGUMENTS` variable** where user input should be inserted ## See Also * [Custom Slash Commands](/cli/custom-commands) - Learn how to create and manage custom commands * [CLI Reference for Custom Commands](/cli/reference#custom-commands) - Complete command-line reference for custom commands # Integrations and MCP Source: https://docs.augmentcode.com/cli/integrations Expand Augment's capabilities with external tools and data sources through native integrations and Model Context Protocol (MCP) servers. export const Command = ({text}) => {text}; export const Keyboard = ({shortcut}) => {shortcut} ; Auggie runs commands and tools automatically. Only use integrations and MCP servers from trusted sources, and be aware of the risks of combining multiple tools with external data sources or production systems. ## About Integrations and MCP Auggie can utilize external integrations through native integrations like GitHub, Linear, and Notion and Model Context Protocol (MCP) to access external systems for information and integrate tools to take actions. MCP is an open protocol that provides a standardized way to connect AI models to different data sources and tools. ## Native Integrations You'll need to configure the integration in Augment for VS Code or JetBrains IDEs. Once configured, the integration will be available for use with Auggie automatically. See a full list and examples for [native agent integrations](/setup-augment/agent-integrations). ### 1. Setup in Augment extension * **Visual Studio Code**: Click the settings icon in the top right of Augment's chat window or press and select * **JetBrains IDEs**: Click the Augment icon in the bottom right of your JetBrains IDE and select ### 2. Connect the integration Click "Connect" for the integration you want to set up Set up integrations in the settings page You'll be redirected to authorize the integration with the appropriate service. After authorization, the integration will be available for use with Augment Agent. ## MCP Integrations In addition to native integrations, Auggie can also access external systems through Model Context Protocol (MCP) servers. MCP servers can be used to access local or remote databases, run automated browser testing, send messages to Slack, or even play music on Spotify. You can use multiple MCP servers with Auggie by passing a JSON string or a path to a JSON file with the `--mcp-config` flag. You can pass the flag multiple times for multiple configurations. Some servers may require you to install dependencies on the host machine or containers. ```json // After npm install gitlab-mr-mcp { "mcpServers": { "gitlab-mr-mcp": { "command": "node", "args": ["/path/to/gitlab-mr-mcp/index.js"], "env": { "MR_MCP_GITLAB_TOKEN": "your_gitlab_token", "MR_MCP_GITLAB_HOST": "your_gitlab_host" } } } } ``` # Interactive mode Source: https://docs.augmentcode.com/cli/interactive Use a rich interactive terminal experience to explore your codebase, build new features, debug issues, and integrate your tools. export const Command = ({text}) => {text}; Auggie is currently in beta and does not support all features available in the Augment plugins for Visual Studio Code or JetBrains IDEs. ## About interactive mode Auggie is an agentic terminal-based code assistant that has deep codebase knowledge powered by Augment's context engine. Auggie can help you understand a new codebase, fix bugs quickly, and build new features faster. Auggie has access to your connected integrations and MCP servers and can pull in additional context or run tools to get your tasks done. ## Using interactive mode Run `auggie` without any mode flags to get the full-screen terminal user interface with rich interactive features, real-time streaming of responses, and visual progress indicators. This mode shows all tool calls, results, and allows ongoing conversation through an intuitive interface. ```sh # Start Auggie in interactive mode auggie # Provide an initial instruction auggie "Look at my open issues and prioritize the highest impact ones for me" ``` ### Multi-line input Entering a new line in the input box depends on your terminal configuration and platform. You can use `Ctrl + J` to enter a new line in any terminal. See below for instructions to configure your terminal to use `Option + Enter` to enter a new line. | Terminal application | New line shortcut | | :------------------------- | :---------------- | | All terminals | `Ctrl + J` | | MacOS Terminal (see below) | `Option + Enter` | | iTerm2 (see below) | `Option + Enter` | | VS Code Terminal | `Option + Enter` | | Ghostty | `Shift + Enter` | **MacOS Terminal** 1. Go to 2. Check **iTerm2** 1. Go to 2. Check ## Reference ### Shortcuts | Command | Description | | :------------------ | :---------------------------------------------------------- | | `Ctrl + P` | Enhance your prompt with codebase context | | `Escape` | Interrupt the active agent | | `Ctrl + C` | Interrupt the active agent | | `Escape` + `Escape` | Clear the input box | | `Ctrl + C` | Press twice to exit | | `Ctrl + D` | Press twice to exit | | `Up Arrow` | Cycle through previous messages | | `Down Arrow` | Cycle through previous messages | | `Ctrl + O` | Open current input in external editor, inserts text on exit | ### Slash Commands | Command | Description | | :----------------- | :---------------------------------------------------------- | | `/account` | Show account information | | `/clear` | Clear the input box | | `/editor` | Open current input in external editor, inserts text on exit | | `/exit` | Exit Auggie | | `/feedback` | Provide feedback to the Augment team | | `/github-workflow` | Generate a GitHub Action workflow | | `/help` | Show help | | `/logout` | Logout of Augment | | `/mcp-status` | View the status of all configured MCP servers | | `/model` | Select the model for this session | | `/new` | Start a new conversation with no message history | | `/permissions` | View and manage tool permissions | | `/request-id` | Show the request ID for the current conversation | | `/task` | Open task manager to add, edit, and manage tasks | | `/verbose` | Toggle verbose output for tools | | `/vim` | Toggle Vim mode for advanced text editing | For more information about slash commands, including how to create custom commands, see [Custom Slash Commands](/cli/custom-commands). # Prompt Enhancer Source: https://docs.augmentcode.com/cli/interactive/prompt-enhancer Use Ctrl+P to enhance your prompts with relevant context, structure, and conventions from your codebase. export const Keyboard = ({shortcut}) => {shortcut} ; ## About the Prompt Enhancer The Auggie CLI prompt enhancer is a powerful feature that helps you craft better prompts by automatically adding relevant context, structure, and conventions from your codebase. Instead of writing detailed prompts from scratch, you can start with a simple idea and let the prompt enhancer transform it into a comprehensive, well-structured prompt. ## Activating the Prompt Enhancer To use the prompt enhancer in Auggie's interactive mode: 1. **Start typing your prompt** in the input box 2. **Press ** to activate the prompt enhancer 3. **Wait for enhancement** - Auggie will process your prompt and replace it with an enhanced version 4. **Review and edit** the enhanced prompt if needed 5. **Submit your enhanced prompt** by pressing Enter The prompt enhancer is only available when you have text entered at the command prompt. The shortcut will only work in interactive mode. ## How It Works When you press , the prompt enhancer: 1. **Captures your current input** and saves it to history 2. **Switches to Enhancement mode** - you'll see the mode indicator change and input will be temporarily disabled 3. **Sends your prompt** to the enhancement service using your current workspace context 4. **Processes the response** and extracts the enhanced prompt 5. **Replaces your input** with the enhanced version and returns to Normal mode During enhancement, you'll see: * The mode indicator shows "Enhancing your prompt, press Esc to cancel" * Input is disabled to prevent conflicts * A visual indication that processing is in progress ## Enhancement Process The prompt enhancer uses your workspace context to improve your prompts by: * **Adding relevant file references** from your current project * **Including coding conventions** and patterns from your codebase * **Structuring the prompt** for better clarity and specificity * **Adding context** about your project's architecture and dependencies * **Suggesting specific examples** based on existing code patterns ## Canceling Enhancement You can cancel the prompt enhancement process at any time: * **Press ** to cancel enhancement and restore your original input * **Press ** to cancel enhancement and restore your original input When canceled, you'll see a brief notification and your original prompt will be restored. ## Error Handling If the prompt enhancement fails: * Your original input will be restored * An error notification will appear briefly (\~3 seconds) * You can try enhancing again or proceed with your original prompt Common reasons for enhancement failure: * Network connectivity issues * Service temporarily unavailable * Input too short or unclear for enhancement ## Examples ### Before Enhancement ``` fix the login bug ``` ### After Enhancement (Example) ``` Fix the authentication bug in the login flow. Please: 1. Review the current login implementation in `src/auth/login.ts` 2. Check for issues with token validation and session management 3. Examine error handling in the authentication middleware 4. Look at recent changes to the user authentication flow 5. Test the fix with both valid and invalid credentials 6. Ensure the fix follows our existing error handling patterns Context: This appears to be related to the recent changes in the authentication system. Please maintain consistency with our existing auth patterns and ensure proper error messages are returned to the user. ``` ## Integration with Other Features The prompt enhancer works seamlessly with other Auggie CLI features: * **History Navigation**: Enhanced prompts are added to your command history * **Multi-line Input**: Works with both single-line and multi-line prompts * **Conversation Context**: Uses your current conversation history for better enhancement * **Workspace Awareness**: Leverages your current workspace and file context ## Tips for Best Results 1. **Start with clear intent** - Even simple prompts like "add tests" or "refactor this" work well 2. **Be specific about scope** - Mention specific files or components when relevant 3. **Use domain language** - Technical terms related to your project help the enhancer understand context 4. **Review enhanced prompts** - The enhancer provides a starting point; feel free to edit further 5. **Iterate if needed** - You can enhance the same prompt multiple times for different approaches ## Troubleshooting **Ctrl+P doesn't work:** * Ensure you have text in the input box * Make sure you're in Normal mode (not in a menu or other mode) * Check that you're using the correct key combination for your terminal **Enhancement takes too long:** * Press Esc to cancel and try again * Check your network connection * Try with a shorter or simpler prompt **Enhanced prompt isn't helpful:** * Edit the enhanced prompt manually * Try starting with a more specific initial prompt * Consider the context - the enhancer works best with workspace-relevant requests ## Related Features * [Task Management](/cli/interactive/task-management) - Break down enhanced prompts into manageable tasks * [Keyboard Shortcuts](/cli/interactive#shortcuts) - Learn other useful CLI shortcuts * [Slash Commands](/cli/interactive#slash-commands) - Discover other interactive commands # Using Task Manager Source: https://docs.augmentcode.com/cli/interactive/task-management Use /task to break down complex problems into manageable steps. export const Command = ({text}) => {text}; export const Keyboard = ({shortcut}) => {shortcut} ; ## About the Task Manager The Auggie CLI task manager allows you to break down complex problems into discrete, manageable actions and track your progress through each step. It's particularly useful for automation workflows and keeping the agent focused on multi-step tasks. The task manager maintains state per session and stores tasks under `~/.augment` for persistence across CLI sessions. ## Activating the Task Manager Start Auggie in interactive mode and use the `/task` slash command: ```bash # Start Auggie in interactive mode auggie # Then type the slash command /task ``` This opens the task manager interface, which takes over the main panel and provides a focused environment for task management. ### Alternative Access You can also ask the agent to create a task list for you: ```bash auggie "Start a task list to implement user authentication" ``` The agent will automatically create and populate a task list when it encounters complex, multi-step problems. ## Task Manager Interface The task manager provides a scrollable interface with comprehensive theming and visual feedback. When active, it replaces the main chat interface to provide a focused task management experience. ### Navigation and Interaction Use your keyboard to interact with the Task Manager: | Key | Action | | :--------- | :----------------------------------------------------------------------------------------- | | `↑` / `↓` | Navigate between tasks. The active task is highlighted with • next to the \[ ] Task Title. | | `J` / `K` | Alternative vim-style navigation (up/down) | | `A` | Add a new task | | `E` | Edit the active task's title and description | | `D` | Delete the active task | | `Spacebar` | Toggle task status | | `Esc` | Dismiss the Task Manager | ## Task Status Indicators Tasks have three distinct states with corresponding visual status indicators: * **\[ ] Not Started** - Empty checkbox, task has not been started * **\[✓] Done** - Checkmark, task has been completed * **\[-] Cancelled** - Dash, task has been cancelled or is no longer needed ## Working with Tasks ### Creating Tasks **Manual Creation:** 1. Press `A` to add a new task 2. Enter the task title when prompted 3. Optionally add a description for more detailed context **Agent-Generated Tasks:** The agent automatically creates tasks inside the Task Manager when it encounters complex problems. You can also explicitly request task creation: ```bash "Create a task list to refactor the authentication system" ``` ### Editing Tasks 1. Navigate to the desired task using arrow keys or J/K 2. Press `E` to edit 3. Modify the title first, then the description 4. The task manager provides inline editing with clear visual feedback ### Task Execution **Manual Execution:** * Use the task list as a checklist, manually updating status as you complete work * Toggle status with `Spacebar` to track progress **Agent Execution:** You can ask the agent to work on specific tasks from the task manager: ```bash "Work on the first incomplete task in my task list" "Complete the database migration task" ``` The agent will access your task list and update task status as it works. ## Advanced Features ### Task Hierarchy and Subtasks The task manager supports nested task structures: * Main tasks can have subtasks for complex workflows * Subtasks are automatically indented and organized hierarchically * Navigate through nested structures using standard navigation keys ### Persistence and Sessions * Tasks are automatically saved per session under `~/.augment` * Task lists persist across CLI restarts within the same session * Each conversation session maintains its own task list ### Integration with Agent Workflow The task manager is designed to work seamlessly with agent automation: * **Keeps agents focused**: Provides clear structure for multi-step workflows * **Progress tracking**: Agent can update task status as it completes work * **Context preservation**: Tasks maintain context across long conversations * **Automation-friendly**: Particularly useful for non-interactive automation workflows ## Use Cases and Examples ### Development Workflow ```bash auggie "Create a task list to implement user registration feature" # Agent creates tasks like: # [ ] Design user registration API endpoints # [ ] Create user model and database schema # [ ] Implement registration validation # [ ] Add password hashing and security # [ ] Write unit tests for registration # [ ] Update API documentation ``` ### Code Refactoring ```bash auggie "Break down refactoring the payment system into tasks" # Agent creates structured tasks for complex refactoring ``` ### Bug Investigation ```bash auggie "Create tasks to investigate and fix the login timeout issue" # Agent creates systematic debugging tasks ``` ## Tips for Effective Task Management 1. **Be Specific**: Create clear, actionable task descriptions 2. **Break Down Complex Work**: Use subtasks for multi-step processes 3. **Regular Updates**: Keep task status current for accurate progress tracking 4. **Agent Collaboration**: Let the agent help create and organize task structures 5. **Session Organization**: Use task lists to maintain focus across long sessions ## Troubleshooting **Task Manager Won't Open:** * Ensure you're in interactive mode (`auggie` without `-p` flag) * Try typing `/task` exactly as shown * Check that you're not in the middle of another operation **Tasks Not Persisting:** * Tasks are saved per session - starting a new session creates a new task list * Check that `~/.augment` directory has proper write permissions **Navigation Issues:** * Use either arrow keys (↑/↓) or vim keys (J/K) for navigation * Ensure the task manager has focus (not in edit mode) ## Related Features * [Prompt Enhancer](/cli/interactive/prompt-enhancer) - Enhance task descriptions with context * [Keyboard Shortcuts](/cli/interactive#shortcuts) - Learn other useful CLI shortcuts * [Slash Commands](/cli/interactive#slash-commands) - Discover other interactive commands # Introducing Auggie CLI Source: https://docs.augmentcode.com/cli/overview Auggie in the terminal gives you powerful agentic capabilities to analyze code, make changes, and execute tools in an interactive terminal and in your automated workflows. export const Availability = ({tags}) => { const tagTypes = { invite: { styles: "bg-gray-700 text-white dark:border-gray-50/10" }, beta: { styles: "border border-zinc-500/20 bg-zinc-50/50 dark:border-zinc-500/30 dark:bg-zinc-500/10 text-zinc-900 dark:text-zinc-200" }, vscode: { styles: "border border-sky-500/20 bg-sky-50/50 dark:border-sky-500/30 dark:bg-sky-500/10 text-sky-900 dark:text-sky-200" }, jetbrains: { styles: "border border-amber-500/20 bg-amber-50/50 dark:border-amber-500/30 dark:bg-amber-500/10 text-amber-900 dark:text-amber-200" }, vim: { styles: "bg-gray-700 text-white dark:border-gray-50/10" }, neovim: { styles: "bg-gray-700 text-white dark:border-gray-50/10" }, default: { styles: "bg-gray-200" } }; return
Availability {tags.map(tag => { const tagType = tagTypes[tag] || tagTypes.default; return
{tag}
; })}
; }; ## Introduction Auggie CLI takes the power of Augment's agent and context engine and puts it in your terminal, allowing you to use Augment anywhere your code goes. You can use Auggie in a standalone interactive terminal session alongside your favorite editor or in any part of your software development stack. * Build features and debug issues with a standalone interactive agent. * Get instant feedback, insight, and suggestions for your PRs and builds. * Triage customer issues and alerts from your observability stack. ## Getting started To use Auggie CLI in interactive mode or in your automations, you'll need: * Node 22 or later installed * A compatible shell like zsh, bash, fish ```sh npm install -g @augmentcode/auggie ``` You can install Auggie CLI directly from npm anywhere you can run Node 22 or later. Auggie is currently in beta and may not run on all environments and terminal configurations. ```sh cd /path/to/your/project ``` Your project will be indexed automatically when you run Auggie in your project directory. Augment's powerful context engine provides the best results when it has access to your project's codebase and any related repositories. ```sh auggie login ``` After installing, you'll have to log in to your Augment account. Run auggie login and follow the prompts. ```sh auggie "optional initial prompt" ``` Just run `auggie` to start the interactive terminal. You can also pass a prompt as an argument and use `--print` to print the response to stdout instead of the interactive terminal–perfect for automation workflows. ## Using Auggie in interactive mode Run `auggie` without any mode flags to get the full-screen terminal user interface with rich interactive features, real-time streaming of responses, and visual progress indicators. This mode shows all tool calls, results, and allows ongoing conversation through an intuitive interface. Best for manual development work, exploration, and interactive problem-solving sessions where you want the full visual experience and plan to have back-and-forth conversations with the agent. ## Using Auggie in your automations **Print Mode**: Add the `--print` flag (e.g., `auggie --print "your instruction"`) to execute the instruction once without the UI. This mode exits immediately without prompting for additional input. Perfect for automation, CI/CD pipelines, and background tasks where you want the agent to act without follow-up from a person. **Quiet Mode**: `--quiet` flag (e.g., `auggie --print --quiet "your instruction"`) to tell the agent to only reply back with a final output. Ideal when you need to use the agent to provide structured data back without all the steps it took to get there. Provides a simple, clean response. # Tool Permissions Source: https://docs.augmentcode.com/cli/permissions Control what tools Auggie CLI can execute with granular permission settings for security and compliance. Tool permissions configured will only work inside the CLI and not in the Augment code extension. export const Command = ({text}) => {text}; export const Keyboard = ({shortcut}) => {shortcut} ; ## About Tool Permissions Auggie CLIs tool permission system provides fine-grained control over what actions the agent can perform in your environment. This security layer ensures that Auggie only executes approved operations, protecting your codebase and system from unintended changes. Tool permissions are especially important when: * Running Auggie in production environments * Working with sensitive codebases * Enforcing organizational security policies * Using Auggie in automated workflows ## How Permissions Work When Auggie attempts to use a tool, the permission system: 1. **Checks for matching rules** in your configuration 2. **Applies the first matching rule** based on tool name and optional patterns 3. **Rules are evaluated top-down** - first match wins 4. **Prompts for approval** when set to ask-user mode (interactive only) ### Permission Flow ``` Tool Request → Check Rules → Apply Permission → Execute/Deny → Log Decision ``` ### Notes on Unmatched Tools * Rules are evaluated in order from top to bottom * The first matching rule determines the permission * If no rules match, the CLI follows its implicit runtime behavior * Configure explicit rules for all tools you want to control ## Configuration Files Tool permissions are configured through `settings.json` files with clear precedence: ### File Locations 1. **User settings**: `~/.augment/settings.json` * Personal preferences that apply to all your projects * Ideal for your default security stance 2. **Project settings**: `/.augment/settings.json` * Repository-specific rules shared with your team * Perfect for project-specific security requirements Settings are merged with later files taking precedence. Project settings override user settings. ## Basic Configuration ### Creating Rules Rules define permissions for specific tools. Each rule can specify: * **Tool name** - The specific tool to control * **Permission type** - `allow`, `deny`, or `ask-user` * **Optional patterns** - For shell commands, use regex matching ### Basic Rule Structure ```json { "tool-permissions": [ { "tool-name": "launch-process", "permission": { "type": "deny" } }, { "tool-name": "view", "permission": { "type": "allow" } } ] } ``` ### Allow List Configuration Create an explicit allow list by only allowing specific tools: ```json { "tool-permissions": [ { "tool-name": "view", "permission": { "type": "allow" } }, { "tool-name": "codebase-retrieval", "permission": { "type": "allow" } }, { "tool-name": "grep-search", "permission": { "type": "allow" } }, { "tool-name": "github-api", "permission": { "type": "allow" } } ] } ``` This configuration explicitly allows only the listed tools. Tools not in this list will follow the CLI's implicit behavior. ### Block List Configuration Create a block list by explicitly denying specific dangerous tools: ```json { "tool-permissions": [ { "tool-name": "remove-files", "permission": { "type": "deny" } }, { "tool-name": "kill-process", "permission": { "type": "deny" } }, { "tool-name": "launch-process", "shell-input-regex": "^(rm|sudo|shutdown|reboot)", "permission": { "type": "deny" } } ] } ``` This configuration blocks specific dangerous operations. Tools not explicitly denied will follow the CLI's implicit behavior. ### Mix and Match Configuration Combine allow, deny, and ask-user rules for fine-grained control: ```json { "tool-permissions": [ { "tool-name": "view", "permission": { "type": "allow" } }, { "tool-name": "codebase-retrieval", "permission": { "type": "allow" } }, { "tool-name": "grep-search", "permission": { "type": "allow" } }, { "tool-name": "str-replace-editor", "permission": { "type": "ask-user" } }, { "tool-name": "save-file", "permission": { "type": "ask-user" } }, { "tool-name": "launch-process", "shell-input-regex": "^(npm test|npm run lint|git status|git diff)", "permission": { "type": "allow" } }, { "tool-name": "launch-process", "shell-input-regex": "^(rm -rf|sudo|chmod 777)", "permission": { "type": "deny" } }, { "tool-name": "launch-process", "permission": { "type": "ask-user" } }, { "tool-name": "remove-files", "permission": { "type": "deny" } } ] } ``` This configuration provides fine-grained control with different permission levels based on tool risk and usage patterns. ## Available Tools ### Process Management | Tool | Description | | :--------------- | :--------------------------------- | | `launch-process` | Execute shell commands and scripts | | `read-process` | Read output from running processes | | `write-process` | Send input to running processes | | `list-processes` | List all active processes | | `kill-process` | Terminate running processes | ### File Operations | Tool | Description | | :------------------- | :---------------------------------- | | `view` | Read file contents | | `str-replace-editor` | Edit files with find/replace | | `save-file` | Create or overwrite files | | `remove-files` | Delete files from the filesystem | | `codebase-retrieval` | Search codebase with context engine | | `grep-search` | Search files with regex patterns | ### External Services | Tool | Description | | :----------- | :--------------------------- | | `github-api` | GitHub API operations | | `linear` | Linear issue tracking | | `notion` | Notion workspace access | | `supabase` | Supabase database operations | | `web-search` | Web search queries | | `web-fetch` | Fetch web page content | ### MCP Server Tools MCP tools follow the pattern `{tool-name}_{server-name}`: * Example: `query_database-mcp` * Truncated to 64 characters if longer * Treated like any other tool for permissions ## Advanced Rules ### Shell Command Filtering Control which shell commands can be executed using regex patterns: ```json { "tool-permissions": [ { "tool-name": "launch-process", "shell-input-regex": "^(ls|pwd|echo|cat|grep)\\s", "permission": { "type": "allow" } }, { "tool-name": "launch-process", "permission": { "type": "deny" } } ] } ``` This configuration: 1. Allows only safe commands (ls, pwd, echo, cat, grep) 2. Denies all other shell commands 3. Rules are evaluated in order - first match wins ### Event-Based Permissions Control when permission checks occur: ```json { "tool-permissions": [ { "tool-name": "github-api", "event-type": "tool-response", "permission": { "type": "allow" } } ] } ``` **Event types:** * **`tool-call`** (default) - Check before tool execution * **`tool-response`** - Check after execution but before returning results to agent ## Interactive Approval When using `ask-user` mode in interactive sessions, Auggie displays approval prompts: ``` 🔒 Tool Approval Required ───────────────────────── Tool: launch-process Command: npm install express [A]llow once [D]eny [Always allow] [Never allow] ``` ### Keyboard Shortcuts | Key | Action | | :---- | :-------------------------- | | `A` | Allow this specific request | | `D` | Deny this specific request | | `Y` | Always allow this tool | | `N` | Never allow this tool | | `Esc` | Cancel and deny request | In non-interactive mode (--print), ask-user permissions default to deny for security. ## Common Configurations ### Read-Only Mode Allow only read operations, perfect for code review and analysis: ```json { "tool-permissions": [ { "tool-name": "view", "permission": { "type": "allow" } }, { "tool-name": "codebase-retrieval", "permission": { "type": "allow" } }, { "tool-name": "grep-search", "permission": { "type": "allow" } }, { "tool-name": "web-search", "permission": { "type": "allow" } }, { "tool-name": "web-fetch", "permission": { "type": "allow" } }, { "tool-name": "str-replace-editor", "permission": { "type": "deny" } }, { "tool-name": "save-file", "permission": { "type": "deny" } }, { "tool-name": "remove-files", "permission": { "type": "deny" } }, { "tool-name": "launch-process", "permission": { "type": "deny" } } ] } ``` ### Development Mode Add safety guards for potentially dangerous operations: ```json { "tool-permissions": [ { "tool-name": "remove-files", "permission": { "type": "ask-user" } }, { "tool-name": "launch-process", "shell-input-regex": "^(rm|sudo|chmod)\\s", "permission": { "type": "ask-user" } } ] } ``` ### CI/CD Pipeline Restrictive settings for automated workflows: ```json { "tool-permissions": [ { "tool-name": "view", "permission": { "type": "allow" } }, { "tool-name": "str-replace-editor", "permission": { "type": "allow" } }, { "tool-name": "save-file", "permission": { "type": "allow" } }, { "tool-name": "launch-process", "shell-input-regex": "^(npm test|npm run lint|jest)\\s", "permission": { "type": "allow" } }, { "tool-name": "remove-files", "permission": { "type": "deny" } }, { "tool-name": "launch-process", "permission": { "type": "deny" } } ] } ``` ## Custom Policies ### Webhook Validation Use external services to validate tool requests: ```json { "tool-permissions": [ { "tool-name": "github-api", "permission": { "type": "webhook-policy", "webhook-url": "https://api.company.com/validate-tool" } } ] } ``` The webhook receives: ```json { "tool-name": "github-api", "event-type": "tool-call", "details": { /* tool-specific data */ }, "timestamp": "2025-01-01T02:41:40.580Z" } ``` Expected response: ```json { "allow": true, "output": "Optional message to include in agent response" } ``` ### Script Validation Use local scripts for complex validation logic: ```json { "tool-permissions": [ { "tool-name": "launch-process", "permission": { "type": "script-policy", "script": "/path/to/validate-command.sh" } } ] } ``` ## Best Practices 1. **Be Explicit**: Define clear rules for all tools you want to control 2. **Layer Settings**: Use user settings for defaults, project settings for team rules 3. **Test Configurations**: Verify permissions work as expected before automation 4. **Log Decisions**: Monitor which tools are being allowed/denied for audit trails 5. **Regular Reviews**: Periodically review and update permission rules 6. **Order Matters**: Remember that rules are evaluated top-down, first match wins ## Troubleshooting **Permissions Not Working:** * Check file locations and ensure settings.json is valid JSON * Verify rule order - first matching rule wins * Use `--augment-cache-dir` to specify custom settings directory **Ask-User Mode in Automation:** * Ask-user permissions automatically deny in non-interactive mode * Use explicit allow/deny rules for automation scenarios * Consider webhook or script policies for dynamic decisions **MCP Tools Not Recognized:** * Ensure MCP server name follows `{tool}_{server}` pattern * Check for 64-character truncation on long names * Verify MCP server is properly configured and running ## Security Considerations * **Never commit sensitive webhook URLs** to version control * **Use `.augment/settings.local.json`** for personal security overrides * **Regularly audit** tool usage in production environments * **Implement defense in depth** with multiple permission layers * **Test permission changes** in isolated environments first ## Related Features * [Authentication](/cli/setup-auggie/authentication) - Secure access to Auggie * [Custom Rules](/cli/reference#custom-rules-files) - Project-specific guidelines * [MCP Integrations](/cli/integrations) - External tool configuration * [Automation](/cli/automation) - Using permissions in CI/CD # CLI Flags and Options Source: https://docs.augmentcode.com/cli/reference A comprehensive reference for all command-line flags available in the Auggie CLI. ## CLI flags | Command | Description | | :----------------- | :----------------------------------------------------------------------- | | `auggie` | Start Auggie in interactive mode | | `auggie --print` | 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 | ### Input | 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 ` | Execute a custom command from `.augment/commands/` or `~/.augment/commands/` | Custom commands are reusable instructions stored as markdown files. They can be placed in: * `~/.augment/commands/.md` - Global commands (user-wide) * `./.augment/commands/.md` - Project commands (workspace-specific) * `~/.claude/commands/.md` - Claude Code user commands * `./.claude/commands/.md` - Claude Code workspace commands Commands are resolved in order of precedence, with Auggie-specific locations taking priority over Claude Code locations. **Examples:** ```sh # 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 ``` See [Custom Commands](/cli/custom-commands) for detailed information on creating and managing custom commands. ### 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 --list-models` | List available models | | `auggie -lm` | Shorthand for `--list-models` | Tool permissions can be configured in settings.json files. See [Permissions](/cli/permissions) for detailed configuration. ### MCP and integrations | 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 | ### Authentication | Command | Description | | :----------------------------- | :------------------------------------------- | | `auggie --login` | Login to Augment and store the token locally | | `auggie --logout` | Remove the locally stored token | | `auggie --print-augment-token` | 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 | ## Custom Rules Files Auggie automatically loads custom rules and guidelines from several file locations to provide context-aware assistance. These files help Auggie understand your project's conventions, coding standards, and preferences. ### Supported Rules Files Auggie looks for rules files in the following order of precedence: 1. **Custom rules file** (via `--rules` flag): `/path/to/custom-rules.md` 2. **CLAUDE.md**: Compatible with Claude Code and other AI tools 3. **AGENTS.md**: Compatible with Cursor and other AI development tools 4. **Workspace guidelines**: `.augment/guidelines.md` (legacy format) ### File Locations **Workspace Root Files:** * `CLAUDE.md` - Root-level rules file compatible with Claude Code * `AGENTS.md` - Root-level rules file compatible with Cursor and other tools **Augment Directory Files:** * `.augment/guidelines.md` - Legacy workspace guidelines file * `.augment/rules/` - Directory containing multiple rule files (IDE feature) ### Rules File Format Rules files should be written in Markdown format with natural language instructions. Here's the recommended structure: ```markdown # Project Guidelines ## Code Style - Use TypeScript for all new JavaScript files - Follow the existing naming conventions in the codebase - Add JSDoc comments for all public functions and classes ## Architecture - Follow the MVC pattern established in the codebase - Place business logic in service classes - Keep controllers thin and focused on request/response handling ## Testing - Write unit tests for all new functions - Maintain test coverage above 80% - Use Jest for testing framework ## Dependencies - Prefer built-in Node.js modules when possible - Use npm for package management - Pin exact versions in package.json for production dependencies ``` ### Example Rules Files **Basic Project Rules (CLAUDE.md):** ```markdown # Development Guidelines - Use semantic commit messages following conventional commits - Run `npm run lint` before committing changes - Update documentation when adding new features - Follow the existing error handling patterns - Use environment variables for configuration ``` **Framework-Specific Rules (AGENTS.md):** ```markdown # React Project Guidelines ## Component Development - Use functional components with hooks - Implement proper TypeScript interfaces for props - Follow the established folder structure in src/components/ ## State Management - Use React Context for global state - Keep component state local when possible - Use custom hooks for complex state logic ## Styling - Use CSS modules for component styling - Follow the design system tokens defined in src/styles/tokens.css - Ensure responsive design for mobile and desktop ``` **Backend API Rules:** ```markdown # API Development Guidelines ## Endpoint Design - Follow RESTful conventions for URL structure - Use appropriate HTTP status codes - Include proper error messages in responses ## Database - Use Prisma ORM for database operations - Write database migrations for schema changes - Include proper indexing for query performance ## Security - Validate all input parameters - Use JWT tokens for authentication - Implement rate limiting on public endpoints ``` ### Using Custom Rules Directory You can specify a custom directory for Auggie's configuration files: ```bash # Use custom directory instead of .augment auggie --augment-cache-dir /path/to/custom-config # This will look for rules in: # /path/to/custom-config/guidelines.md # /path/to/custom-config/rules/ ``` ### Best Practices for Rules Files 1. **Be Specific**: Provide clear, actionable guidelines rather than vague suggestions 2. **Use Examples**: Include code examples when describing patterns or conventions 3. **Keep Updated**: Regularly review and update rules as your project evolves 4. **Be Concise**: Focus on the most important guidelines to avoid overwhelming the AI 5. **Test Guidelines**: Verify that Auggie follows your rules by testing with sample requests ### Compatibility with Other Tools The CLAUDE.md and AGENTS.md formats are designed to be compatible with other AI development tools: * **Claude Code**: Uses CLAUDE.md for project-specific instructions * **Cursor**: Supports AGENTS.md for AI assistant configuration * **Other AI Tools**: Many tools are adopting these standard file formats This ensures your rules work consistently across different AI development environments. # Login and authentication Source: https://docs.augmentcode.com/cli/setup-auggie/authentication You will need an active account and valid session token to use Auggie CLI which you can get by following the instructions below. ## About authentication Before you can use Auggie, you will need to login to create a session token that can be used by Auggie in both interactive and automation modes. Augment authentication tokens are secrets and should be protected with the same level of security you'd use for any sensitive credential. Tokens are tied to the user who logged in, not to your team or enterprise account, so each user has a unique augment token. ## Logging in You can login by running the following command and following the prompts. ```sh auggie --login ``` ## Logging out You can logout by running the following command. This will remove the local token from your machine and you will need to login again to use Auggie. ```sh auggie --logout ``` ## Getting your token For automation, you will need to provide your token each time you run Auggie. After you have logged in above, you can get your token by running the following command. ```sh auggie --print-augment-token ``` ## Using your token After you have your token, you can pass it to Auggie through a number of methods depending on your use case and environment. ### Environment variables You can set the `AUGMENT_SESSION_AUTH` environment variable to your token before running Auggie. Pass it before you run the command, add it to your environment, or add it to your shell's rc file to persist it. ```sh AUGMENT_SESSION_AUTH='' ``` ### Token file You can store the token as plaintext in a file and then use the `--token-file` flag to pass it to Auggie. We do not recommend checking your token into version control. ```sh auggie --token-file /path/to/token ``` ## Revoking your tokens You can expire all the tokens for the current logged in user by running the following command. Using `--logout` will only remove the local token from your machine. ```sh auggie --revoke-all-augment-tokens ``` # Install Auggie CLI Source: https://docs.augmentcode.com/cli/setup-auggie/install-auggie-cli Install Auggie to get agentic coding capabilities in your terminal, on your server, or anywhere your code runs. ```sh npm install -g @augmentcode/auggie ``` # About installing Auggie Installing Auggie CLI is easy and will take you less than a minute. You can install Auggie CLI directly from npm anywhere you can run Node 22 or later. Many systems do not ship with the latest version of Node.js, so you may need to upgrade Node to use Auggie. Auggie is currently in beta and may not run on all environments and terminal configurations. ## System requirements * [**Node.js 22+**](https://nodejs.org/en/download/) * **Platforms**: MacOS, Windows WSL, Linux * **Shells**: zsh, bash, fish ### Interactive mode Using Auggie in interactive mode requires a terminal that supports ANSI escape codes. We recommend using Ghostty, iTerm2, MacOS Terminal, Windows Terminal, Alacritty, Kitty, and other modern terminals. If you are connecting to your shell over SSH or through tmux you may need to adjust your terminal settings or configuration to enable proper color support, font rendering, and interactivity. # Workspace context Source: https://docs.augmentcode.com/cli/setup-auggie/workspace-context Auggie will automatically index the current working directory or directory you specify to give Augment a full view of your system. ## About Workspace Context Augment is powered by its deep understanding of your code. Your codebase will be automatically indexed when you run `auggie` from a git directory or you can specify a directory to index. If you run Auggie from a non-git directory, a temporary workspace will be created for you. ## Specifying a directory to index To specify a directory other than the current working directory pass the target directory to the `--workspace-root` flag. ```sh auggie --workspace-root /path/to/your/project ``` To learn more about what files are indexed and how to ignore files, see [Workspace indexing](/cli/setup-auggie/workspace-indexing). # Index your workspace Source: https://docs.augmentcode.com/cli/setup-auggie/workspace-indexing When your workspace is indexed, Augment can provide tailored code suggestions and answers based on your unique codebase, best practices, coding patterns, and preferences. You can always control what files are indexed. ## Security and privacy Augment stores your code securely and privately to enable our powerful context engine. We ensure code privacy through a proof-of-possession API and maintain strict internal data minimization principles. [Read more about our security](https://www.augmentcode.com/security). ## What gets indexed Augment will index all the files in your workspace, except for the files that match patterns in your `.gitignore` file and the `.augmentignore` file. [Read more about Workspace Context](/cli/setup-auggie/workspace-context). ## Ignoring files with .augmentignore The `.augmentignore` file is a list of file patterns that Augment will ignore when indexing your workspace. Create an `.augmentignore` file in the root of your workspace. You can use any glob pattern that is supported by the [gitignore](https://git-scm.com/docs/gitignore) file. ## Including files that are .gitignored If you have a file or directory in your `.gitignore` that you want to be indexed, you can add it to your `.augmentignore` file using the `!` prefix. For example, you may want your `node_modules` indexed to provide Augment with context about the dependencies in their project, but it is typically included in their `.gitignore`. Add `!node_modules` to your `.augmentignore` file. ```bash .augmentignore # Include .gitignore excluded files with ! prefix !node_modules # Exclude other files with .gitignore syntax data/test.json ``` ```bash .gitignore # Exclude dependencies node_modules # Exclude secrets .env # Exclude build artifacts out build ``` # Introduction Source: https://docs.augmentcode.com/introduction Augment is the developer AI platform that helps you understand code, debug issues, and ship faster because it understands your codebase. Use Chat, Next Edit, and Code Completions to get more done. export const NextEditIcon = () => ; export const CodeIcon = () => ; export const ChatIcon = () => ; Augment Code ## Get started in minutes Augment works with your favorite IDE and your favorite programming language. Download the extension, sign in, and get coding. Visual Studio Code

Visual Studio Code

Get completions, chat, and instructions in your favorite open source editor.

JetBrains IDEs

JetBrains IDEs

Completions are available for all JetBrains IDEs, like WebStorm, PyCharm, and IntelliJ.

Vim and Neovim

Vim and Neovim

Get completions and chat in your favorite text editor.

## Learn more Get up to speed, stay in the flow, and get more done. Chat, Next Edit, and Code Completions will change the way you build software. } href="/using-augment/chat"> Never get stuck getting started again. Chat will help you get up to speed on unfamiliar code. } href="/using-augment/next-edit"> Keep moving through your tasks by guiding you step-by-step through complex or repetitive changes. } href="/using-augment/completions"> Intelligent code suggestions that knows your codebase right at your fingertips. # Agent Integrations Source: https://docs.augmentcode.com/jetbrains/setup-augment/agent-integrations Configure integrations for Augment Agent to access external services like GitHub, Linear, Jira, Confluence, and Notion. export const Keyboard = ({shortcut}) => {shortcut} ; export const Command = ({text}) => {text}; export const GleanLogo = () => ; export const ConfluenceLogo = () => ; export const JiraLogo = () => ; export const NotionLogo = () => ; export const LinearLogo = () => ; export const GitHubLogo = () => ; ## About Agent Integrations Augment Agent can access external services through integrations to add additional context to your requests and take actions on your behalf. These integrations allow Augment Agent to seamlessly work with your development tools without leaving your editor. Once set up, Augment Agent will automatically use the appropriate integration based on your request context. Or, you can always mention the service in your request to use the integration. ## Setting Up Integrations To set up integrations with Augment Agent in JetBrains IDEs, follow these steps: 1. Click the Augment icon in the bottom right of your IDE and select 2. Click "Connect" for the integration you want to set up Set up integrations in the settings page You'll be redirected to authorize the integration with the appropriate service. After authorization, the integration will be available for use with Augment Agent. ## Easy MCP Integrations > **New:** Easy MCP launched ONLY July 30, 2025, providing one-click access to popular developer tools. Easy MCP transforms complex MCP server setup into a single click. Available integrations include: * **CircleCI** - Build logs, test insights, and flaky-test detection * **MongoDB** - Data exploration, database management, and context-aware code generation * **Redis** - Keyspace introspection, TTL audits, and migration helpers For detailed setup instructions and examples, see [Configure MCP servers](/jetbrains/setup-augment/mcp). ## Native Integrations ##
GitHub Integration
Add additional context to your requests and take actions. Pull in information from a GitHub Issue, make the changes to your code (or have Agent do it for you), and open a Pull Request all without leaving your editor. ### Examples * "Implement Issue #123 and open up a pull request" * "Find all issues assigned to me" * "Check the CI status of my latest commit" For authorization details, see [GitHub documentation](https://docs.github.com/en/apps/using-github-apps/installing-a-github-app-from-a-third-party). ##
Linear Integration
Read, update, comment on, and resolve your Linear issues within your IDE. ### Examples * "Fix TES-1" * "Create Linear tickets for these TODOs" * "Help me triage these new bug reports" For authorization details, see [Linear documentation](https://linear.app/docs/third-party-application-approvals). ##
Jira Integration
Work on your Jira issues, create new tickets, and update existing ones. ### Examples * "Show me all my assigned Jira tickets" * "Create a Jira ticket for this bug" * "Create a PR to fix SOF-123" * "Update the status of PROJ-123 to 'In Progress'" For authorization details, see [Jira documentation](https://support.atlassian.com/jira-software-cloud/docs/allow-oauth-access/). ##
Confluence Integration
Query existing documentation or update pages directly from your IDE. Ensure your team's knowledge base stays current without any context switching. ### Examples * "Summarize our Confluence page on microservice architecture" * "Find information about our release process in Confluence" * "Update our onboarding docs to explain how we use Bazel" For authorization details, see [Confluence documentation](https://developer.atlassian.com/cloud/confluence/oauth-2-3lo-apps/). ##
Notion Integration
Search and retrieve information from your team's knowledge base - access documentation, meeting notes, and project specifications. This integration is currently READ-ONLY. ### Examples * "Find Notion pages about our API documentation" * "Show me the technical specs for the payment system" * "What outstanding tasks are left from yesterday's team meeting?" For authorization details, see [Notion documentation](https://www.notion.so/help/add-and-manage-connections-with-the-api#install-from-a-developer). ##
Glean Integration
> **Note:** The Glean integration is in early access and thus is a little different from other integrations. > > * It is currently only available to enterprise customers. > * It does not appear in the list of integrations in the settings panel. The Glean integration lets the agent retrieve information from your team's internal data sources leveraging Glean's powerful search engine. **To Enable the Glean Integration:** You'll need to be have administrator access to Augment and Glean. Follow the instructions on [https://app.augmentcode.com/dashboard/glean](https://app.augmentcode.com/dashboard/glean) and your agent will be ready to use Glean! ### Examples * "Search Glean for past related incidents and how they were resolved" * "Search Glean for why we're migrating to a new payment processor" ## Next Steps * [Configure additional tools with Easy MCP or advanced MCP setup](/jetbrains/setup-augment/mcp) * Explore one-click integrations for CircleCI, MongoDB, and Redis through Easy MCP # Install Augment for JetBrains IDEs Source: https://docs.augmentcode.com/jetbrains/setup-augment/install-jetbrains-ides Are you ready for your new superpowers? Augment in JetBrains IDEs gives you powerful code completions integrated into your favorite text editor. export const Keyboard = ({shortcut}) => {shortcut} ; export const Command = ({text}) => {text}; export const ExternalLink = ({text, href}) => {text} ; export const JetbrainsLogo = () => ; Augment requires version `2024.3` or above for all JetBrains IDEs. [See JetBrains documentation](https://www.jetbrains.com/help/) on how to update your IDE. } horizontal> Install Augment for JetBrains IDEs ## About Installation Installing is easy and will take you less than a minute. Augment is compatible with all JetBrains IDEs, including WebStorm, PyCharm, and IntelliJ. You can find the Augment plugin in the JetBrains Marketplace and install it following the instructions below. Augment plugin in JetBrains Marketplace ## Installing Augment for JetBrains IDEs For these instructions we'll use *JetBrains IntelliJ* as an example, anywhere you see *IntelliJ* replace the name of the JetBrains IDE you're using. In the case of Android Studio, which is based on IntelliJ, please ensure that your installation uses a runtime with JCEF. Go to , type and press . Ensure the current runtime ends with `-jcef`; if not, select one **with JCEF** from the options below. You can download the latest version of JetBrains IDEs from the website. If you already have IntelliJ installed, you can update to the latest version by going to{" "} . From the menu bar, go to , or use the keyboard shortcut to open the Settings window. Select from the sidebar. Using the search bar in the Plugins panel, search for{" "} . Click to install the extension. Then click{" "} to close the Settings window. Sign in to by clicking in the Augment panel. If you do not see the Augment panel, use the shortcut{" "} or click the Augment icon{" "} in the side bar of your IDE. See more details in [Sign In](/setup-augment/sign-in). ## Installing Beta versions of Augment for JetBrains IDEs In order to get a specific bug fix or feature, sometimes you may need to *temporarily* install a beta version of Augment for JetBrains IDEs. To do this, follow the steps below: You can download the latest beta version of Augment from website. Please click on the latest version and save the archive to disk. From the menu bar, go to , or use the keyboard shortcut to open the Settings window. Select from the sidebar. Click on the gear icon next to tab and click . Select the archive you downloaded in the previous step and click . # Keyboard Shortcuts for JetBrains IDEs Source: https://docs.augmentcode.com/jetbrains/setup-augment/jetbrains-keyboard-shortcuts Augment integrates with your IDE to provide keyboard shortcuts for common actions. Use these shortcuts to quickly accept suggestions, write code, and navigate your codebase. export const Keyboard = ({shortcut}) => {shortcut} ; export const Command = ({text}) => {text}; ## About keyboard shortcuts Augment is deeply integrated into your IDE and utilizes many of the standard keyboard shortcuts you are already familiar with. These shortcuts allow you to quickly accept suggestions, write code, and navigate your codebase. We also suggest updating a few keyboard shortcuts to make working with code suggestions even easier. To update keyboard shortcuts, use one of the following: | Method | Action | | :------- | :------------------------------------------------------------- | | Keyboard | select | | Menu bar | | ## General | Action | Default shortcut | | :----------------- | :----------------------------------- | | Open Augment panel | | ## Chat | Action | Default shortcut | | :----------------------- | :----------------------------------- | | Focus or open Chat panel | | ## Completions | Action | Default shortcut | | :--------------------------- | :----------------------------------- | | Accept entire suggestion | | | Accept word-by-word | | | Reject suggestion | | | Toggle automatic completions | | To update keyboard shortcuts, use one of the following: | Method | Action | | :------- | :------------------------------------------------------------------- | | Keyboard | then select | | Menu bar | | ## General | Action | Default shortcut | | :----------------- | :--------------------------------- | | Open Augment panel | | ## Chat | Action | Default shortcut | | :----------------------- | :--------------------------------- | | Focus or open Chat panel | | ## Completions | Action | Default shortcut | | :--------------------------- | :--------------------------------- | | Accept entire suggestion | | | Accept word-by-word | | | Reject suggestion | | | Toggle automatic completions | | # Setup Model Context Protocol servers Source: https://docs.augmentcode.com/jetbrains/setup-augment/mcp Use Model Context Protocol (MCP) servers with Augment to expand Augment's capabilities with external tools and data sources. export const Command = ({text}) => {text}; export const Keyboard = ({shortcut}) => {shortcut} ; ## About Model Context Protocol servers Augment Agent can utilize external integrations through Model Context Protocol (MCP) to access external systems for information and integrate tools to take actions. MCP is an open protocol that provides a standardized way to connect AI models to different data sources and tools. MCP servers can be used to access local or remote databases, run automated browser testing, send messages to Slack or even play music on Spotify. ## Easy MCP: One-Click Integrations > **New:** Easy MCP launched on July 30, 2025, making it easier than ever to connect popular developer tools to Augment Code. Easy MCP is a new feature in the Augment Code extension that transforms complex MCP server setup into a single click. Instead of manually configuring servers, hunting for GitHub repos, or editing JSON files, you can now connect popular developer tools with just an API token or OAuth approval. ### Available Easy MCP Integrations Easy MCP provides one-click access to these popular developer tools: #### CircleCI * **Context:** Build logs, test insights, flaky-test detection * **Sample prompt:** "Find the latest failed pipeline on my branch and surface the failing tests." * **Setup:** Click "+", paste your CircleCI API token, and you're connected. #### MongoDB * **Context:** Data exploration, database management, and context-aware code generation * **Sample prompt:** "Analyze my user collection schema and suggest optimizations for our new search feature." * **Setup:** One-click OAuth connection to your MongoDB instance. #### Redis * **Context:** Keyspace introspection, TTL audits, and migration helpers * **Sample prompt:** "Generate a migration script to move expiring session keys to the new namespace." * **Setup:** Connect with your Redis credentials in seconds. ### Getting Started with Easy MCP 1. Open the Augment Code extension in your JetBrains IDE 2. Navigate to the Easy MCP pane in the settings 3. Click the "+" button next to your desired integration 4. Paste an API token or approve OAuth 5. Start using the integration immediately in your Agent conversations From that moment on, Augment Code streams your tool's live context into every suggestion and autonomous Agent run. ## Advanced Configuration: Settings Panel For developers who need custom MCP server configurations or want to use servers not available through Easy MCP, you can configure MCP servers manually using the Augment Settings Panel. To access the settings panel, select the gear icon in the upper right of the Augment panel. Once the settings panel is open, you will see a section for MCP servers. Fill in the `name` and `command` fields. The `name` field must be a unique name for the server. The `command` field is the command to run the server. Environment variables have their own section and no longer need to be specified in the command. To add additional servers, click the `+` button next to the `MCP` header. To edit a configuration or to delete a server, click the `...` button next to the server name. ### Add a Remote MCP server If your MCP server runs remotely (for example, a hosted service), click the "+ Add remote MCP" button in the MCP section. Remote MCP connections support both HTTP and SSE (Server‑Sent Events). * Connection Type: choose HTTP or SSE * Name: a unique display name for the server * URL: the base URL to your MCP server (e.g., [https://api.example.com](https://api.example.com)) Remote MCP servers appear alongside your local MCP servers in the list. You can edit or remove them using the "..." menu next to the server name. ## Server compatibility Not all MCP servers are compatible with Augment's models. The MCP standard, implementation of specific servers, and Augment's MCP support are frequently being updated, so check compatibility frequently. # Index your workspace Source: https://docs.augmentcode.com/jetbrains/setup-augment/workspace-indexing When your workspace is indexed, Augment can provide tailored code suggestions and answers based on your unique codebase, best practices, coding patterns, and preferences. You can always control what files are indexed. ## About indexing your workspace When you open a workspace with Augment enabled, your codebase will be automatically uploaded to Augment's secure cloud. You can control what files get indexed using `.gitignore` and `.augmentignore` files. Indexing usually takes less than a minute but can take longer depending on the size of your codebase. ## Security and privacy Augment stores your code securely and privately to enable our powerful context engine. We ensure code privacy through a proof-of-possession API and maintain strict internal data minimization principles. [Read more about our security](https://www.augmentcode.com/security). ## What gets indexed Augment will index all the files in your workspace, except for the files that match patterns in your `.gitignore` file and the `.augmentignore` file. ## Ignoring files with .augmentignore The `.augmentignore` file is a list of file patterns that Augment will ignore when indexing your workspace. Create an `.augmentignore` file in the root of your workspace. You can use any glob pattern that is supported by the [gitignore](https://git-scm.com/docs/gitignore) file. ## Including files that are .gitignored If you have a file or directory in your `.gitignore` that you want to indexed, you can add it to your `.augmentignore` file using the `!` prefix. For example, you may want your `node_modules` indexed to provide Augment with context about the dependencies in their project, but it is typically included in their `.gitignore`. Add `!node_modules` to your `.augmentignore` file. ```bash .augmentignore # Include .gitignore excluded files with ! prefix !node_modules # Exclude other files with .gitignore syntax data/test.json ``` ```bash .gitignore # Exclude dependencies node_modules # Exclude secrets .env # Exclude build artifacts out build ``` # Using Agent Source: https://docs.augmentcode.com/jetbrains/using-augment/agent Use Agent to complete simple and complex tasks across your workflow–implementing a feature, upgrade a dependency, or writing a pull request. export const type_0 = "changes" export const AtIcon = () =>
; ## About Agent Augment Agent is a powerful tool that can help you complete software development tasks end-to-end. From quick edits to complete feature implementation, Agent breaks down your requests into a functional plan and implements each step all while keeping you informed about what actions and changes are happening. Powered by Augment's Context Engine and powerful LLM architecture, Agent can write, document, and test like an experienced member of your team. ## Accessing Agent To access Agent, simply open the Augment panel and select one of the Agent modes from the drop down in the input box. Augment Agent ### Choosing a model Use the model dropdown in the Augment panel to switch between Claude Sonnet 4 and GPT-5. Your selection applies only to Agent for the current workspace and can be changed at any time. See [Available Models](/models/available-models) for details. ## Using Agent To use Agent, simply type your request into the input box using natural language and click the submit button. You will see the default context including current workspace, current file, and Agent memories. You can add additional context by clicking and selecting files or folder, or add an image as context by clicking the paperclip. Agent can create, edit, or delete code across your workspace and can use tools like the terminal and external integrations through MCP to complete your request. ### Enhancing your prompt You can improve the quality of your {type_0} by starting with a well crafted prompt. You can start with a quick or incomplete prompt and use the prompt enhancer to add relevant references, structure, and conventions from your codebase to improve the prompt before it is sent. 1. Write your prompt in the prompt input box 2. Click the Enhance Prompt ✨ button 3. Review and edit the enhanced prompt 4. Submit your prompt ### Reviewing changes You can review every change Agent makes by clicking on the action to expand the view. Review diffs for file changes, see complete terminal commands and output, and the results of external integration calls. Augment Agent ### Checkpoints Checkpoints are automatically saved snapshots of your workspace as Agent implements the plan allowing you to easily revert back to a previous step. This enables Agent to continue working while you review code changes and commands results. To revert to a previous checkpoint, click the reverse arrow to restore your code. Augment Agent ### Agent vs Agent Auto By default, Agent will pause work when it needs to execute a terminal command or access external integrations. After reviewing the suggested action, click the blue play button to have Agent execute the command and continue working. You tell Agent to skip a specific action by clicking on the three dots and then Skip. Augment Agent In Agent Auto, Agent will act more independently. It will edit files, execute terminal commands, and access tools like MCP servers automatically. ### Stop or guide the Agent You can interrupt the Agent at any time by clicking Stop. This will pause the action to allow you to correct something you see the agent doing incorrectly. While Agent is working, you can also prompt the Agent to try a different approach which will automatically stop the agent and prompt it to correct its course. Stopping the agent ### Quick Ask Mode Quick Ask Mode is a toggle button in the agent chat interface that restricts the AI to read-only tools only. When activated, it adds a visual badge to the message and focuses the AI on information gathering without making any changes to your codebase. Quick Ask Mode toggle and usage ### Comparison to Chat Agent takes Chat to the next level by allowing Augment to do things for you-that is create and make modifications directly to your codebase. Chat can explain code, create plans, and suggest changes which you can smartly apply one-by-one, but Agent takes it a step further by automatically implementing the entire plan and all code changes for you. | What are you trying to do? | Chat | Agent | | :----------------------------------------------- | :--: | :---: | | Ask questions about your code | ☑️ | ✅ | | Get advice on how to refactor code | ☑️ | ✅ | | Add new features to selected lines of code | ☑️ | ✅ | | Add new feature spanning multiple files | | ✅ | | Document new features | | ✅ | | Queue up tests for you in the terminal | | ✅ | | Open Linear tickets or start a pull request | | ✅ | | Start a new branch in GitHub from recent commits | | ✅ | | Automatically perform tasks on your behalf | | ✅ | ### Use cases Use Agent to handle various aspects of your software development workflow, from simple configuration changes to complex feature implementations. Agent supports your daily engineering tasks like: * **Make quick edits** - Create a pull request to adjust configuration values like feature flags from FALSE to TRUE * **Perform refactoring** - Move functions between files while maintaining coding conventions and ensuring bug-free operation * **Start a first draft for new features** - Start a pull request (PR) with implementing entirely new functionality straight from a GitHub Issue or Linear Ticket * **Branch from GitHub** - Open a PR from GitHub based on recent commits that creates a new branch * **Query Supabase tables directly** - Ask Agent to view the contents of a table * **Start tickets in Linear or Jira** - Open tickets and ask Agent to suggest a plan to address the ticket * **Add Pull Request descriptions** - Merge your PR into a branch then tell the agent to explain what the changes are and why they were made * **Create test coverage** - Generate unit tests for your newly developed features * **Generate documentation** - Produce comprehensive documentation for your libraries and features * **Start a README** - Write a README for a new feature or updated function that you just wrote * **Track development progress** - Review and summarize your recent Git commits for better visibility with the GitHub integration ## Next steps * [Configure Agent Integrations](/jetbrains/setup-augment/agent-integrations) # Using Chat Source: https://docs.augmentcode.com/jetbrains/using-augment/chat Use Chat to explore your codebase, quickly get up to speed on unfamiliar code, and get help working through a technical problem. export const type_0 = "chats" export const DeleteIcon = () =>
; export const ChevronRightIcon = () =>
; export const NewChatIcon = () =>
; export const Keyboard = ({shortcut}) => {shortcut} ; export const Command = ({text}) => {text}; ## About Chat Chat is a new way to work with your codebase using natural language. Chat will automatically use the current workspace as context and you can [provide focus](/using-augment/chat-context) for Augment by selecting specific code blocks, files, folders, or external documentation. Details from your current chat, including the additional context, are used to provide more relevant code suggestions as well. Augment Chat ## Accessing Chat Access the Chat sidebar by clicking the Augment icon in the sidebar or the status bar. You can also open Chat by using one of the keyboard shortcuts below. **Keyboard Shortcuts** | Platform | Shortcut | | :------------ | :----------------------------- | | MacOS | | | Windows/Linux | | ## Using Chat To use Chat, simply type your question or command into the input field at the bottom of the Chat panel. You will see the currently included context which includes the workspace and current file by default. Use Chat to explain your code, investigate a bug, or use a new library. See [Example Prompts for Chat](/using-augment/chat-prompts) for more ideas on using Chat. ### Enhancing your prompt You can improve the quality of your {type_0} by starting with a well crafted prompt. You can start with a quick or incomplete prompt and use the prompt enhancer to add relevant references, structure, and conventions from your codebase to improve the prompt before it is sent. 1. Write your prompt in the prompt input box 2. Click the Enhance Prompt ✨ button 3. Review and edit the enhanced prompt 4. Submit your prompt ### Conversations about code To get the best possible results, you can go beyond asking simple questions or commands, and instead have a back and forth conversation with Chat about your code. For example, you can ask Chat to explain a specific function and then ask follow-up questions about possible refactoring options. Chat can act as a pair programmer, helping you work through a technical problem or understand unfamiliar code. ### Starting a new chat You should start a new Chat when you want to change the topic of the conversation since the current conversation is used as part of the context for your next question. To start a new chat, open the Augment panel and click the new chat icon at the top-right of the Chat panel. ### Previous chats You can continue a chat by clicking the chevron iconat the top-left of the Chat panel. Your previous chats will be listed in reverse chronological order, and you can continue your conversation where you left off. ### Deleting a chat You can delete a previous chat by clicking the chevron iconat the top-left of the Chat panel to show the list of previous chats. Click the delete icon next to the chat you want to delete. You will be asked to confirm that you want to delete the chat. # Using Actions in Chat Source: https://docs.augmentcode.com/jetbrains/using-augment/chat-actions Actions let you take common actions on code blocks without leaving Chat. Explain, improve, or find everything you need to know about your codebase. export const ArrowUpIcon = () =>
; export const Keyboard = ({shortcut}) => {shortcut} ; Augment Chat Actions ## Using actions in Chat To use a quick action, you an use a command or click the up arrow iconto show the available actions. For explain, fix, and test actions, first highlight the code in the editor and then use the command. | Action | Usage | | :------------------------------- | :----------------------------------------------------------------------- | | | Use natural language to find code or functionality | | | Augment will explain the hightlighted code | | | Augment will suggest improvements or find errors in the highlighted code | | | Augment will suggest tests for the highlighted code | Augment will typically include code blocks in the response to the action. See [Applying code blocks from Chat](/using-augment/chat-apply) for more details. # Applying code blocks from Chat Source: https://docs.augmentcode.com/jetbrains/using-augment/chat-apply Use Chat to explore your codebase, quickly get up to speed on unfamiliar code, and get help working through a technical problem. export const Availability = ({tags}) => { const tagTypes = { invite: { styles: "bg-gray-700 text-white dark:border-gray-50/10" }, beta: { styles: "border border-zinc-500/20 bg-zinc-50/50 dark:border-zinc-500/30 dark:bg-zinc-500/10 text-zinc-900 dark:text-zinc-200" }, vscode: { styles: "border border-sky-500/20 bg-sky-50/50 dark:border-sky-500/30 dark:bg-sky-500/10 text-sky-900 dark:text-sky-200" }, jetbrains: { styles: "border border-amber-500/20 bg-amber-50/50 dark:border-amber-500/30 dark:bg-amber-500/10 text-amber-900 dark:text-amber-200" }, vim: { styles: "bg-gray-700 text-white dark:border-gray-50/10" }, neovim: { styles: "bg-gray-700 text-white dark:border-gray-50/10" }, default: { styles: "bg-gray-200" } }; return
Availability {tags.map(tag => { const tagType = tagTypes[tag] || tagTypes.default; return
{tag}
; })}
; }; export const MoreVertIcon = () =>
; export const CheckIcon = () =>
; export const FileNewIcon = () =>
; export const FileCopyIcon = () =>
; Augment Chat Apply ## Using code blocks from within Chat Whenever Chat responds with code, you will have the option to add the code to your codebase. The most common option will be shown as a button and you can access the other options by clicking the overflow menu iconat the top-right of the code block. You can use the following options to apply the code: * **Copy** the code from the block to your clipboard * **Create** a new file with the code from the block * **Apply** the code from the block intelligently to your file # Focusing Context in Chat Source: https://docs.augmentcode.com/jetbrains/using-augment/chat-context You can specify context from files, folders, and external documentation in your conversation to focus your chat responses. export const AtIcon = () =>
; export const Command = ({text}) => {text}; ## About Chat Context Augment intelligently includes context from your entire workspace based on the ongoing conversation–even if you don't have the relevant files open in your editor–but sometimes you want Augment to prioritize specific details for more relevant responses.