My coworker let an AI agent handle Slack replies while he was "unavailable." It did not go well.
Summary
An employee used an AI agent to auto-respond to Slack messages, and it gave a confidently wrong answer about a client deadline, highlighting the risk of trusting tone and fluency over accuracy.
Similar Articles
my agent wasn't ignoring customers, my own safety guard was eating the replies
A developer details how their AI agent's silence was caused by safety guards failing closed, timeouts, and nested JSON issues, emphasizing that silent failures are worse than wrong answers in customer-facing chatbots.
My personal AI agent posted my bank details on company Slack
XMTP Labs CEO Shane Mac recounted how his personal AI 'CFO' agent, built on Grok Bot with read-only bank access, mistakenly posted his private financial details to his company's executive Slack channel because two similarly named channels confused it. The incident has made him rethink how he deploys personal AI agents.
@omarsar0: This is the most capable AI I have put in front of my own work. Added an AI employee to my Slack, asked it to run this …
The author integrated an AI employee into Slack that autonomously executed and completed a weekly task, showcasing its high capability.
Uncomfortable truth: Is anyone else finding AI agents way too unreliable for real workflows?
A practitioner shares frustration with AI agents' unreliability in multi-step workflows, citing high production failure rates (70-95%) and widespread distrust among knowledge workers due to drift and silent failures.
Giving an agent Gmail + Slack + Sheets feels less like AI and more like handling a junior employee the keys
The post discusses how AI agents integrating with work apps like Gmail and Slack shifts the conversation from autonomy to permissions, emphasizing the need for careful gating in real-world business workflows.