OpenClaude v0.14.0 stabilizes OpenGateway API

OpenClaude released v0.14.0 on May 23 with a cluster of changes centered on its OpenGateway API, according to the project’s GitHub releases page. The update adds a requirement for API keys on `/v1/*` routes and switches those routes to bearer authentication, while also bundling fixes for repeated tool-failure loops, input freezes tied to MCP connections and other bugs that could interrupt long-running workflows. (github.com) OpenClaude describes itself in its repository as an open-source coding-agent CLI for cloud and local model providers. The maintainer also published a demo and notes on X describing the release as a production-focused OpenGateway update. ### Which changes in v0.14.0 affect backend integrations most directly? Version 0.14.0 lists one OpenGateway-specific feature and several adjacent fixes that matter for developers wiring the tool into services. The release says OpenGateway now requires an API key on `/v1/*` and uses bearer authentication, a change tracked in pull request #1322. The same release also fixes “query: stop repeated tool-failure loops,” adds a five-minute timeout to QueryGuard to prevent an “infinite spinner,” and defers some MCP connections to prevent input freezes. Those changes are not labeled as OpenGateway features, but they address failure modes that can disrupt automated or embedded usage. (github.com) ### Why does the authentication change stand out? The `/v1/*` authentication change is the clearest sign that the release is aimed at harderening service-style use rather than just interactive CLI sessions. Requiring API keys on those routes and moving to bearer auth gives developers a more standard pattern for connecting OpenClaude to backend systems that already expect token-based authentication. (github.com) OpenClaude’s repository says the project supports OpenAI-compatible APIs, Gemini, GitHub Models, Codex, Ollama and other backends in a single terminal-first workflow. That makes the gateway layer a key point of integration when teams use OpenClaude as a bridge between application logic and multiple model providers. (github.com) ### What do the bug fixes suggest about the problems developers had been hitting? The release notes point to reliability issues that would be noticeable in production-like workloads. The fixes mention repeated tool-failure loops, infinite spinners, empty built-in agent registrations, OpenRouter retry behavior after a 402 credit shortfall, and MCP connection handling that could freeze input. (github.com) A separate issue in the repository, filed last month, described OpenClaude freezing indefinitely when loading large numbers of custom agents or large external memory stores. That issue was not cited in the v0.14.0 notes, but it shows the project has been dealing with scaling-related rough edges in recent weeks. (github.com) ### How does this fit into OpenClaude’s recent release cadence? GitHub’s release history shows OpenClaude shipping quickly in May. Version 0.12.0 on May 16 added models to the OpenGateway catalog, version 0.12.1 on the same date fixed Gemini tool-call handling through OpenGateway, version 0.13.0 on May 17 added export features and other fixes, and version 0.14.0 arrived on May 23. (github.com) That sequence shows OpenGateway has been an active part of the project’s recent development, with multiple releases touching catalog support, tool-call handling and now authentication and operational stability. (github.com) ### Where should developers look next? The GitHub release entry for v0.14.0 is the authoritative changelog for the code shipped on May 23, and the project repository remains the main reference for supported providers and setup paths. The maintainer’s X post includes a demo and notes tied to the same release, giving developers a public walkthrough of the changes described in the release notes. (github.com) The next concrete step is testing v0.14.0 against existing `/v1/*` integrations, especially any deployments that need to update authentication handling to bearer tokens and verify behavior under multi-step tool or MCP-heavy workloads. (github.com)