ApolloOffice
A local office of AI workers that turns GitHub bug reports into verified pull requests with regression tests.
At a Glance
Self-hosted ApolloOffice binary under AGPL-3.0, run locally with your own GitHub and AI accounts. Currently in beta.
Engagement
Available On
Alternatives
Listed Nov 2026
About ApolloOffice
ApolloOffice is an open-source (AGPL-3.0) desktop app from Silvertree2010 that runs a small office of AI workers on your own computer. Add a GitHub repository and it picks up bug reports, reproduces them, writes a fix with a regression test, and opens a pull request once the proof holds. The project is labeled beta, and the latest listed release is v0.9.0.
What It Is
ApolloOffice is a self-hosted bug-fixing automation tool delivered as a single binary for Windows, macOS and Linux. It works through a fixed pipeline of workers: Scout, Guard, Vet, Hunter, Repro, Fixer, CI, Reviewer, Submit and Watcher, each shown at its own desk on a pixel-office dashboard. It can take bug reports from the repository's issues or hunt for bugs itself, and it runs on your own GitHub and AI accounts with no ApolloOffice server involved.
How the proof works
ApolloOffice itself checks that the new test fails without the fix and passes with it, and that the project's test command stays green. A Reviewer step examines the change before a pull request is opened. By default every pull request waits for your approval, showing the diff, the proof and an editable PR text; a repository can be switched to submit on its own. Commits carry Co-Authored-By trailers for the models involved, and PR text states it was generated with AI.
Providers and isolation
Each worker can use a different provider: Claude Code or Codex with your own login, the Claude, OpenAI or Gemini API with a key, or a local model through Ollama. Repository code runs in Docker on your computer or on any machine reachable over ssh, and the GitHub token stays on your computer.
Beyond single fixes
A Watcher follows open PRs for merges, maintainer change requests and merge conflicts, which it rebases on its own. An optional per-repository feature mode lets it pick small, clearly specified feature requests. A POST /v1/report API and Sentry, GlitchTip and GitHub Actions failure reports can feed bugs in. It also tracks costs per job, worker and repository with an optional daily budget, and supports notifications via ntfy or Discord.
Community Discussions
Be the first to start a conversation about ApolloOffice
Share your experience with ApolloOffice, ask questions, or help others learn from your insights.
Pricing
Open Source (AGPL-3.0)
Self-hosted ApolloOffice binary under AGPL-3.0, run locally with your own GitHub and AI accounts. Currently in beta.
- Licensed under AGPL-3.0
- Single binary for Windows, macOS and Linux
- Runs on your own machine; no ApolloOffice server, no account, no telemetry
- Per-worker provider choice: Claude Code, Codex, Claude/OpenAI/Gemini API or local Ollama (provider costs are external)
- Docker isolation locally or over ssh
Capabilities
Key Features
- Fixed pipeline of AI workers (Scout, Guard, Vet, Hunter, Repro, Fixer, CI, Reviewer, Submit, Watcher)
- Reproduces bugs and writes fixes with regression tests
- Verifies test fails without fix and passes with it
- Approval gate for every pull request by default
- Per-worker provider selection
- Docker isolation locally or over ssh
- Watcher for open PRs, rebasing merge conflicts
- Optional feature mode
- API for bug reports from external tools
- Sentry, GlitchTip and failed GitHub Actions run reporting
- Cost tracking with daily budget
- Notifications via ntfy or Discord
- Automatic updates
