@dotobokuri/fleet-console 1.71.1 → 1.72.0

package/CLAUDE.md

@@ -48,7 +48,7 @@
 
 ## Distribution constraints
 
-- Console serves its own web build and owns both published bins (`fleet`, `fleet-console`); there is no second Console web/HTTP owner. The `fleet` entry may still run an ephemeral per-process AI Gateway for Claude Code passthrough.
+- Console serves its own web build and owns both published bins (`fleet`, `fleet-console`); there is no second Console web/HTTP owner. The `fleet` entry may still run an AI Gateway listener of its own — ephemeral for Claude Code passthrough, or explicitly long-lived under `fleet gateway serve` — always bound to loopback, never a Console web/HTTP surface, and never authenticated.
 - Published Console artifacts are self-contained: workspace packages are bundled and must not survive as workspace-version dependencies.
 - The published `./desktop-protocol` subpath is a compatibility surface for shipped Desktop shells under always-latest Console installs; keep its export surface unchanged.
 - Host and built-in plugin bundles may load separate copies of a module. Never coordinate across that boundary through module-scoped singleton state.

package/README.md

@@ -61,6 +61,19 @@ fleet-console
 
 Prefer `fleet console`. The transitional `fleet-console` bin still works. The launcher ensures the local console server is running and opens `/console/` directly without browser token fragments.
 
+The AI Gateway is configured from the same launcher, against the same `ai-gateway.json` the Console screen edits:
+
+```bash
+fleet gateway                          # interactive configuration
+fleet gateway status                   # configuration and credential state
+fleet gateway models --json            # what the gateway currently exposes
+fleet gateway auth login               # Kimi / OpenCode Go API keys
+fleet gateway set xai-endpoint direct  # one policy axis, no prompts
+fleet gateway serve                    # a standalone loopback gateway
+```
+
+The CLI writes the settings file directly, so it works with the Console stopped; an open Console tab shows the change after a reload. `fleet gateway serve` binds 127.0.0.1 and carries no authentication: a client sets `ANTHROPIC_BASE_URL` to the printed URL and any `ANTHROPIC_API_KEY` starting with `sk-ant-`, whose value the gateway never reads.
+
 ## Desktop coexistence
 
 Fleet Console Desktop is a thin Electron shell around this service, not a second Console implementation. Its packaged standard Node `22.23.1` sidecar runs this package's `dist/cli.mjs serve` outside Electron's asar and loads exactly `http://127.0.0.1:<verified-port>/console/`. The service remains the owner of HTTP/REST/SSE/WebSocket, PTY, provider policy, plugin runtime, durable JSON state, and the React UI.