This release fixes issues for SREs watching stability and regressions.
✓ No known CVEs patched in this version
Topics
+13 more
Summary
AI summaryFixes validation so spend‑limit requests with engine "gemini" are no longer rejected.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Bugfix | Medium |
Accepts engine: "gemini" with budget fields in martin_run, martin_preflight, and martin_doctor. Accepts engine: "gemini" with budget fields in martin_run, martin_preflight, and martin_doctor. Source: llm_adapter@2026-06-13 Confidence: high |
— |
Full changelog
@martinloop/mcp 0.3.2
0.3.2 is a validation hotfix for the standalone MartinLoop MCP server.
Release story
Fix a tool-input validation gap that could reject valid spend-limit requests.
What changed
martin_run,martin_preflight, andmartin_doctornow acceptengine: "gemini", matching the engines the run loop already supports.- Previously, any call that combined
engine: "gemini"with a budget field (for examplemaxUsd) was rejected withInvalid engine., even though Gemini-backed runs were otherwise fully supported. - No other tool inputs, defaults, or behaviors changed.
Why this matters
If you set a spend limit or budget for a Gemini-backed run through the MCP tools, that request now validates correctly instead of being rejected.
Out of scope
- opt-in execution controls (planned for
0.3.3) - new tools or schema fields
- changes to budget enforcement behavior
Release gate
Setting a spend limit on any supported engine - Claude, Codex, or Gemini - through martin_run, martin_preflight, or martin_doctor must validate successfully.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About Keesan12/Martin-Loop
All releases →Related context
Related tools
Earlier breaking changes
- vmcp-v0.1.3 martin_status uses oneOf for selector exclusivity, latest as const.
- vmcp-v0.1.3 maxIterations and maxTokens modeled as integers in tool schemas.
- vmcp-v0.1.3 Tool schemas enforce additionalProperties: false on public contracts.
- vmcp-v0.1.3 Packaged artifacts now require and ship server.json alongside package.json.
Beta — feedback welcome: [email protected]