Initialize
hubu stack initCreate an operator-owned profile without starting services.
Agent spend control plane
Governed spend
for AI agents.
Hubu gives humans policy, budget, authorization, and ledger control. Gongbu executes provider work behind a versioned contract. The boundary is the product.
One governed flow
v4.2CONTROL PLANE
Hubu
- Policy + budgets
- Authorizations
- Ledger + reconciliation
versioned executor contract
EXECUTION PLANE
Gongbu
- Provider credentials
- Temporal workflows
- Artifacts + retries
Experimental and local-first.
Read the production warning →Suitable for development, evaluation, and controlled live-provider experiments—not yet for money-grade production workloads.
Managed stack experience
One command from profile to running
The managed lifecycle centers on one-shot startup and one readiness view, while preserving separate Hubu and Gongbu ownership.
Configure
stack.toml · credentials.toml · providers.tomlChoose ownership, binaries, provider references, targets, and spend gates; managed service credentials stay internal.
Start in one shot
hubu stack startValidate, render, and start missing managed components in dependency order.
Check readiness
hubu stack statusInspect the whole stack through one stable, redacted readiness view.
Connect Codex
hubu init codex --stack-profile …Install the unified MCP handoff, restart Codex, and inspect capabilities.
Run governed work
authorize → execute → submit → reconcileKeep policy and money state in Hubu; provider execution and artifacts in Gongbu.
Find your path
Documentation that follows the system
IDENTITY
Register an agent
Guidance-first, canonical, fingerprinted.
Read guide →GOVERNANCETrace a spend
From intent and policy to ledger finality.
Follow lifecycle →EXECUTIONUnderstand Gongbu
Admission, workflows, providers, artifacts.
Open execution plane →AGENT SURFACEUse unified MCP
One catalog, two isolated backends.
Inspect the tools →