Mighty Max v0.3.3

Full Changelog: v0.3.2...v0.3.3

Mighty Max 0.3.2 — server-terminated connection retries

Covers 0.3.1 + 0.3.2 (0.3.1 was version-bumped but never released).

Fixed

Server-terminated connections (TypeError: terminated) are now retried

When the MiniMax server closes the socket mid-request — observed on a large (352-message) request, surfacing as MiniMax API error (network): terminated with zero retries — the failure now engages the transport's retry machinery:

• isRetriableNetworkError walks the error's cause chain, so undici's TypeError: terminated / fetch failed wrappers (which carry the socket-level ECONNRESET / UND_ERR_SOCKET code on .cause, never on the thrown error itself) are recognized as transient. Bare terminated errors with no cause are matched by message.
• The SSE parsers mark mid-stream network failures retriable, so a body that errors before delivering any event is re-issued transparently by the before-first-event retry driver. Post-first-event terminations still surface immediately (a retry would duplicate delivered content).
• The chat error for network failures now explains that the connection dropped and safe retries were exhausted, instead of the bare envelope.

Four-test regression suite in transport.test.ts ("server-terminated connections").

Deprecated managementCommand replaced with the new configuration schema

VS Code 1.109+ flags contributes.languageModelChatProviders[*].managementCommand as deprecated. The provider entry now uses the new configuration.properties block with apiKey as a secret: true string setting (routed through SecretStorage). The mightyMax.manage command remains registered and is still the authoritative write path for the API key.

Full changelog: https://github.com/greysquirr3l/mightymax-vscode/blob/main/CHANGELOG.md

Mighty Max 0.2.3 — Token Plan usage indicator

T27 — Token Plan usage indicator

A right-side status-bar item (the Mighty Max aviator glyph) now mirrors the MiniMax Token Plan usage bar that's normally only visible at platform.minimax.io. Hover for per-window progress bars; click — or run Mighty Max: Show MiniMax Usage — for the full panel with refresh and a collapsible raw-response disclosure for diagnosing schema drift.

What ships

• $(mightymax-head) status-bar item with neutral / warning / error tints at the 0–79% / 80–99% / 100% thresholds
• 5-minute polling with out-of-band refresh on API-key change
• mightyMax.showUsage command + compact webview
• UsageClient port with UsageUnavailableError (kind: 'unavailable' | 'network' | 'parse', retriable: boolean) — PAYG keys and network blips stay neutral, never red
• Pure-domain usage-normalization.ts with fixture coverage for the four core invariants

Bundle size

	0.2.2	0.2.3
.vsix size	8.57 MB	479.67 kB (~18× smaller)
Hero logo in README	8.9 MB	145 kB

The .vscodeignore now excludes the unreferenced 8.9 MB logo and lets the 145 kB README variant through. tmp/ is also excluded from both git tracking and the packaged bundle.

Verified

• npm run lint — clean
• npm run typecheck — clean
• 7/7 CI checks green on 3b3b951 (Build & test on ubuntu/macos/windows, NPM Audit, Gitleaks, Scorecard, TypeScript analysis)
• vsce package content reviewed against the .vscodeignore deny list

Merged via PR #23.

v0.1.4 — Smart Tool Filtering & Thinking Passback

What's new in 0.1.4

Added

• Smart tool filtering: Fixes M3 tool-calling failures when 80+ tools are present (common in MCP-heavy VS Code setups). Automatically scores and trims the tool set per request using keyword relevance, historical usage frequency, or a hybrid of both. New settings: mightyMax.enableSmartToolFiltering, mightyMax.maxTools (default 30), mightyMax.alwaysIncludeTools, mightyMax.toolFilterStrategy. See SMART_TOOL_FILTERING.md for details.
• Thinking block passback cache: Re-injects thinking blocks with Anthropic signatures into enriched messages before each request, preserving M3 extended-thinking round-trips across VS Code history reconstruction.
• Capability validation guards: evaluateAgentEligibility now rejects non-boolean capability flags with typed reasons.
• callId validation: validateMessages emits a missing-tool-call-id error for tool-call/result parts without a callId.

Changed

• Streaming log line raised to info; includes toolMode and full tool name list.
• StartStreamingRequest port now carries optional thinking config (type, budgetTokens).

Full changelog: https://github.com/greysquirr3l/mightymax-vscode/blob/main/CHANGELOG.md

Mighty Max v0.1.2

Full Changelog: v0.1.1...v0.1.2

Mighty Max v0.1.1

What's Changed

• chore(ci): bump actions/checkout from 4.3.1 to 6.0.3 by @dependabot[bot] in #1
• chore(ci): bump actions/dependency-review-action from 4.9.0 to 5.0.0 by @dependabot[bot] in #2
• chore(ci): bump actions/download-artifact from 4.3.0 to 8.0.1 by @dependabot[bot] in #3
• chore(deps)(deps-dev): bump mocha from 10.8.0 to 11.7.6 by @dependabot[bot] in #5
• chore(deps)(deps-dev): bump @types/node from 20.17.6 to 25.9.2 by @dependabot[bot] in #7
• chore(deps)(deps-dev): bump typescript from 5.6.3 to 6.0.3 by @dependabot[bot] in #8

New Contributors

• @dependabot[bot] made their first contribution in #1

Full Changelog: v0.1.0...v0.1.1

Mighty Max v0.1.0

Full Changelog: https://github.com/greysquirr3l/mightymax-vscode/commits/v0.1.0