GridOrchestratorOptions
Defined in: packages/client/src/lib/orchestrator/orchestrator.types.ts:82
Options under grid mode, where no first screen can be seeded.
Extends
Section titled “Extends”Properties
Section titled “Properties”connection?
Section titled “connection?”
optionalconnection?:Partial<ConnectionOptions>
Defined in: packages/client/src/lib/orchestrator/orchestrator.types.ts:28
Connection options for the ConnectionManager
Inherited from
Section titled “Inherited from”OrchestratorOptionsBase.connection
debounceDelayMs?
Section titled “debounceDelayMs?”
optionaldebounceDelayMs?:number
Defined in: packages/client/src/lib/orchestrator/orchestrator.types.ts:22
Debounce delay for update batching in ms (default: 300)
Inherited from
Section titled “Inherited from”OrchestratorOptionsBase.debounceDelayMs
debug?
Section titled “debug?”
optionaldebug?:boolean
Defined in: packages/client/src/lib/orchestrator/orchestrator.types.ts:20
Enable debug logging (default: false)
Inherited from
Section titled “Inherited from”initialLayout?
Section titled “initialLayout?”
optionalinitialLayout?: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
Section titled “layoutMode”layoutMode:
"grid"
Defined in: packages/client/src/lib/orchestrator/orchestrator.types.ts:84
Layout mode.
maxWaitMs?
Section titled “maxWaitMs?”
optionalmaxWaitMs?:number
Defined in: packages/client/src/lib/orchestrator/orchestrator.types.ts:24
Maximum wait time before forcing an update flush in ms (default: 1000)
Inherited from
Section titled “Inherited from”OrchestratorOptionsBase.maxWaitMs
readyTimeoutMs?
Section titled “readyTimeoutMs?”
optionalreadyTimeoutMs?: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)
Inherited from
Section titled “Inherited from”OrchestratorOptionsBase.readyTimeoutMs
sessionId?
Section titled “sessionId?”
optionalsessionId?:SessionId
Defined in: packages/client/src/lib/orchestrator/orchestrator.types.ts:18
Session ID for conversation continuity. Auto-generated if omitted.
Inherited from
Section titled “Inherited from”OrchestratorOptionsBase.sessionId
vessels?
Section titled “vessels?”
optionalvessels?: readonlyVesselDefinition[]
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.