Skip to content

v0.12.2: MCP ablation and Windows launchers

Choose a tag to compare

@edonadei edonadei released this 21 Sep 02:33

Caliper v0.12.2 adds MCP-server ablation and fixes CLI startup and judge-error handling.

MCP servers can be ablated (#109)

caliper run --ablate <name> now removes a declared MCP server as well as a skill. Use --ablate mcp:<name> or --ablate skill:<name> when names overlap. Runs record configured MCP-server membership, and compare warns when that membership differs outside a recognized ablation pair. Older results remain readable, with unrecorded membership treated as unknown.

Windows Node-based launchers start correctly (#114)

Attempt environments now preserve SystemRoot on Windows, fixing the ncrypto::CSPRNG(nullptr, 0) startup crash seen with Codex and pi npm launchers. Verified with a passing Codex/Luna evaluation on Windows. This fixes the startup portion of #112; Codex home selection and UTF-8 file handling remain outstanding.

Codex judge failures retain their failure classification (#108)

A nonzero Codex judge exit now carries a typed failure, allowing the judge to handle it consistently with other CLI failures.

Cross-platform regression coverage

Every PR now runs the full test suite on Linux and macOS, plus the shared CLI harness suite and a real Node startup check on Windows. Agent calls in CI are faked and require no model credentials.

Full changelog: v0.12.1...v0.12.2