Structs§
- Auth
Config - Auth
Request - Authenticated
Session - Chat
Message - Chat
Tool Call - Chat
Tool Call Function - Cleanup
WsState Request - Client
Ids - Complete
External Core Events Request - Complete
External Core Events Response - Endpoint
Payload Request - Error
Response - External
Core Device Identity - External
Core Error - External
Core Event - External
Core Event Completion - External
Core Health - External
Core Mdns Record - External
Core Request - External
Core Response - External
Core Runtime Metadata - External
Core Service Effects - Handle
Core Input Request - Handle
Core Input Response - Http
Payload Request - HubConnection
Proof Request - HubConnection
Proof Response - HubMdns
Instance Record - Image
- List
Mdns Records Request - LlmComplete
Request - LlmComplete
Response - LlmGeneration
Options - LlmRoute
Info - MwsClient
Info - MwsMessage
- MwsMessage
Type - MwsSource
- Node
Auth Request - Node
Auth Response - Node
Challenge Evidence - Node
Challenge Payload - Node
Instance List Item - Node
Instance List Response - Node
Token Issue Request - Node
Token Issue Response - Node
Token List Item - Node
Token List Response - Node
Token Revoke Request - Node
Token Revoke Response - Playground
Payload Request - Poll
External Core Events Request - Poll
External Core Events Response - Provider
Tool Call - Register
Local AppClient Request - Register
Node Connection Request - Scope
Info - Scope
Member - Service
Core Output - Update
Callback Base Request - User
Info - User
Setting
Enums§
- Exception
Code - External
Core Event Kind - External
Core Method - Node
Binding Status - Node
Instance Policy - Service
Core Effect - Service
Core Input - Service
Core Response
Constants§
- EXTERNAL_
CORE_ PROTOCOL_ VERSION - HUB_
CONNECTION_ PROOF_ PROTOCOL - HUB_
CONNECTION_ PROOF_ TARGET - MWS_
MAX_ FRAME_ SIZE - MWS_
MAX_ MESSAGE_ SIZE - Shared MWS transport limits. Both websocket peers must apply these values so an envelope accepted by one side is never rejected solely due to asymmetric transport configuration.
- MWS_
MAX_ WRITE_ BUFFER_ SIZE - NODE_
ONBOARDING_ CHALLENGE_ ALGORITHM - NODE_
ONBOARDING_ CHALLENGE_ AUDIENCE - NODE_
ONBOARDING_ CHALLENGE_ PROTOCOL - NODE_
ONBOARDING_ ES256_ ALGORITHM - NODE_
ONBOARDING_ TOKEN_ AUDIENCE - NODE_
ONBOARDING_ TOKEN_ ISSUER_ PREFIX - NODE_
ONBOARDING_ TRANSACTION_ TTL_ SECONDS
Functions§
- hub_
connection_ proof_ signing_ payload - Canonical, domain-separated bytes signed by the Hub for one physical WS connection. Length prefixes keep the encoding unambiguous without relying on JSON object ordering.