Questions, answered directly
Including the ones where the honest answer is “not yet.”
- What is Arcadia Mission Control?
- A governance and prioritization layer for AI-assisted software production. It holds what you are building and why, decides which work comes next, stops at the decisions that should stay human, and verifies that approved work actually completed. It sits above your coding agents rather than replacing them.
- How is this different from a coding agent?
- Coding agents write code. Mission Control does not write any. It decides what the agents should work on, keeps their sessions and branches from colliding, and checks the result against criteria written before the work started. Different job, different layer.
- How is this different from an orchestration framework?
- Orchestration frameworks route and parallelize execution — they make more agents run at once. Mission Control governs intent, approval, priority, and evidence. It answers what should run and whether it worked, not how to run more of it.
- How is this different from an issue tracker?
- A tracker stores intent but never decides. It will not tell you what to do next, will not stop an agent at an approval boundary, and will not verify that a closed ticket reflects work that happened. Mission Control does those three things.
- Which coding agents does it work with?
- It is agent-neutral by design and currently drives Claude Code, Codex, and OpenCode. As agents become interchangeable infrastructure, being tied to one of them would be a liability. Which agents matter most to early users is one of the things we are asking.
- Is it available yet?
- No. It runs today as the system used to build itself, which is a real test but not a product anyone else can install. Early access opens when someone who is not the author can set it up from cold and have it work.
- What does it cost?
- Nothing is for sale, and there is no price yet. Nobody has paid for this, so any number on the page would be a guess dressed as a fact. The signup form asks what you would find credible, and that answer genuinely shapes the decision.
- Does it need access to my code or my repositories?
- The website collects no code, no repository access, and no credentials — only what you type into the form. Arcadia itself runs locally, on your own machine and your own repositories. A hosted option is something we are exploring, not something that exists.
- How much autonomy does it actually take?
- As much or as little as you set. The design intent is that consequential actions — spending money, deploying, anything irreversible — stop and wait for a person, while ordinary work continues. How much autonomy people actually want is an open question we are asking directly.
- Who is building this?
- MartianRover — a very small operation, currently one person. That is a reason to be skeptical about longevity and a reason it can change direction fast based on what early users say. You can reach a human at arcadia@martianrover.com.