trending
•

5h ago

Why Your Agents Won't Work: an open roast thread

Let's do an honest agent roast. If you've tried using an AI agent in real work, tell us about a time it didn't work.
What were you trying to get done? What did the agent do instead? What did you have to redo or clean up? Stories from sales, operations, research, support, coding, or anywhere else are welcome.
Maybe it lost context between tools. Maybe it lacked permission, made something up with confidence, or broke in a completely different way. No polished demos, no pitches, and no need to have a fix. I'm curious which failures keep showing up when agents leave the demo and enter daily work.
What's your most memorable agent fail?

•

17h ago

When your team switches AI agents, what happens to the project context?

Hi, I'm Kelly from Busabase. We're building an open-source database and workspace where the records, docs, skills, and apps a team chooses to keep can be reused by people and connected AI agents.
One problem we keep running into: an agent finishes useful work, but the result stays buried in a chat. The next person or agent has to reconstruct the project background and decisions before moving forward. In Busabase, that work can live in a shared workspace, with access controlled by permissions and review when needed.
How does your team handle this today? Where do you keep the project context that multiple agents need, and what gets lost most often when you move between tools like Claude Code and Codex? I'd love to hear what's working for you and what still breaks.

Busabase - The general system of record for AI agents

Different agents. One shared base. Busabase is a general-purpose database and workspace for people and AI agents. Keep business records, docs, skills, and apps in one place so the next task can build on them. Connect Claude Code, Codex, and more. Set access, review changes when needed, and see what changed. Busabase is open source, with Cloud, Personal Desktop, and self-hosting options.