v2.1.1
Released 2026-08-25Highlights
- Cancelled remote HTTP calls no longer release their connection-pool slot before the background transport finishes, eliminating an intermittent protocol and routing failure after cancellation.
- Power-Boost catalog changes are now delivered to active AI sessions through real MCP notifications. The stale state where the UI showed 237 tools while AI remained at 189 is fixed.
- Two stable compatibility tools provide bounded search over the complete live catalog and safe dispatch to a selected tool, keeping tools reachable even when a client limits direct tools.
- Concurrent HTTP tool calls no longer queue behind one connection; a bounded persistent connection pool reduces latency.
- Hanging tool calls are fixed: when an MCP server sends a request to the app (for example ping) it now always gets a reply. Previously such requests went unanswered, the server kept waiting, and the call stayed pending until the 300-second ceiling.
- When an MCP server stops reading its input, the call now fails with a clear error within the given timeout; previously it could wait forever without ever hitting a timeout.
- Tool calls with large arguments are noticeably faster: the roughly 12 ms summarisation cost paid on the response path for a 5 MB argument is gone, and the cost no longer depends on input size.
Fixes
- Backup listing, backup preview, diagnostics ZIP creation and folder launch now run outside the gateway event loop. Large logs or backup histories no longer pause concurrent tool calls, and broken archives no longer fail the entire list.
- The explicitly selected unsigned packaging mode now completes correctly when Windows Application Control blocks the embedded backend after the shell starts; signed release mode remains strict.
- Valid JSON-RPC tool calls no longer fall through to HTTP 404 when a connector or reverse proxy rewrites the invocation path after discovery; the same access-key and Origin checks remain enforced.
- Power-Boost extensions added, updated or removed from a running MCP are now reconciled automatically with the live runtime and tool catalog. Custom gateway ports are discovered from the active instance and settings, with no manual restart required.
- Remote MCP HTTP errors now include the endpoint, status and bounded response detail without exposing secret query values. A tool call that received an HTTP response is never resent through fallback.
- Ambiguous remote tool calls are no longer resent through another connection when the socket may have failed after execution, preventing the same action from running twice.
- The live Tool Calls view now reconciles rows locally instead of issuing three API requests and rerunning history aggregates for every event.
- Gateway diagnostics show the latest catalog revision and tool count delivered to each AI session; history queries are faster through composite indexes and invalidated caches.
- Two redundant database reads on every successful tool call were removed; the cached client lookup now actually skips the query it was meant to avoid.