KI-Coding: Was Claude Code besser macht als die Konkurrenz

So, what the hell am I doing making a video about good parts of Claude Code? Well, as I hinted at the start, I've been using it a ton, and I've noticed a handful of things I actually really like. I'll be transparent with my goal here. I want every other harness to steal all of these things. I am making this video not because Claude Code is better and I want everyone to appreciate how great it is, but because I want everything else to take the good parts so that I don't miss Claude Code when I use other things. So, knowing that, what are those things? One of the things Cloud Code does really differently with their skills is the ability to execute scripts in them. There's a lot of use cases where it's nice for the model to know things when it loads the skill instead of having to load the skill and then do things and then do the next step. But this is a feature that Claude Code does really well that I think people are too hesitant to introduce. Next, I want to talk about the Claude MD for a bit. I have issues here in particular that the claud and agentmd are competing standards. But I have come around to some of the cool things you could do in the cloud MD. Claude MD files can import additional files using at path/2/import syntax. Imported files are expanded and loaded into context at launch alongside the cloud MD that references them. This also means you can do a very convenient thing for those of us who are annoyed that the agent MD and claude MD are different at agents.mmd. Now my claude MD is my agents MD. This is a really nice pattern, especially because it works with things other than markdown, and I wish more things would copy it. While I was reading these docs to get this information, I found another really cool feature I didn't know about, which is launching sessions from links. They actually have their own HTTP code here, claude- CLI slash, that allows you to open things in cloud CLI. So you can have a page that someone makes that has a bunch of links in it to trigger cloud CLI. But one of the really nice things Cloud Code has that I haven't seen anyone else do is a special command slash by the way, which lets you ask a quick side question without interrupting the main conversation. But what I want to show off is workflows. Because workflows aren't just a bunch of tool calls the agent can do. You let the agent write code to do a thing instead. By default, workflows use up to eight agents in parallel, and it will constantly be spinning up new ones as previous work is finished. One more that a lot of people told me to talk about which I haven't used yet but I've heard really good things so I'm going to try it here is remote control. So now I've given the ability for this cloud code instance on my real computer to be controlled through cloud.ai the website or from my phone using the cloud app. I can click audit open PRs and workflow planning. And this is the exact run that is going on on my computer right now. There's a lot of things in cloud code that are good. I went out of my way to not talk about the bad here but I might have to in the future. So, if you want me to do a video where I tear apart all of the things that Cloud Code does wrong, let me know in the comments.