agentic-qe

Agentic Quality Engineering Fleet

---

What AQE Does For You

• Generates comprehensive tests automatically — unit, integration, property-based, and BDD scenarios for your codebase with framework-specific output (Jest, Vitest, Playwright, Cypress, pytest, JUnit, Go, Rust, Swift, Flutter, and more)
• Finds coverage gaps and prioritizes what to test — risk-weighted analysis identifies the most impactful untested code paths
• Detects and fixes flaky tests — ML-powered detection with root cause analysis and stabilization recommendations
• Learns your codebase patterns over time — remembered patterns are reused across sessions and projects, improving with every interaction
• Coordinates 60 specialized QE agents — from test generation to security scanning to chaos engineering, orchestrated by a central coordinator
• Reduces AI costs with intelligent routing — automatically routes tasks to the right model tier (fast/cheap for simple tasks, powerful for complex ones)
• Works with your existing tools — integrates with 11 coding agent platforms and your existing CI/CD pipeline

---

Quick Start

# Install
npm install -g agentic-qe

# Initialize your project (auto-detects tech stack, configures MCP)
cd your-project && aqe init --auto

# That's it — MCP tools are available immediately in Claude Code
# For other clients: aqe-mcp

After init, your coding agent can use AQE tools directly. For example in Claude Code:

"Generate tests for src/services/UserService.ts with 90% coverage target"
"Find coverage gaps in src/ and prioritize by risk"
"Run security scan on the authentication module"
"Analyze why tests in auth/ are flaky and suggest fixes"

Windows install

agentic-qe runs on Windows, but several of its performance-oriented native dependencies (hnswlib-node for HNSW search, @ruvector/gnn for graph neural networks, @ruvector/rvf-node for the RVF pattern store) ship as optional native modules. hnswlib-node in particular has no prebuilt binaries and compiles from source via node-gyp. npm install does not fail when these modules can't build — they're declared optional and AQE falls back to JavaScript paths at runtime.

Important caveat about the fallback. The pure-JavaScript HNSW fallback (ProgressiveHnswBackend) is correct but degrades to O(N) brute-force search when neither hnswlib-node nor @ruvector/gnn is available. That's fine for small projects but unsuitable for large indexes (tens of thousands of vectors and up). If you plan to run AQE against a sizeable codebase on Windows, install the native build toolchain so hnswlib-node compiles:

• Python 3 (added to PATH), and
• Visual Studio 2022 Build Tools with the Desktop development with C++ workload — works with any node-gyp version, or
• Visual Studio 2026 with the same workload plus an upgraded npm (npm install -g npm@latest — VS 2026 detection requires npm ≥ 11.6.3, shipped via node-gyp ≥ 12.1.0). Node 22 LTS still ships npm 10.x by default, which cannot detect VS 2026; either upgrade npm globally or use VS 2022 Build Tools instead.

If the native dep fails to build you'll see a node-gyp warning during install (e.g. gyp ERR! find VS); the install itself completes. To verify which backend is active:

aqe health
# Look for "HNSW backend: native" (hnswlib-node) or "HNSW backend: js"
# (ProgressiveHnswBackend — see caveat above).

Linux and macOS users: no extra setup required. The native binary compiles out of the box.

---

Claude Code Plugin (Alternative Install)

If you only need a slim, scoped fleet inside Claude Code — without the full aqe init setup — install the agentic-qe-fleet plugin. It bundles 11 specialized QE agents, 9 slash commands, 9 skills, and auto-registers the MCP server.

Install from a local checkout