ui/client/features/wizard/services/Wizard

Cockpit client (features), v0.9. Source: ui/client/features/wizard/services/Wizard.tsx.

Functions#

connectWizardSocket()#

connectWizardSocket(handlers): WebSocket

Defined in: ui/client/features/wizard/services/Wizard.tsx:15

Real I/O — opens the wizard's WebSocket and wires the given handlers. The wizard is inherently a multi-turn conversation, which is exactly why it stays on ui/server's own WebSocket transport rather than a Next.js API route (see the decision recorded on epic #64).

Parameters#

handlers

WizardSocketHandlers

Returns#

WebSocket

---

sendAnswer()#

sendAnswer(ws, text): void

Defined in: ui/client/features/wizard/services/Wizard.tsx:38

Parameters#

ws

WebSocket

text

string

Returns#

void

---

sendCancel()#

sendCancel(ws): void

Defined in: ui/client/features/wizard/services/Wizard.tsx:43

Stop the run: the server aborts an in-flight model call.

Parameters#

ws

WebSocket

Returns#

void

---

sendReview()#

sendReview(ws): void

Defined in: ui/client/features/wizard/services/Wizard.tsx:47

Parameters#

ws

WebSocket

Returns#

void

---

sendStart()#

sendStart(ws, seedRoute?, planner?): void

Defined in: ui/client/features/wizard/services/Wizard.tsx:34

Parameters#

ws

WebSocket

seedRoute?

string

planner?

"mechanical" | "ai"

Returns#

void