An AI gateway sits between agent clients and real execution. That position makes predictability more important than visual novelty.
A terminal-first product can be called by a person, a shell script, CI, an IDE, or another agent. The same operation can emit readable output for an operator and structured JSON for automation. Stable exit codes, explicit flags, and versioned protocols become a public contract that does not depend on a browser session.
Terminal-first does not mean terminal-only. It means the CLI, HTTP API, SDK, and MCP tools remain complete enough to operate and verify the system without a dashboard. Every UI action should eventually map back to one of those inspectable capabilities.
THREE DESIGN PRINCIPLES
Optimize the boundary, not the chrome.
Automate the same path humans use
Commands need non-interactive modes, documented exit codes, machine-readable output, and deterministic defaults.
Make authority explicit
Paid or real-provider execution should require a visible, scoped authorization instead of inheriting ambient UI state.
Return evidence, not reassurance
Health, provider, model, execution mode, and cleanup state should be inspectable in output and through read-only tools.
THE PRODUCT BOUNDARY
One core, several operator surfaces.
This separation keeps the runtime useful when a browser is absent, makes integration tests reproducible, and lets future interfaces evolve without silently changing provider or approval behavior.
RUN THE CLAIM
A first request should be disposable.
Unified AI System publishes a credential-free Docker path. It starts an isolated gateway, proves health and readiness, sends one local fake-provider request, reports the execution mode, and cleans up.
docker run --rm ghcr.io/happy520ai/unified-ai-system/ai-gateway-service:0.4.0 pnpm gateway demo
No account or API key is required for this verified path. Real provider calls are outside the default demo boundary.
WHERE UI BELONGS
Use a console for governance density.
Enterprise teams still benefit from a browser interface. The useful surface is not another chat page. It is a focused operator console for role-based access, approval queues, policy, audit history, budgets, usage, and fleet health.
That ordering keeps the open-source gateway easy to evaluate while leaving room for an enterprise console that earns its complexity. Production readiness, L5 autonomy, and AGI remain claims that require independent evidence beyond repository tests.