fix: restart periodic ping after client reconnection

travisbreaks · claude · travisbreaks · commit e1cee804857e · 2026-04-02T00:32:51.000-05:00
The reconnection path (when transport.sessionId is set) returns early,
skipping the startPeriodicPing() call that runs after normal
initialization. Since _onclose() clears the ping timer during
disconnection, connection health monitoring silently stops working
after any reconnect. Adding startPeriodicPing() before the early
return ensures pings resume on reconnection.

Co-Authored-By: Claude Opus 4.6 (1M context) &lt;noreply@anthropic.com&gt;
diff --git a/packages/client/src/client/client.ts b/packages/client/src/client/client.ts
@@ -498,6 +498,8 @@ export class Client extends Protocol<ClientContext> {
             if (this._negotiatedProtocolVersion !== undefined && transport.setProtocolVersion) {
                 transport.setProtocolVersion(this._negotiatedProtocolVersion);
             }
+            // Restart periodic ping since _onclose() clears the timer on disconnect
+            this.startPeriodicPing();
             return;
         }
         try {

Original file line number	Diff line number	Diff line change
`@@ -498,6 +498,8 @@ export class Client extends Protocol<ClientContext> {`
`498`	`498`	`if (this._negotiatedProtocolVersion !== undefined && transport.setProtocolVersion) {`
`499`	`499`	`transport.setProtocolVersion(this._negotiatedProtocolVersion);`
`500`	`500`	`}`
	`501`	`+ // Restart periodic ping since _onclose() clears the timer on disconnect`
	`502`	`+ this.startPeriodicPing();`
`501`	`503`	`return;`
`502`	`504`	`}`
`503`	`505`	`try {`