The Standard of Claude Code: Practical Agentic Engineering
This will be the definitive guide to Claude Code. This course dives deep into how and why Claude Code works, teaches you how to directly apply the components of harness engineering, and even dissects actual production code. Take the know-how of a developer with over 10 years of experience and transform into a key talent in the era of AI agents.
197 learners
Level Intermediate
Course period Unlimited
[Practical Tips] EP.02 Agent View - Performing Parallel Tasks with Claude Code
Hello, the second series of the Claude Code practical tips lecture has been updated!
This topic covers Claude Code's new Agent View feature. I have summarized how to work in parallel by gathering multiple Claude sessions on a single screen.
I've tried various tools to run multiple sessions at once, but after switching to Agent View myself, I've put together some practical insights on which situations actually speed up your workflow and what points you need to be careful about.

(Practice screen within the lecture)
Have you ever experienced this? When using Claude Code, you eventually reach a moment where you think, "I wish I could run several of these at once." You want to have one instance fixing a bug, another reviewing a PR, and yet another investigating a failing test. So, you open two, three, four terminal tabs. Before you know it, this happens: Which tab was finished? Which one is waiting for my response? Is this tab still running or has it stopped? You end up clicking through the tabs one by one to check.
Agent View eliminates that tab switching. It lines up all active sessions row by row and shows you what's in progress, what's waiting for you, and what's finished, all on a single screen. Just one claude agents command opens that dashboard.
But first, we need to clear up one misunderstanding.
It is easy to perceive Agent View as simply a "screen where you can view multiple sessions at once." However, the real core is not the screen itself, but the fact that it changes the way we approach work.
In the past, when I gave Claude a task, I would sit in front of that chat and wait until the answer arrived. Work progressed one at a time, and only while I was physically present. Agent View flips this. You can assign tasks to multiple sessions, let them run on their own, and then simply handle the ones marked "Input Required" in the list like notifications. The sessions don't stop just because you leave. The unit of work shifts from "a single conversation I'm tied to" to "multiple sessions running independently."
I have updated two lectures where you can experience both theory and practice. Please give them a listen and try applying them to your actual work :)

+As a side note, the Agent Teams Operation Manual lecture, which was scheduled for update within June, has also been updated!

I will be rooting for your learning journey.
I will be back with more helpful news next time.
Thank you.




