Supercharge your website and app testing with next‑generation AI automation. QLOOD‑CLI is a preconfigured wrapper around the AugmentCode (Auggie) CLI that thinks like a user, tests like a pro, and catches what humans miss.
Links:
- Qlood: https://qlood.com
- AugmentCode: https://augmentcode.com
- Auggie automation docs: https://docs.augmentcode.com/cli/automation
- QLOOD‑CLI is pre‑prompted to run specific tests for your app
- Orchestrates multiple Auggie CLI runs
- Executes tasks with
auggie --print "Our prompt" - Launches Playwright (non‑interactive) to test your app and capture screenshots
- Auggie drafts results: Errors, Warnings, Success
- Auggie analyzes your project and generates a fix prompt automatically
In short: a streamlined auggie --print "Our prompt" wrapper with pre‑made prompts that achieve your goal.
Learn more: https://www.augmentcode.com/
Disclaimer: Using QLOOD‑CLI may require an AI provider API key and an AugmentCode.com account. Running the tool may use your real credits on connected services.
-
Install (global):
npm install -g qlood-cli
-
Launch the CLI:
qlood
-
Show all commands (inside the TUI):
/help
QLOOD-CLI supports multiple AI agents. Switch between them anytime mid-conversation:
| Command | Agent | Description |
|---|---|---|
/auggie |
Auggie | AugmentCode CLI (default) |
/cc |
Claude Code | Anthropic's Claude Code CLI |
/gemini |
Gemini CLI | Google's Gemini CLI |
/opencode |
OpenCode | Open-source AI coding assistant |
/kilo |
Kilo Code CLI | Open-source AI coding assistant |
All commands (/review, /refactor, /reviewrepo, etc.) work with whichever agent is currently selected.
Codebase Context: All agents (except Auggie, which has it built-in) are automatically instructed to use the codebase-retrieval tool when searching the codebase. This requires MCP configuration. See docs/CODEBASE_RETRIEVAL_INSTRUCTION.md for details.
# Example: Switch to Kilo and run a refactor analysis
/kilo
/refactor| Command | Description |
|---|---|
/review |
Run all reviews (repo + app + build) |
/reviewrepo |
Repository & supply chain review |
/reviewapp |
Application code & config review |
/reviewbuild |
Build / CI/CD / IaC review |
/refactor |
Find largest files/functions & generate report |
/new |
Start a new conversation |
/status |
Show session info |
/help |
Show all available commands |
/quit |
Exit QLOOD-CLI |
Full documentation: https://qlood.com/docs
What QLOOD tests (automatically):
- End‑to‑end, user‑like flows
- UI/UX checks and obvious anti‑patterns
- Console log auditing
- Network performance signals and failures
- Security/vulnerability scans (basic heuristics)
- Auth flow validation
- Dead link detection and navigation problems
- API key exposure hints and URL rewrite safety
- Node.js 18+
- Auggie CLI installed and authenticated:
auggie --login
- QLOOD initializes a project‑local
./.qlood/folder and uses Auggie (via MCP Playwright) to drive a headless browser. - You’ll be prompted to initialize on first run. Accepting allows Auggie to index your project for context‑aware testing.
- Credentials should be provided via environment variables or a gitignored
.envfile.
MIT