Skip to content

GridOrchestratorOptions

Defined in: packages/client/src/lib/orchestrator/orchestrator.types.ts:82

Options under grid mode, where no first screen can be seeded.

optional connection?: Partial<ConnectionOptions>

Defined in: packages/client/src/lib/orchestrator/orchestrator.types.ts:28

Connection options for the ConnectionManager

OrchestratorOptionsBase.connection


optional debounceDelayMs?: number

Defined in: packages/client/src/lib/orchestrator/orchestrator.types.ts:22

Debounce delay for update batching in ms (default: 300)

OrchestratorOptionsBase.debounceDelayMs


optional debug?: boolean

Defined in: packages/client/src/lib/orchestrator/orchestrator.types.ts:20

Enable debug logging (default: false)

OrchestratorOptionsBase.debug


optional initialLayout?: undefined

Defined in: packages/client/src/lib/orchestrator/orchestrator.types.ts:91

Unavailable under grid mode. A seed has to create the instances it arranges, which only a tiling tree expresses; grid positions can merely move instances that already exist. Seed under TilingOrchestratorOptions.initialLayout instead.


layoutMode: "grid"

Defined in: packages/client/src/lib/orchestrator/orchestrator.types.ts:84

Layout mode.


optional maxWaitMs?: number

Defined in: packages/client/src/lib/orchestrator/orchestrator.types.ts:24

Maximum wait time before forcing an update flush in ms (default: 1000)

OrchestratorOptionsBase.maxWaitMs


optional readyTimeoutMs?: number

Defined in: packages/client/src/lib/orchestrator/orchestrator.types.ts:26

Max wait time for instance readiness before skipping actions in ms (default: 500)

OrchestratorOptionsBase.readyTimeoutMs


optional sessionId?: SessionId

Defined in: packages/client/src/lib/orchestrator/orchestrator.types.ts:18

Session ID for conversation continuity. Auto-generated if omitted.

OrchestratorOptionsBase.sessionId


optional vessels?: readonly VesselDefinition[]

Defined in: packages/client/src/lib/orchestrator/orchestrator.types.ts:44

Vessel definitions to register before TilingOrchestratorOptions.initialLayout is validated and applied. Equivalent to calling vesselManager.registerVessel() for each immediately after construction — including its report-don’t-throw behavior: a definition that fails schema validation is skipped and logged rather than aborting construction, so one bad vessel cannot take down every other vessel. Registering here (rather than after construction) exists so an initialLayout seed can reference these vessels — the registry starts out empty otherwise. The one place this still throws is indirect: if initialLayout names an instance whose vessel failed validation (or was never listed here), construction throws naming that instance and vessel — a seed genuinely cannot be honored without the vessel it names.

OrchestratorOptionsBase.vessels