Maintain a forked open-source app through eight releases with Claude

Artur Shaikhutdinov had earlier forked OpenResearch with Claude to add three coding agents, Kimi Code, MiniMax Code and ZCode. After a reader reported that ZCode failed with a model selection error, he kept Claude Opus 5.5 on the fork for three weeks. Claude worked in a cloud Linux container while he installed each CI build on his Windows 10 machine with real accounts and replied ok or sent a screenshot of the error. Claude was not allowed to merge without his ok. The work covered ZCode sign-in changes, decrypting its credentials file to detect mismatched accounts, moving from print mode to ZCode's undocumented app-server protocol by recording its answers against a mock provider, four upstream merges, a Windows desktop build, a Russian translation of 1,288 strings, and two PRs to upstream reviewed by the Greptile bot.

Between 28 September and 16 October the fork shipped 8 releases, v0.3.3 to v0.3.10, from about 11 hours 16 minutes of agent work spread over 18 days: 33 commits, roughly 5,258 lines added and 1,090 removed across 61 files, and 28 new tests. Greptile found real bugs both he and Claude had missed, including chats opening in YOLO mode and approved plans that could not edit files, and scored the final PR 5/5 after fixes. Upstream maintainers have not responded to either PR. He spent $32; by Claude's own token count it would have been over $230 at API prices.

Several failures only showed up on his real machine because Claude's container tested against an unofficial npm build of ZCode, so a human on the target platform stayed essential. Most of the API-price estimate was re-reading long cached context rather than output. The article does not name the harness beyond a cloud container.