Big Idea

The argument in one line.

Claude's native Agent View dashboard lets you manage multiple agents running simultaneously from a single terminal interface, eliminating the need for separate windows or third-party dashboards.

Who This Is For

Read if. Skip if.

READ IF YOU ARE…

A developer or AI operator running multiple Claude Code agents simultaneously who currently juggles terminal windows and wants a native dashboard to monitor them all at once.
Someone building an agentic operating system with folder-based context injection for clients or brands who needs to understand how Claude's Agent View integrates with that workflow.
A user on Claude 2.10.139+ who has existing agent sessions scattered across terminals and wants to consolidate them into a single managed view with sorting and pinning options.

SKIP IF…

You're still working with single-agent workflows or babysitting one ChatGPT window at a time — this is built for concurrent multi-agent management, not sequential prompting.
You're on Claude versions below 2.10.139 or don't have access to Claude Code's research preview features — the Agent View isn't available to you yet.
You need subfolder-level sorting within your repo structure — the current implementation only sorts by top-level repo, not nested directory hierarchies.

TL;DR

The full version, fast.

Anthropic shipped a native multi-agent dashboard inside Claude Code called Agent View, solving the problem of juggling five terminal windows when running parallel agents. After updating to version 2.10.139 or higher, run `claude agents` to open a summary dashboard, then migrate existing terminals in by typing `/bg` to background each session. From the dashboard you sort by status or repo with Ctrl+S, reorder with Shift+Up/Down, pin with Ctrl+T, spin up new tasks from the bottom prompt, and reply or approve across sessions via the spacebar quick-reply. Pair it with a folder-based agentic OS � a clients directory that injects brand and context per conversation � so every parallel agent works from the right brief without manual context-switching.

Free for members

Chat with this breakdown — free.

Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.

Create a free account →

Chapters

Where the time goes.

00:00 – 00:49

01 · The problem + the reveal

Agents are powerful but multi-agent management is chaos — five terminal windows, community workarounds, dashboard sprawl. Anthropic shipped Agent View natively inside Claude Code.

00:49 – 01:07

02 · How to enable it

Must be on Claude Code v2.10.139+. Run 'claude --version' to check, 'claude --update' to upgrade, then 'claude agents' to enter the summary view.

01:07 – 02:25

03 · Migrating sessions + basic navigation

Use /bg to background existing terminal sessions — they appear instantly in Agent View. Sorted by status by default. Ctrl+S for repo sort, Shift+Up/Down to reorder, Ctrl+T to pin.

02:25 – 03:44

04 · Current limitations

Repo sort only works at the parent folder level — no subfolder grouping for multi-client setups yet. Simon demonstrates the gap and flags it as a future request.

03:44 – 04:55

05 · Deep-diving sessions + approvals

Jump into any session for full context view. Spacebar opens a quick-reply interface. Typing 'approve' attempted batch approval — partially worked, still needed manual jump-in.

04:55 – 05:35

06 · Pairing with the Agentic OS

The Agentic OS is just a folder structure that injects context (brand, client, scheduled jobs) at the right time. Agent View is the control plane on top. Each session benefits from the context automatically.

Atomic Insights

Lines worth screenshotting.

Claude Code's native Agent View terminal dashboard is Anthropic's answer to the proliferation of third-party multi-agent UIs — it ships the management layer that the community had been building as workarounds.
Sorting agents by repo rather than status is the view that makes multi-project work legible: you can see all tasks in a specific codebase or client folder grouped together without switching terminals.
Backgrounding existing sessions with /bg and migrating them into Agent View converts fragmented terminal windows into a unified dashboard without interrupting the work in progress.
Pinning specific agents with ctrl+t and reordering with shift+up/down means the dashboard reflects the human's current priorities rather than chronological session order.
An Agentic Operating System as a folder structure that injects context at the right time is compatible with Agent View because the OS is not a UI — it is the data layer that each session reads, regardless of how sessions are managed.
The client subfolder limitation — sorting by repo but not by subfolder — is the gap that matters for agencies operating multiple client contexts: until subfolder-level sorting ships, a workaround is required to separate client work visually.
Agents getting to 90% of the output from a good prompt is the capability threshold that makes multi-agent management the bottleneck — the problem is no longer 'can the AI do this' but 'how do I manage multiple agents doing multiple things simultaneously.'
Talking to a session directly from the summary view — without jumping into the full terminal — is the productivity behavior that Agent View enables: brief responses, approvals, and status checks without losing the dashboard context.
The pattern of building third-party dashboards (Vibe Kanban, TMux, custom command centers) before Anthropic ships a native solution is the standard adoption curve for developer tools — the community solves the pain first, then the platform formalizes it.
Terminal-only availability at launch means desktop app users cannot use Agent View yet — which is the constraint that determines whether an experienced terminal user will switch from their existing workflow.
A Agentic OS folder structure that injects brand voice, client context, and scheduled jobs is the abstraction layer that makes every session in Agent View context-aware without manual setup per session.
Managing multiple agents from a single dashboard without five terminal windows is not a convenience improvement — it is the operational requirement for any solo operator running concurrent work streams across multiple clients or projects.
Seeing the last output and time-since-last-input for each session in the summary view enables triage: you know immediately which agents need attention and which ones are running without checking each one individually.
Approving agent actions from the summary view — type approve without jumping to the full terminal — is the workflow that keeps the human in the loop without the context switch cost of switching terminals for each approval.
The multi-agent management problem is the next frontier after the single-agent quality problem: once individual agents reliably execute complex tasks, the constraint moves to how many can a single human effectively supervise simultaneously.

