Claude Code has a new UI (pair it with Claude OS)

Added: 2026-05-12

[00:00:00]agents have gotten really good and we're no longer sitting in one chat GBT2 window babysitting every step and asking it to just redo everything. They're now actually executing on a brief and getting us to 90% from a good prompt.

[00:00:13]But this has created a brand new problem for us. How do we actually manage multiple agents running at the same time without five terminal windows open and juggling between them? So, we had Vibe Canban who built a Canban style UI, T-Mux, who had an unofficial answer for the terminal crowd, and I even built my own command center to manage business goals. And loads of others did exactly the same. It was dashboard crazy. So, it's honestly about the time that Anthropic stepped in and shipped something native for us to all use. And that's what we're looking at today, the new agent view. So, it's a proper UI for managing multiple claw code agents built right into claw code. So, let me show you how to get the most out of it and how it pairs with your own Agentic operating system. So, first thing you need to do because it's in research preview is make sure that you're on the latest update for Claude. So, you can hit claude- version. It will tell you exactly which version you're on and you need to be on 2.1.139 or higher. So, we're going to go claude-update in our terminal and it's going to effectively make sure you're up to date. We're then going to just run claude agents and you're going to pop into the summary view and you're going going to become really familiar with this view because it's the highle view of how we see all of our agents organized by session. Now the first thing you're probably going to want to do is migrate your existing sessions into this dashboard view. So if you've got an existing sessions and you start the agent view, this will appear blank.

[00:01:35]So we'll go to an existing session and what we can do is just hit /bg continue this session in the background and free the terminal. It's going to background that task. And then when we go back to the agent view, we've got another session that's appeared inside our agent view. We'll do the same with this session here. It's going to background it. And you see these these sessions effectively close. So what we can do now is actually close down these two terminals. They've been backgrounded and they've been put into the agent view across here. So by default, it's sorted by status. Makes total sense from a UX perspective. We can describe a new task for a new session down here. So we're spinning up a new agent or a new instance when we describe a task down here. So, draft a LinkedIn carousel based on my last YouTube video. Going to hit that. And you can now see that that session is working. So, it's sorted by status by default, but this is where it gets really powerful because if you're working across multiple repositories, you can actually hit Ctrl S and sort it by repo instead or folder structure. So, here we're working all tasks in the same repo and you've got the same sorting here. And what we can actually do is go up and down the list here. We can actually use the shift up and shift down to move any session in any order that we want. And we can even pin them with control t if you wanted to. So you can have loads of agents operating at the same time. See this summary level view and then actually pin some or jump into the detail if you want to. Now right now this sorting by repo does not go down to the subfolder level which is something I'm hoping they're going to add in the future. The way that we organize our aentic operating system is that we have a clients folder and we jump into that individual client's context. So, say I was operating within that client's folder. You can see up here, client/acme corp, tell me about the brand voice for this client. So, we're operating within that client folder. But when we actually go backwards into the agent view, it still appears under the same sorting at the parent folder level. What would be brilliant in the future is if we can sort by subfolder levels, so that we can actually operate within multiple clients and just see all the tasks for all of our different clients in separate aggregated groups down here. So if we jump back to the status view on those that need input, we can see the names of the different sessions and flick through those. We can see the last output that Claude code has given us and also when we last discussed something with this conversation or how long it's been waiting for our input for example. Now we can of course jump into the detail of any of these conversations. So if we wanted to jump into the meta skill system creator, we now get a recap at the bottom. We get the ability to control this session specifically from the remote control view and we can reply directly in the conversation but still see all the full context as if it was a claw code terminal session. So we just need to hit back on our keyboard or left on our keyboard to jump back and right to jump into that session. Now what's more useful is you can actually talk to those sessions directly from this interface. So if we hit spacebar and we go up and down we see the latest status for all these different conversations and we can reply directly in here. Let's see if we can actually approve from this window too. So a couple of them are waiting approvals. Let's see if actually by typing approve we can push through the approval at this point. Now there is one limitation here. It's terminal only at the moment. So we don't have access to the desktop app when doing this but I'm sure soon in the desktop app they'll have a similar interface to interact with multiple sessions. It didn't seem to actually give the approval in that session. So we needed to jump in and actually approve it manually. Now the big question is you set up your Aentic operating system or your clawed operating s system. How do we actually use this in conjunction with that? And it's actually pretty simple because the Aentic OS is just a folder structure at the end of the day that injects context at the right time. So it's just pulling in your brand context, your client context, your scheduled jobs at the right time. So, if you've got your operating system architecture already built, then each conversation is going to benefit from the context. And now you can just operate multiple conversations at one time without flicking through multiple terminals to try and work out which ones need input and which ones don't. So, go and check it out for yourself and see what you think. I'm curious whether this will stop you using other UIs. So, let me know below and make sure you subscribe if you haven't already. See you in the next one.