feat(companion): add reconnect resilience

This commit is contained in:
William Valentin
2026-02-25 11:12:21 -08:00
parent 7b170cff4d
commit ac60fa5be3
9 changed files with 297 additions and 27 deletions
+4 -1
View File
@@ -1067,6 +1067,9 @@ Flynn now propagates a run-level abort signal into model/tool execution, so prov
Register node role/capabilities for the current WebSocket connection.
Registration is scoped to the connection. If a companion reconnects it must call `node.register` again
to restore node identity, capabilities, and access to `node.*` methods.
**Request:**
```json
{
@@ -1840,5 +1843,5 @@ For more implementation details, see:
- Protocol types: `src/gateway/protocol.ts`
- Handlers: `src/gateway/handlers/`
- Gateway server: `src/gateway/server.ts`
- Companion runtime client helper: `src/companion/runtimeClient.ts` (node + system + `canvas.*` typed RPC wrappers, optional `autoConnect`)
- Companion runtime client helper: `src/companion/runtimeClient.ts` (node + system + `canvas.*` typed RPC wrappers, optional `autoConnect`/`autoReconnect`, connection event subscriptions)
- Platform companion wrappers: `src/companion/platformClients.ts`