Introduction
GitHub Repository
Report issues, leave feature requests and view custom workflows for Auggie CLI
NPM Package
Install Auggie CLI from npm
- 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 20 or later installed
- A compatible shell like zsh, bash, fish
Auggie 1.x is a prerelease and is published under the
prerelease tag on npm. Auggie 0.x is published under the v0-release tag. See What’s new in Auggie 1.x for changes from 0.x.1
Install Auggie with npm
2
Go to your project directory
3
Login or sign up to Augment
auggie auth login and follow the prompts.4
Start using Auggie
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
Runauggie 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
Non-interactive mode is an additional feature that may be disabled if it is not included in your agreement (enterprise).
--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.
Output modes: In print mode, Auggie prints the final response by default, followed by a Request ID line (used for support). Use --mode stream to see text and tool activity as it happens, or --mode json for structured output without the Request ID line.