Original Summary

ApolloOffice is a small app that runs on your own computer. You point it at a GitHub repo, and a team of AI workers takes the bug reports from there: one finds new issues, one writes a test that reproduces the bug, one writes the fix, one runs the project's tests, one reviews the change and one opens the pull request. Each of them has its own pixel desk on the dashboard, so you can watch who is working on what. A fix only goes out when ApolloOffice has checked it itself: the new test must fail without the fix and pass with it, and the project's full test suite has to stay green. By default every pull request waits for your approval first. Does it actually work? I have been running it nonstop since October 14 on storytold's Craft apps, 13 Rust repos like figcraft, wordcraft and vectorcraft. In those five days around 170 of its pull requests got merged, 60 of them in figcraft alone, and 151 more are open and waiting for review. Only 12 have been closed without a merge so far. Stack A single Rust binary with a web dashboard, for Windows, macOS and Linux. The workers use Claude Code with your own login by default. You can also pick Codex, an API key or a local model through Ollama for each worker. Builds run in Docker on your computer or on other machines over ssh. There is no server of mine in between and no telemetry. I built most of it together with Claude Code. It's free and open source (AGPL-3.0): https://github.com/Silvertree2010/ApolloOffice I'd like to hear what you think, especially from people who maintain open source projects: would you want PRs like these?   submitted by   /u/QueasyCat3096 [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/19 14:19:26