Qoder CLI stuck at v0.2.14 while npm has v1.1.55 — automated version updates appear broken

[tanpenggood]

Summary

The Qoder CLI entry in the registry (qoder/agent.json) is pinned at v0.2.14, while the npm package @qoder-ai/qodercli has reached v1.1.55. That's a gap of roughly 4 months and ~50 releases.

Current state

• Registry file: qoder/agent.json
• Current version in registry: 0.2.14
• Distribution: npx @qoder-ai/qodercli@0.2.14 --acp
• Latest on npm: 1.1.55 (stable 1.1.54 also available)

Evidence of broken auto-update

The repo has a daily automated "Version update failed" issue (e.g. #609, #606, #604, #601, #599, #597, #594, #592...) dating back to at least 2026-09-10. These generic failures suggest the automated version-update workflow cannot successfully bump Qoder's entry.

Impact

Users of JetBrains AI Assistant (and any other ACP client consuming this registry) get a severely outdated agent. v0.2.14 has known bugs (e.g. WebFetch broken) that were fixed many releases ago. The version gap also means users miss out on new capabilities and model support added in the 1.x line.

Request

1. Short term: Manually update qoder/agent.json to 1.1.55 (or at least 1.1.54 stable).
2. Long term: Investigate why the automated version-update workflow fails for Qoder specifically — is the npm package name correct, are there auth/permission issues, or did the update script break for this entry?

References

• Registry entry: https://github.com/agentclientprotocol/registry/blob/main/qoder/agent.json
• npm package: https://www.npmjs.com/package/@qoder-ai/qodercli
• Related JetBrains issue: https://youtrack.jetbrains.com/issue/LLM-31283