AI 開發工具
AgentHarness 0.36.12 Synchronizes Pins for Four Coding Agent CLIs, but Container-Build Compatibility Still Requires Independent Verification
AgentHarness released versions 0.36.9 through 0.36.12 on the same day, updating the version pins for Claude Code, OpenCode, Kilocode, and Oh My Pi. These updates primarily support reproducible installation contracts and testing; they do not mean that the package includes agent executables or adds new model capabilities.
Ruby coding-agent orchestration layer AgentHarness released versions 0.36.9, 0.36.10, 0.36.11, and 0.36.12 on August 31. In sequence, the releases updated Claude Code in `vendor/pins` from 2.1.238 to 2.1.250, OpenCode from 1.18.19 to 1.18.23, Kilocode from 7.4.23 to 7.5.5, and the Oh My Pi coding agent from 17.4.0 to 18.0.8. RubyGems indicates that 0.36.12 was built and signed by GitHub Actions, with links to the source commit and the Sigstore transparency log.
For AgentHarness, version pins serve a purpose beyond development dependencies. It provides a unified Ruby API for eleven coding CLIs and exposes a provider installation contract that allows downstream containers or worker nodes to obtain package names, installation commands, expected binaries, supported version ranges, and selected download hashes. An orchestrator can therefore pin external CLIs during the image-build stage without hard-coding the installation details for Claude Code, Codex, Aider, or OpenCode individually. Provider metadata can also describe capabilities such as authentication methods, MCP support, and dangerous modes.
However, the changelogs for all of these releases classify the changes as `deps-dev` pin bumps. They do not claim to alter AgentHarness's scheduling, isolation, or error-handling semantics, nor do they bundle binaries for the four CLIs in the Ruby gem. In particular, with Oh My Pi moving to 18.x and Kilocode entering the 7.5.x series, maintainers have aligned interface tests with the pinned versions, but downstream users should still rebuild their images and rerun tests covering permissions, output parsing, and non-interactive mode. The project's main branch also contains model-compatibility contracts and features such as the Claude OAuth PKCE exchange that are still marked as unreleased and must not be counted as delivered in 0.36.12. Engineering teams should next examine whether automated pin updates are accompanied by sufficient end-to-end testing and whether the contract can reliably reject incompatible combinations before deployment when upstream external CLIs introduce breaking changes.