Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
benvinegar merged 1 commit into from
Feb 24, 2026
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion slack-bridge/broker-bridge.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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);
Copy link

@greptile-apps greptile-apps bot Feb 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The legacy bridge in bridge.mjs:268 still has the old "Agent is starting up" message. Consider updating it to match this improved message for consistency.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Prompt To Fix With AI 
This is a comment left during a code review.
Path: slack-bridge/broker-bridge.mjs
Line: 702

Comment:
The legacy bridge in `bridge.mjs:268` still has the old "Agent is starting up" message. Consider updating it to match this improved message for consistency.

<sub>Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!</sub>

How can I resolve this? If you propose a fix, please make it concise.

return true;
}
logInfo(`🔌 forwarding to agent via ${currentSocket}`);
Expand Down