My AI workers got ~316 PRs merged in 7 days. The model was never the bottleneck

Reddit r/ArtificialInteligence Tools
coding-agents automation rust open-source ci-cd pull-requests

Summary

作者运行了一套由编码代理组成的小型流水线，在 7 天内于 13 个 Rust 仓库中合并了约 316 个 PR，并分享了关键经验：结果校验应依赖测试与 CI 而非模型本身。项目已开源，为单一 Rust 二进制，兼容 Claude Code、Codex 与 Ollama。

Ran a small pipeline of coding agents on 13 Rust repos for a week. It takes an issue, writes a failing test, fixes it, runs CI and opens a PR. Around 316 got merged in the first seven days. What I learned: Check the result in code, not with the model. A PR only goes out if the new test is red without the fix and green with it. Small models handle more steps than one might think. Only the real fix needs a strong one. Most "bad fixes" came from a broken build image, not from the model. Works with Claude Code, Codex, API keys or Ollama. Open source, single Rust binary. GitHub: https://github.com/Silvertree2010/ApolloOffice
Original Article

Similar Articles

30 to 70 PRs a Day: How We Managed to Not Wreck Our Systems

Lobsters Hottest

Honeycomb's engineering team more than doubled peak daily merges from ~30 to ~74 using AI tools like Claude Code, with AI-attributed code rising to 82.6% by June 2026, while managing incidents proportionally. They share practices like continuous delivery, fast CI, and observability that amplified with AI.

Learnings from 100K lines of Rust with AI (2025)

Hacker News Top

A developer shares learnings from building a 100K-line Rust-based multi-Paxos consensus engine using AI coding agents, achieving dramatic productivity gains and performance improvements.

@interjc: Over the past few days, I used my own subagent-team skill to lead an "AI team" in development — burning through the weekly quotas of several Claude/Codex/Gemini accounts plus hundreds of dollars in API costs on a major overhaul of a monorepo project. I pulled out all the delegation records and did a retrospective:

X AI KOLs Following

The author shares a retrospective of using their own subagent-team skill to lead a Claude/Codex/etc. AI team through a major monorepo overhaul: cross-vendor model reviews offer the best ROI, rework volume depends on task risk rather than model tier, and they summarize a division of labor where low-tier models act as coordinators, strong models handle risky implementation, and top-tier models handle reviews.