fix: improve bridge message when agent socket is not found (#157)

baudbot-agent · Baudbot · web-flow · commit 7fc976231218 · 2026-02-23T21:23:57.000-05:00
Co-authored-by: Baudbot &lt;hornet@agentmail.to&gt;
diff --git 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}`);

Original file line number	Diff line number	Diff line change
`@@ -699,7 +699,7 @@ async function handleUserMessage(userMessage, event) {`
`699`	`699`	`const currentSocket = socketPath;`
`700`	`700`	`if (!currentSocket) {`
`701`	`701`	`logError("🔌 no pi socket found — agent may not be running");`
`702`		`- await say(event.channel, "⏳ Agent is starting up — try again in a moment.", event.ts);`
	`702`	+ 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);
`703`	`703`	`return true;`
`704`	`704`	`}`
`705`	`705`	logInfo(`🔌 forwarding to agent via ${currentSocket}`);