I've been testing SuperAGI for the last two weeks, primarily to automate some internal reporting workflows. The promise of a "no-code" agent builder is attractive, but the reality has been a parade of silent failures. My agents just stop, with the UI showing a pleasant "Completed" status while delivering zero output.
The logs are worse than useless. I get timestamps and generic step names, but no actual error messages, stack traces, or even a hint about which tool or API call caused the problem. It's like trying to debug a black box that's decided not to talk to you.
So, for those of you who've moved beyond the marketing demos:
* What is the *actual* debugging workflow? Are you supposed to run everything locally with verbose flags?
* Is there a hidden log panel, or are we expected to instrument every single tool with our own logging?
* Has anyone reverse-engineered the common failure modes for agents that fail silently? I'm already looking at:
* API keys with insufficient permissions (though no auth error appears)
* Tool output schema mismatches
* Exceeding some unstated context window limit
This feels like a fundamental observability issue. For a platform selling enterprise-grade automation, silent failures are a non-starter. How are you handling this, or is this just an accepted cost of using the platform?
Question everything