From 8bc0e66cd4fe6f6503ef8b5d608dd58cdcb0b66d Mon Sep 17 00:00:00 2001
From: Baudbot <hornet@agentmail.to>
Date: Mon, 23 Feb 2026 21:18:52 -0500
Subject: [PATCH] fix: improve bridge message when agent socket is not found

Replace the misleading 'Agent is starting up' message with a more
actionable one that tells the user the agent is not connected and
suggests running 'sudo baudbot restart' to fix it.

The old message assumed the agent was booting, but the common cause
is a stale session UUID or a crashed agent process.
---
 slack-bridge/broker-bridge.mjs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/slack-bridge/broker-bridge.mjs b/slack-bridge/broker-bridge.mjs
index 61d8c89..9bc00a6 100755
--- a/slack-bridge/broker-bridge.mjs
+++ b/slack-bridge/broker-bridge.mjs
@@ -699,7 +699,7 @@ async function handleUserMessage(userMessage, event) {
   const currentSocket = socketPath;
   if (!currentSocket) {
     logError("🔌 no pi socket found — agent may not be running");
-    await say(event.channel, "⏳ Agent is starting up — try again in a moment.", event.ts);
+    await say(event.channel, "🔌 Agent is not connected — it may be restarting or the session expired. Run `sudo baudbot restart` to bring it back.", event.ts);
     return true;
   }
   logInfo(`🔌 forwarding to agent via ${currentSocket}`);