What is an AI coding agent supervisor?+
Your right hand over coding agents you plug in — not another chat, runtime, or planner. One Supervisor covers a single session or a multi-agent mission: company and repo context let it inject constraints, cover criteria, double-check mechanical work, and escalate only when the decision is still yours. It also selects an eligible route, lands mid-flight steers at the program level with a visible receipt, and proves results independently. Most of the loop never reaches you; the ones that do are the calls you would want to make anyway.
How is this different from just running a coding agent yourself?+
Running an agent alone still makes you the router, the context-loader, the babysitter, and the QA function: you re-explain taste and decisions every session, unstick mid-flight, and review every diff cold. HiveBase’s Supervisor answers what it can for you from company context so you don’t babysit each chat in a mission — mechanical orchestration recedes, and only clarifying judgment, money paths, and other calls that stay yours pull you in.
Is a quick fix a different product from a big mission?+
No. One intake, size-adaptive. A quick task is a program of one — same Supervisor, same surface, no mode switch, no “group it later.” Multi-agent waves only appear when the work actually needs them.
What happens when I interrupt mid-run?+
You steer the Supervisor, not each agent chat. Every interjection enters at the program level — from task chat, Linear, a hold answer, or a scoped hint in an open session. The Supervisor triages the meaning, fences it to the plan revision it was judged against, and returns a visible receipt so the redirect doesn’t feel like it vanished even when it worked.
Do I need API keys or BYOK?+
Claude Max is GA on your Mac. Codex, Cursor, and SuperGrok are local previews of the same plug-in. Cloud subscription runners are on the roadmap. Metered HiveBase Cloud (API key or credits) is a separate preview — consumer subscription credentials stay off that venue. API keys and BYOK are optional overflow. When a pool would spill into unexpected on-demand billing, HiveBase Holds for your approval instead of continuing silently.
What happens when a subscription hits its cap?+
Usage is not one number: some legs refill on a clock (queue and resume), others are monthly pools (route elsewhere or Hold). Cursor has no public quota API, so HiveBase cannot pre-check Cursor remaining — exhaustion is reactive at execution. If continuing would spill into surprise on-demand billing, HiveBase stops and asks you first — it never burns your card quietly.
What does “done” mean here?+
Every criterion carries a proof tier: verified with independent evidence, reviewed only, or unverified — stated plainly. Agent self-checks are not verification. Producer and grader are different families when proof is claimed. Experience surfaces fail soft with honest labels; trust surfaces fail closed.
What happens when a Mission hits a wall?+
It parks with a typed reason and a next action — never bricks. It ships what already passed verification, surfaces the blocked work with the real error, and never silently half-merges. Safe partial delivery is part of the contract.
