01What is Claude Code 2.0 and how does it work?

What is Claude Code 2.0? It is a version of Claude Code that turns one Claude into a whole team, with the desktop app built for running lots of sessions side by side.

The big shift is how you work. Before, you waited for Claude to finish, and then you started the next thing. Now your sessions can start each other, report back to each other, and keep going after you close your laptop.

In this episode, Julian Goldie does not just list the features. For each one, he shows a real workflow you can build, along with the prompt that runs it. There are seven workflows in total, and each one is a job you can picture handing to a small team.

The video version of the episode was itself made with Claude Code. One Claude researched every feature in Anthropic's official docs, while the main session set up the tools needed to make it.

02Main features in Claude Code 2.0

Here are the main features covered in the episode, and what each one does for you:

  • Nested sessions: sessions that start their own sessions and report back when they finish.
  • Split view: two sessions open right next to each other.
  • Side chats: a quick question that does not clutter your main task.
  • Projects: one ongoing conversation where Claude coordinates a stream of related work.
  • Cloud sessions: work that runs on Anthropic's servers, even when your laptop is closed.
  • Remote control: a way to check in on a session from your phone.
  • Built-in browser: a browser pane next to your chat, where Claude can check its own work.
  • Artifacts: live web pages on a private Claude.ai link.
  • Computer use: Claude clicks, types and reads the screen in the apps on your computer.
  • Mods: plugins that change how Claude Code looks and behaves.

The rest of this article walks through how each one is used.

03How to get Claude Code 2.0 and get started

Getting started takes two moves: update the app, then open the right tab. After that, the best plan is to build up slowly, one workflow at a time. Here is the order to follow:

  1. Update the Claude desktop app.
  2. Open the Code tab.
  3. Start with the first workflow. Ask Claude to research two things in parallel, and watch the sessions report back.
  4. Try the second workflow. Open a second session in split view, and have one session write while the other checks.
  5. Once that feels easy, start your first project and let Claude run the threads for you.

This order matters because each step teaches you something the next step needs. You see sessions reporting back first. Then you learn to watch two at once.

Only then do you hand a whole stream of work to a project. Starting small also protects your usage limits, which are covered further down.

04Nested sessions and split view: the research team and review desk

The first workflow is the research team, and it uses nested sessions. When you ask Claude to run tasks in parallel, it starts a separate session for each one. They show up under your main session in the sidebar, and each one reports back when it is done.

The example prompt asks Claude to research your top three competitors in parallel, with one session each, to find their offers, prices and best content, and then give you one summary table. Claude suggests the tasks, you click Start All, and three sessions go to work at once.

The second workflow is the review desk. Hold Option, or Alt on Windows, and click a session in the sidebar. It opens right next to the one you are in.

  • The writer session on the left drafts your sales page.
  • The checker session on the right checks every claim against your offer and flags anything that does not match.

If you have a quick question mid-task, press Command and semicolon, or type /btw. That opens a side chat. It reads the main conversation but adds nothing back, so your main task stays clean.

05Projects, cloud sessions and remote control

The third workflow is the content engine, and it uses projects. A project is one ongoing conversation where Claude coordinates a stream of related work. You say what needs doing, and it starts a thread for each task, usually in the cloud and in parallel.

It keeps track of every thread and sees what each one reports back. For example, you can ask it to turn one piece of content into a blog post, a newsletter and five social posts.

The fourth workflow is the overnight shift. A cloud session runs on Anthropic's servers, so it keeps working after you close your laptop. There are two ways to start one:

  • In the desktop app, pick an environment under Cloud.
  • In the terminal, use the Claude command with its cloud option, then add your task.

Before bed, you could ask it to check every page in your website's repo for broken links and missing page titles, fix what it can, and give you a report. In the morning, the report is waiting.

Remote control lets you check in from your phone. Type /rc in a session on your computer, then open the Claude app on your phone, and you are in the same session. Your computer just needs to stay on.

06The built-in browser, artifacts and computer use

The fifth workflow is the live dashboard. Press Command, Shift and B, and a browser opens as a pane next to your chat. Claude can open your app, click through it and check its own work.

When it wants to visit a new site, you choose one of three options: allow once, always allow, or deny.

Then you can ask for an artifact that tracks your leads this week, with a chart and a table. Claude publishes it as a live web page on a private Claude.ai link, and it keeps updating as you work. Click Share to send it to your team or a client.

The sixth workflow is the desktop assistant, which uses computer use. It is for apps that do not have a connector. You switch it on in settings, under Enable Computer Use.

The example prompt asks Claude to open your spreadsheet, copy this week's sales numbers into your report template, and save it as a PDF. Claude asks before it touches each app, and you choose to allow it for this session or deny it. This is a research preview on Mac and Windows.

07Make Claude your own with mods

The seventh workflow is about making the tool fit you. A mod is a plugin that changes how Claude Code looks and behaves. Here is what a mod can add:

  • A panel next to your chat.
  • A band above the prompt.
  • New slash commands.

You have two ways to get one. The first is to ask Claude to build it. The example in this episode asks for a mod that shows your to-do list in a panel beside the chat, so your list stays in view while you work.

The second way is to install an existing mod with /plugin install.

There is one rule to remember here. Mods run with your permissions, so only install ones you trust. That means a mod can do what you are allowed to do, which is why the source matters.

If you did not build it yourself, think about where it came from before you add it.

08Claude Code 2.0 tips, limits and mistakes to avoid

The main limit is usage. All of this runs on your plan's usage limits, and more sessions means more usage. Here is how each feature affects them:

  • Every nested session sends its own requests.
  • Projects use your limits faster.
  • Cloud sessions share the same limits as the rest of your Claude usage.

So if you run 10 sessions at once, you will hit your limit a lot sooner. The fix is simple: start with two or three sessions, and build up from there. You can always add more once you see how fast your limits go.

A few other things are worth keeping in mind:

  • Side chats are not saved once you close the app, so do not keep anything important only in one.
  • Remote control needs your computer to stay on.
  • Computer use runs on your real desktop, so keep an eye on it.
  • The browser asks before visiting a new site, so pick always allow with care.

09What is Claude Code 2.0 good for, and who should use it?

The workflows in this episode are everyday business jobs. That is the best way to judge whether Claude Code 2.0 fits you. Look for your own work in this list:

  • Researching competitors and their prices.
  • Drafting a sales page and checking its claims.
  • Making blog posts, newsletters and social posts.
  • Checking a website for broken links and missing page titles.
  • Tracking leads in a chart and table you can share.
  • Moving sales numbers from a spreadsheet into a report.

It matters because you no longer have to sit and wait for one task before you start the next. Several sessions can work at once, and some can keep going while you sleep. You stay in charge by choosing what each one is allowed to touch.

Julian shares every prompt and workflow from this episode, plus the Claude Code skills he uses to run them, inside the AI Profit Boardroom, which has over 3,400 members.