From f0d8c84a6434ebf8282f98f0243a589d197d4cff Mon Sep 17 00:00:00 2001
From: josedario87 <jodarioel87@gmail.com>
Date: Sat, 14 Feb 2026 23:36:44 -0600
Subject: [PATCH] fix: Auto-reconnect on refresh by deferring torch state to
 torch-update

The registered handler was setting hasTorch early, causing torch-update
to see no transition and skip connectToMCP().
---
 frontend/src/services/torch.ts | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/frontend/src/services/torch.ts b/frontend/src/services/torch.ts
index 8b20f5e..2ff5b9d 100644
--- a/frontend/src/services/torch.ts
+++ b/frontend/src/services/torch.ts
@@ -74,11 +74,8 @@ async function handleMessage(data: any) {
       clientId = data.id
       torchStore.setClientId(data.id)
       console.log(`[Torch] Registered as ${data.id}, hasTorch: ${data.hasTorch}`)
-
-      // Just update state, don't auto-connect - user must request torch explicitly
-      if (data.hasTorch) {
-        torchStore.setTorchState(data.id)
-      }
+      // Don't set torch state here — let torch-update handle the transition
+      // so connectToMCP() is triggered correctly
       break
     }