It's only getting worse

Question

Sean \u002D I\u0027ve been with you from your first launch. There are a handful of us that have seen both the rise and continued fall of AF. I come here because discord is no longer a place to voice these concerns. As you know, AF is full of bugs right now. User\u0027s can\u0027t go more than a week without running into another major bug that renders the agents unreliable.  You\u0027ve now introduced Claw and to no surprise it is full of more bugs. So many that most are calling this Alpha, at best, within threads we have outside of AF.  Your dev team can\u0027t fix AF bugs while also trying to fix claw. You\u0027ve stretched them too thin now. Why is it that you continue to build on top of a noticeably unstable system? You\u0027re passionate about this industry, but you\u0027re overspent now. We need the original Sean that cared more for the basics than new bells and whistles.

SeanP_AgenticFlowAI · Answer

Hi, \u000athanks for the honest feedback. I\u0027m appreciate it below is my clarification (using Ishi to format from my voice transcript for easier reading as it\u0027s 2am here). I hope this clarify a bit, I will explain more in next Office Hour. Bests, Sean\u000a\u002D\u000aSince you\u0027ve been here from Day 1, you deserve the unvarnished truth about why we are doing this and how we are managing the resources.\u000a\u000aFirst, I acknowledge the pain. You are right—AgenticFlow (AF) has had stability issues, and introducing a new app (Claw/Ishi) looks like \u0022shiny object syndrome\u0022 from the outside. I understand why it feels like we are overstretched.\u000a\u000aBut here is the reality of the situation and why this is a strategic necessity, not a distraction:\u000a\u000a1. The \u0022Complexity Wall\u0022\u000aWe hit a wall with AgenticFlow. We wrote 2,000+ pages of documentation and created 250+ videos, yet the learning curve remains brutal. We realized that for most users, building complex workflows (like the 16\u002Dagent setups our power users have) is simply too hard to do manually. We cannot scale support by just writing more docs. We needed a better way to help users build.\u000a\u000a2. Ishi is not a distraction\u003B Ishi is the \u0022fix\u0022\u000aWe didn\u0027t build Claw (now re\u002Dbranded as Ishi) just to have a cool desktop app. We built it because we need a \u0022Pair Programmer\u0022 that lives on your desktop to help you build AgenticFlow.\u000a\u002D The Vision: Instead of you reading docs to fix an error, Ishi sits on your desktop, reads your context, and helps you configure the AgenticFlow backend.\u000a\u002D The Synergy: We are currently building deep Traceability features into AF. The goal is for Ishi to read those trace logs and tell you exactly why an agent failed and how to fix it, rather than you having to hunt for the error yourself.\u000a\u000a3. Resource Allocation\u000aI want to be clear: The core engineering team is still 100% focused on AgenticFlow.\u000aWe spent December stabilizing the core and adding the new Traceability layer. Ishi is being built by a spun\u002Doff \u0022tiger team\u0022 specifically to solve the usability problem of AF. We aren\u0027t abandoning the core\u003B we are building the interface that makes the core usable.\u000a\u000aThe Road Ahead\u000aWe are renaming Claw to Ishi (meaning \u0022Will\u0022 and \u0022Cornerstone\u0022) to reflect this foundation. I am asking you to hang in there a little longer. We are building Ishi to be the \u0022Expert\u0022 that helps you debug the \u0022Platform\u0022 (AF).\u000a\u000aWe need the platform to be stable, but we also need the tool that makes the platform accessible. We are working on both.\u000a\u000aThank you for holding me accountable. I\u0027m still the same Sean, just trying to solve a much harder problem than when we started.

AgenticFlow

Share AgenticFlow

Related questions