A guided setup flow for gateway configuration, providers, IDE context, skills, and the first operational handoff.
Store the gateway target, align provider defaults, choose IDE context, and prepare the first execution handoff.
Gateway details and operator credentials stay in browser storage with no arbitrary host probing from this page.
This route works best after the buyer already understands deployment and review posture from the enterprise and docs surfaces.
The wizard keeps setup state visible while operators configure gateway, model, IDE, and skill choices.
The WebUI gateway handles provider routing, sessions, and execution boundaries. The browser chat surface expects the authenticated WebUI API host here, not the static marketing site origin. This step validates and stores the URL locally instead of probing arbitrary hosts from the browser.
Stored in browser session storage only. If you previously bootstrapped the WebUI with?token=...on the gateway host, cookie auth can also be reused.
Default WebUI gateway:http://localhost:8787
Manual verification:open http://localhost:8787/webui/?token=YOUR_TOKEN