AGENTIC QE V3.8.8 SHIPS MCP‑FREE AGENTS, A MEMORY CLI, AND WASM PARSERS
Agentic QE v3.8.8 removes the hard MCP dependency, adds a memory CLI, and brings cross-language WASM parsers. Per the release notes, agents and skills now run ...
Agentic QE v3.8.8 removes the hard MCP dependency, adds a memory CLI, and brings cross-language WASM parsers.
Per the release notes, agents and skills now run without an MCP server, with 431 MCP tool calls replaced by CLI commands and MCP made opt‑in v3.8.8. You can still enable it via aqe init --with-mcp or claude mcp add aqe -- aqe-mcp if needed.
A new aqe memory CLI adds seven subcommands (store, get, search, list, delete, share, usage), letting agents read and write memory without an MCP server release.
The update also includes WASM parsers for Python, Java, C#, Rust, and Swift, avoiding native binaries, plus standardized kebab‑case skill names and improved activation triggers details.
You can run agents without deploying or operating an MCP server, shrinking operational overhead and simplifying local and CI environments.
WASM parsers deliver portable cross-language code intelligence, reducing native build complexity and platform-specific breakage.
-
terminal
Run agents with MCP disabled; verify aqe memory store/get/search in CI and on an air‑gapped host, and confirm expected access controls for share/usage.
-
terminal
Benchmark WASM parsers vs your current native parsers for Python/Java/C#/Rust/Swift; measure startup time, throughput, and memory footprint.
Legacy codebase integration strategies...
- 01.
If your automation relied on aqe init auto‑configuring MCP, update scripts to pass --with-mcp or remove the dependency entirely.
- 02.
Audit any references to old skill names and MCP tool calls; map to kebab‑case skills and aqe CLI wrappers, and update logs/RBAC around memory share.
Fresh architecture paradigms...
- 01.
Start MCP‑free to cut infra and run ephemeral agents in containers with simpler networking and fewer moving parts.
- 02.
Adopt the memory CLI for lightweight task context persistence and use WASM parsers to keep builds portable across OS/CPU.