Claude Code Has Evolved
Channel: Chase AI
Uploaded:
Duration: PT1204S
Read a transcript preview of “Claude Code Has Evolved” from Chase AI, uploaded on 2026-05-14.
Transcript preview
Language: English (original, YouTube automatic captions)
[0:00] Your Claude code agentic OS sucks and
[0:02] it's because you're focused on the wrong
[0:05] things. You're spending all your time on
[0:07] fancy dashboards and command centers
[0:08] like this one and this one instead of
[0:11] focusing on what actually drives value
[0:13] in a Claude code agentic OS and that's
[0:16] this, a skill and automation backbone
[0:19] that actually drives everything. The
[0:22] problem is creating something like this
[0:23] at a high level takes time, isn't flashy
[0:26] and can be kind of boring especially
[0:28] when we compare it to these wild looking
[0:31] command centers that bring in a ton of
[0:33] views. But the truth is to get any value
[0:36] out of a Claude code agentic OS
[0:38] especially when we're talking about the
[0:39] observability piece, the dashboard
[0:41] piece, the command center thing, it's
[0:43] only going to happen if this is locked
[0:46] in. And that's because a strong agentic
[0:48] OS has three parts to it. The first is
[0:51] what you see right here. It's the skill
[0:52] and automation backbone. It's the idea
[0:54] that we are going to take Claude code
[0:56] and turn it into a system that can give
[0:58] us reliable outputs. We are going to
[1:00] take your daily or your team's or your
[1:03] client's workflows and tasks, turn those
[1:05] into skills, turn those skills into
[1:07] automations where it makes sense and in
[1:09] the process build out a cohesive system
[1:13] like you see here so we can do
[1:15] the same thing over and over again at a
[1:18] high level and get consistent outputs.
[1:21] The second part of an agentic OS is the
[1:22] memory layer. How do we handle the idea
[1:25] of context engineering? Well, there's a
[1:27] number of ways we can do it. W