Many people now call the Claude desktop app "Claude 2.0". That is not an official name. It is a nickname that stuck after the Code tab of the desktop app changed a lot.
The changes are real, though. One conversation can start other conversations and hand work to them. You can ask a question on the side while work is running. Documents and dashboards are built right in the chat. So we picked one example and used the app from start to finish. We pretend to open a small café in Seoul and ask which neighborhood is better, Mangwon-dong or Seongsu-dong, using open commercial-district data from the city of Seoul. We wrote no code.
This post covers:
- What the Code tab is
- District research from a one-line request
- The session panel: environment, Remote Control, context
- Splitting work three ways with nested sessions
- Projects and side chat
- Building a dashboard, a business plan and slides
- Slash commands and shortcuts
- Limits
The companion video is in Korean.How to read the numbers. [Official docs] means documentation published by Anthropic. [Measured] means a result we saw on screen when we ran it in the Claude desktop app on our Mac. District numbers come from Seoul's commercial district analysis service, coffee and beverage category, Q2 2026.
1. What the Code tab is
The top right of the Claude desktop app has a speech-bubble button and a code button. The speech bubble is the chat we all know. This post is about the Code tab.
Despite the name, its job is simple. It reads a folder on your computer and creates files in it. Whether you clean up a spreadsheet or write a report, the result is a real file. Most of the recent changes landed in this tab (Claude Code desktop docs).
Before, several tasks meant several open conversations, and you had to remember where each one stood. In the new Code tab, Claude does that bookkeeping. A main session splits the work, and child sessions do it and report back.
2. District research from a one-line request
We opened a café folder and typed one line in plain language (in Korean).
- Research which is better for opening a café, Mangwon-dong or Seongsu-dong, using Seoul commercial district data.
Claude first made a plan and showed a to-do list inside the conversation: download the data, narrow down and compare the neighborhoods, write up the result. A check appears each time a step finishes, so you can see what it is doing without asking.
The data is the commercial district analysis dataset on Seoul Open Data Plaza. The sales file had about 16,000 rows and the store file about 35,000 rows [Measured].
The first result [Measured]:
| District | Estimated sales per store, one quarter |
|---|---|
| Seongsu 1-ga 2-dong | KRW 32.02 million |
| Mangwon 1-dong | KRW 13.30 million |
One line at the end of the result is worth noticing. Claude wrote that rent is not in the data, so it could not compare profit. It said what it did not know.
3. The session panel: environment, Remote Control, context
In the Code tab, one conversation is called a session. A button at the top right opens the session panel, which shows what is happening in the session as a few cards [Official docs].
- Environment card: shows which folder the session works in. Here it was the
cafefolder on our Mac. - Remote Control: turn it on and you can follow the same session from the Claude app on your phone. Start a task at your desk and check it while you are out.
- Context card: context is how much Claude holds in mind at once for this conversation. Think of it as the pile of papers spread out on a desk. Your messages take space, and so do settings files and connected apps.
When the pile gets too big, Claude summarizes the earlier part to free up space. This is called compaction. So a context number that is filling up is a signal to split the work into smaller units.
When the research finished, the card showed 14% used, 138 thousand of one million tokens. Below that it lists how much messages, connected tools and system settings each take [Measured].
4. Splitting work three ways with nested sessions
This is the biggest change. With nested sessions, a session starts new sessions under itself and hands work to them. Each child session reports its result to the session above when it finishes (Claude app changelog).
A subagent is similar. It is a worker that does a side task inside one session and returns only a summary (subagents docs). You cannot step in and talk to it midway. A child session is different. It is a real session, so you can open it at any time, see what it did and keep talking to it.
Why split at all? Because of the pile of papers. Research, price comparison and copywriting in one conversation fill the desk fast. Split up, each session carries only its own papers, and the main session receives reports and keeps the overall picture.
We typed this in the main session.
- Split this three ways and start one session for each: sales and store numbers by district, menu price ranges at nearby cafés, and opening promo copy.
What happened [Measured]:
- Before starting a child session, the app asks first. It asks whether to start a session with this name for this task and shows the instructions Claude will send to it. Approve, and it starts.
- The three sessions share one folder, so Claude told each session to edit only its own file.
- In the left sidebar, the main session sits under the
cafefolder with three child sessions indented below it. Click one and you can continue the conversation right there.
To see the files the child sessions made, click the number on the changes card at the bottom of the session panel.
menu-prices.md: written by the pricing session. The top says when and where the prices were checked. The table lists the neighborhood, whether the café is independent or a franchise, and the low, high and median price for each menu item. Cells it could not confirm are marked unconfirmed.promo-copy.md: written by the promo session. Customers differ by neighborhood, so it wrote separate copy for Mangwon and Seongsu.CLAUDE.md: a file a person wrote before starting. Claude reads this note first whenever it works in the folder. It holds the data address, the business category code and a rule never to show the API key on screen.
Child sessions leave their results as files. The main session reads those files again to build the dashboard and the plan.
Tip: use one session as a control room
With several sessions running, checking each one for a pending question gets tedious. Ask the main session instead.
- Is any session waiting for my answer right now?
A session in the Code tab can see the state of other sessions, so it tells you only what needs a decision. This time it answered that nothing was waiting and that all three child sessions had finished their files [Measured]. This is not a separate feature. It is a way of using a session.
5. Projects and side chat
Projects: goals that run for weeks
Projects are similar but bigger. Give Claude one goal that keeps producing work, and it starts a thread for each task you send (Projects docs).
- Threads mostly run in the cloud, not on your computer. They keep working after you close your laptop [Official docs].
- That also means the files they need have to go to the cloud. For material that must stay on your computer, nested sessions are the better fit.
- Projects are in public beta on Pro and Max plans and are rolling out account by account [Official docs].
The rule is simple. Use nested sessions to split work you will finish today. Use Projects for a goal that keeps producing work for weeks. Projects were not yet enabled on our account, so the menu did not appear in the sidebar. If you do not see it, you can join the waitlist.
Side chat: ask without interrupting
Sometimes a question comes up while Claude is in the middle of a long task. Asking in the main conversation interrupts the work and clutters the history. Open a side chat instead. Type /btw and your question, or press Cmd+; [Official docs].
/btw how much of this is left?
A side chat opened on the right and answered that one of the three sessions had finished and two were still running [Measured]. A side chat can read the whole main conversation so far, so it answers with context. What you say there does not mix into the main conversation.
One caution. Side chats are not saved to disk [Official docs]. If you need to keep something, move it to the main conversation.
6. Building a dashboard, a business plan and slides
Claude builds documents, slides, designs and dashboards right in the chat. These pages are called artifacts. An artifact starts private, and you share it by link when you want (artifacts docs).
Dashboard
- Build a dashboard comparing Mangwon-dong and Seongsu-dong with these numbers.
An artifact card appeared in the conversation first, then a new to-do list: pull the numbers, build the dashboard, check the screen. Claude first checked the numbers the child sessions had organized against the original data, then built the dashboard.
The top of the dashboard has five number tiles [Measured].
| Item | Mangwon | Seongsu |
|---|---|---|
| Estimated sales per store, one quarter | KRW 11.84 million | KRW 28.68 million (about 2.4x) |
What each tile means:
- Estimated sales: the city's estimate of what cafés in the area earned over the quarter.
- Store count: how many stores of the same category there are.
- Openings and closures: stores that opened and closed in the period. When both are high, the area has many customers and also fierce competition.
Scroll down for the share of sales by time of day and by age group. Seongsu was strongest at lunch, Mangwon in the afternoon and evening. The table at the bottom shows 596 cafés on the Seongsu side, 88 of them franchises, so competition is strong [Measured].
The numbers in section 2 (Seongsu 1-ga 2-dong and Mangwon 1-dong) differ from the tiles here, because the dashboard was built from the numbers the child session organized again. The ratio was about 2.4x in favor of Seongsu both times.
Business plan document
- Write a business plan document from what we have researched so far.
We gave no outline. Claude built the skeleton first and then filled the sections in order: summary, district analysis, target customers, menu and pricing, opening promotion.
One moment stood out. After finishing, Claude read the document again, found five places where the Korean word for Seongsu had been mistyped as a different word, and fixed them itself [Measured].
The document opens on the right. You can edit it yourself or ask Claude to. The summary gives a conclusion and also says the location is not decided yet because there is no rent data. The risk table names rent as the biggest gap too.
Slides to persuade the family
- Make five slides from this to persuade my family.
Claude wrote the slides one at a time from the cover and added short speaker notes to each. The second slide shows in large type that a café in Seongsu earns 2.4 times as much. The last slide says the decision comes after checking rent and lists four things to check. It left a blank for what to ask the family, to be filled in by hand. The deck can be downloaded as a PowerPoint file.
From the numbers to the presentation, everything stayed in one conversation.
7. Slash commands and shortcuts
Type / in the input box to see the available commands (commands docs).
| Command | What it does |
|---|---|
/recap | Summarizes where this session stands. Useful when you return after a few days. |
/output-style | Changes how Claude writes. If answers are long and hard, switch to a short, plain style. |
/doctor | Checks installation and settings. The first thing to try when something seems off. |
/skill-doctor | Shows how much context your skills (saved know-how for tasks) take up. |
/advisor | Works with a lighter model and asks a stronger model for advice only at important moments. |
/rewind | Returns the conversation and files to an earlier point. |
When we sent /recap, it summarized in two sentences that the research, dashboard, plan and slides were done and that the next step was to fill in the blank on the slides [Measured].
Three shortcuts are enough to remember [Official docs].
Cmd+;side chatEscstop the current responseCmd+/shortcut list
Summary
- Split work with nested sessions (work for today) or Projects (a goal that runs for weeks).
- Ask questions that come up midway in a side chat. Remember that it is not saved.
- Get results as a dashboard, document or slides right in the chat.
- If you are new, start with side chat. It cannot disturb the work in progress. Next, open the session panel, and then try nested sessions.
Limits of this walkthrough
- This is one run on one Mac, one account and one example (café district research). How sessions are split and what gets built can differ by request and situation.
- Sales are estimates based on card payment data and other sources, so they can differ from real store sales. Rent is not in the data. Use these numbers only as a starting point for a decision.
- We did not separately verify the menu prices and promo copy the child sessions produced.
- Projects are described from the official documentation.
- "Claude 2.0" is a nickname, and the app keeps changing. Check the latest official docs before you rely on any of this.
Watch the video
The same walkthrough with the real app on screen (in Korean).
Sources
- Anthropic, Claude Code desktop — Code tab, session panel, Remote Control, side chat, shortcuts
- Anthropic, Claude app changelog — nested sessions
- Anthropic, Projects — public beta on Pro and Max, cloud threads
- Anthropic, Artifacts — documents, slides, designs and dashboards; private first, shared by link
- Anthropic, Subagents
- Anthropic, Commands —
/recap,/output-style,/doctor,/skill-doctor,/advisor,/rewind - Seoul Open Data Plaza, Seoul commercial district analysis service (estimated sales and stores by administrative dong) — coffee and beverage category, Q2 2026 (KOGL Type 1: attribution)






