clawdbot/moltbot is not too great for vibe coding tried to vibe code in it for a few days, but I don't recommend it for beyond an AI assistant as of yet Here are the reasons: 1. You want to see what's happening in between the prompts. Terminals give you that ability, Moltbot doesn't. This is a major issue when you work on projects that have even just a bit of depth. 2. You don't see whether it is stuck in loading or working on something. This problem is like bringing friction to a place that didn't exist. With a terminal, I never have this issue. Here, when Moltbot is stuck, I wait a long time thinking it's working on something, only to realize it didn't and got stuck. Wasted so much time like this. 3. Moltbot feels only better for vibe coding when you are not at home. The terminal experience is just 100X better in every way if you are building projects. Only if you wanna continue to build on a project when you are not at home, that's when it can get handy. 4. Debugging visibility is extremely bad When something breaks, you don't get the full picture. Terminal shows you the raw error, the stack trace, the logs. Moltbot gives you a filtered summary. When you're debugging, you need to see everything that's going on, so you don't go into trying to debug the same way when AI gets into rabbit holes. ...