Takeaway

The two-layer pattern.

Steal this architecture

Agent View is the cockpit; the Agentic OS folder structure is the engine — and you can build the engine first, then drop the cockpit on top later.

Map your projects as folders with CLAUDE.md context files at each level — this IS the Agentic OS.
Use /bg to hand off any running session to the dashboard without losing state.
The subfolder-sort gap is a real product hole — position JoeFlow's Sessions panel as the fix (client-level grouping out of the box).
Simon's 'limitation-first' honesty pattern (show what doesn't work) is a trust-builder worth copying in your own tutorials.
The format: Problem → Reveal → Enable → Demo → Limitation → Integration — all in under 6 minutes. Time it for your next tool tutorial.

Glossary

Terms worth knowing.

Agent View (Claude Code): A built-in terminal dashboard in Claude Code that displays all running agent sessions in one place, allowing users to monitor status, switch between sessions, and send replies without juggling multiple terminal windows.
TUI (Terminal User Interface): A text-based graphical interface that runs inside a terminal, using keyboard navigation and layout to replicate the feel of a GUI without a graphical window system.
Agentic OS (operating system): A folder-based organizational structure that automatically injects relevant context (client briefs, brand voice files, scheduled tasks) into AI agent sessions depending on which directory the agent is launched from.
TMux: A terminal multiplexer that lets users split one terminal window into multiple panes and manage several shell sessions simultaneously — commonly used to run parallel processes.
Research preview: An early-access release of a software feature that is functional but still under active development, made available for user testing before the full stable launch.
Context injection: The practice of automatically including relevant files, instructions, or data in an AI agent's prompt based on the current working directory or project structure, without the user having to paste it manually each time.

Resources

Things they pointed at.

00:00toolVibe Kanban

00:00toolTMux

00:49linkClaude Code Agent View docs ↗

00:49productSimon's Skool community (Scrapes) ↗

Quotables

Lines you could clip.

00:42

“It was dashboard crazy. So it's honestly about the time that Anthropic stepped in and shipped something native.”

Clean problem-to-solution pivot, no setup needed→ TikTok hook↗ Tweet quote

05:01

“The AgenTek OS is just a folder structure at the end of the day that injects context at the right time.”

Demystifies the concept in one sentence — shareable insight→ Newsletter pull-quote↗ Tweet quote

02:40

“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.”

Sells the value proposition concisely→ IG reel cold open↗ Tweet quote

The Script

Word for word.

Read-along

Don't just watch it. Burn it in.

See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.

metaphoranalogy

Agents have gotten really good, and we're no longer sitting in one ChatGPT 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.

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 Kanban who built a Kanban style UI, TMux 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 ClawCode agents built right into ClawCode. So let me show you how to get the most out of it and how it pairs with your own Agencik 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 dash dash version. It will tell you exactly which version you're on, and you need to be on 2.10.139 or higher.

So we're gonna go Claude dash dash update in our terminal, and it's gonna effectively make sure you're up to date. We're then gonna just run Claude agents, and you're gonna pop into the summary view, and you're gonna gonna become really familiar with this view because it's the high level 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 any existing sessions and you start the agent view, this will appear blank.

So we'll go to an existing session, and what we can do is just hit slash b g, continue this session in the background, and free the terminal. It's gonna 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 gonna 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.

It 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. I'm gonna 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 control 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 this 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 gonna add in the future. The way that we organize our agentic operating system is that we have a client's 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 slash 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 Metascale 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 Clawd 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 space bar and we go up and down, we'd 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 if a couple of them are awaiting 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 Agencik operating or your Claude operating system. How do we actually use this in conjunction with that? And it's actually pretty simple because the AgenTek 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 gonna 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.

The Hook

The bait, then the rug-pull.

For months the multi-agent management problem was a DIY sport: Vibe Kanban, TMux scripts, homemade dashboards. Then Anthropic shipped something native — and Simon Scrapes spent five minutes showing exactly how to use it.

Frameworks

Named ideas worth stealing.

04:55model

The Agentic OS

A folder structure that injects context (brand, client, scheduled jobs) automatically into Claude Code sessions via CLAUDE.md files at the right directory levels. Agent View becomes the control plane on top.

Steal forJoeFlow Sessions panel architecture — each project folder = context scope, Agent View = cockpit

02:25list