Skip to content
Agentic Levels

Everything starts here.

GuestLocal progress only
PreferencesSign in
01Start with one taskBest first move for beginners.02Check your LevelMeasure where you are.03Score an AI resultFind the habit to practice first.04Return to Your WorkScores, links, and checkpoints.
Start here

Begin

HomeThe main entry point.New to AIStart with one useful task.
Know where you are

Measure

Check your LevelUse this after you have tried AI.Fluency ScoreScore an AI result you can review.
Build the habit

Learn

LevelsLessonsTracks
Find the reference

Library

PromptsReferenceResourcesCompare Tools
Turn it into work

Apply

Your Next MoveChoose what AI should change next.Tool SetupGet the tools ready.
Come back later

Return

Your WorkScores, links, and checkpoints.My PathContinue from your level.Updates
Site

Site

PricingAboutFAQ & FeedbackPreferences

© 2026 Fuentes Studio

Privacy·Terms
yourCouncil
Ready to help
✦

What do you want to understand?

Ask anything about what you're learning.

Tracks›Claude Fundamentals
L5Lesson 2Free

The Code tab in the desktop app: the click-through door in

The third tab of the desktop app you already installed

After this, you'll be able to describe the Code tab as the Claude Code door inside the same desktop app you installed in Module 5, say why it is the most approachable of the several surfaces for a non-developer, and explain what it costs and what it needs to run.

Before you start

Complete What Claude Code actually is first; this lesson zooms into the desktop app, the most approachable of the several surfaces you met there.

The idea

This is not a separate program; it is the Code tab of the same Claude Desktop app you installed in Module 5. That app has three tabs: Chat (the plain conversation), Cowork (the background worker from Module 5), and Code (Claude Code in click-through form). Click the Code tab, point it at a real project folder, and ask Claude about the code in plain English.

The learner starts the code tab in the desktop app: the click-through door in with this risk visible: Hunting for a separate 'Claude Code desktop app' to download. It is the Code tab of the desktop app you already installed in Module 5.
The learner starts the code tab in the desktop app: the click-through door in with this risk visible: Hunting for a separate 'Claude Code desktop app' to download. It is the Code tab of the desktop app you already installed in Module 5.

It requires Claude Code access through your plan, and on Windows it asks you to install a free helper called Git for Windows the first time. Of Claude Code's several surfaces, this is the gentlest door for someone who does not live in a terminal. The experience is buttons and panels, not commands you have to memorize.

A "project folder" (developers call it a codebase) is just the folder holding all the files for one piece of software. You do not need to understand those files. You open the folder and ask Claude what is going on, and it reads the code for you.

Here is the before and after: Before, a developer says "Claude Code is amazing" and you picture a black window full of typed commands and tune out. After, you know one of its doors is the Code tab of the desktop app you already have, the same window where Chat and Cowork live.

Now try it: say back, in one sentence, where the Code tab lives and how it differs from the terminal version. It is the desktop app's Code surface, click-through, pointed at a project folder, on a plan with Claude Code access.

It is the third tab (Code) of the desktop app you already installed, paid, and pointed at a real project folder, not a new download.

The Code tab in the desktop app: the click-through door in mapThe code-surface map works when the setup choice, proof step, and next action stay connected.
Code-adjacent questionThe starting request, source, setup, or surface before the lesson shapes it.
Code surface selectionThe practical pass that turns the lesson concept into a usable Claude habit.
1Repo and risk checkThe proof step that keeps the result honest before use.
say what the desktop app's Code tab doesThe finished outcome the learner can inspect and repeat.
Next confident Claude actionThe point where the learner can keep working without guessing.

Try it (8 min)

Watch out for

  • Hunting for a separate 'Claude Code desktop app' to download. It is the Code tab of the desktop app you already installed in Module 5.
  • Picturing Claude Code as only a black terminal window. The Code tab is the same tool in a normal click-through app.
  • Expecting it on a free plan. The Code tab, like every Claude Code surface, needs a plan with Claude Code access.
  • Forgetting the Windows setup step. On Windows the Code tab asks you to install Git for Windows, a small free helper, the first time you open it.
  • Thinking it works without a project. The Code tab needs a real project folder to point at, or it has nothing to read.

Paste this into Claude

I am not a developer. I already installed the Claude Desktop app, and I have heard it has a "Code" tab that is Claude Code. I want to understand that tab before I ever click it. Please:

1. Confirm, in plain English, that the desktop app has three tabs (Chat, Cowork, and Code) and that the Code tab is Claude Code inside the same app I already have, not a separate download.
2. Explain how that Code tab differs from the terminal (typed-command) version of Claude Code. I have heard it is the same tool, just click-through.
3. Tell me what a "project folder" or "codebase" is, and why the Code tab needs one to be useful.
4. Confirm what it costs (I believe it requires Claude Code access through your plan) and anything it has to install first (I have heard Windows needs something called Git for Windows).
5. Tell me honestly: as a non-developer, would I run this myself, or mostly recognize it when a developer is using it?

Do not assume I know any technical terms. Explain each one as you use it.

Created by potrace 1.16, written by Peter Selinger 2001-2019 What good looks like

  • Claude confirms the desktop app has three tabs (Chat, Cowork, Code) and that the Code tab is Claude Code inside the same app, not a separate program
  • Claude explains the Code tab is the same Claude Code tool as the terminal, in a click-through window
  • Claude defines 'project folder' or 'codebase' and says why the Code tab needs one
  • Claude confirms it requires a plan with Claude Code access and notes the Windows Git for Windows step
  • Claude tells you a non-developer mostly recognizes it rather than runs it, and never asks you to write code
M6 02 Proof PathMove through The Code tab in the desktop app: the click-through, check proof, then fix only the weak part.
yesnorun it again
StartBegin with the real task
The Code tab in the desktop app:After this, you'll be able to describe the Code tab as the Claude Code door inside
1Proof visible?Claude confirms the desktop app has three tabs Chat, Cowork, Code and that the Code
Ready to useState in one sentence that the Code tab is the third tab of the desktop app you
Fix the weak partBreaks when you go looking for a standalone Claude Code download because there is not

When this breaks

  • Breaks when you go looking for a standalone Claude Code download because there is not one; the Code tab lives inside the same Claude Desktop app you already have alongside Chat and Cowork.
  • Breaks when you open the Code tab with no project folder to point at because it reads a real codebase, so with nothing loaded it has nothing to explain.

AI can help with this

Paste this into Claude: 'The desktop app has a Chat tab, a Cowork tab, and a Code tab. Explain the Code tab in plain English. How is it different from the terminal version of Claude Code, what does it cost, what does it need to run, and would a non-developer like me actually use it?'

The lesson rule resolves it and proves the result with this check: Claude confirms the desktop app has three tabs (Chat, Cowork, Code) and that the Code tab is Claude Code inside the same app, not a separate program

Created by potrace 1.16, written by Peter Selinger 2001-2019 You can now

✓

You can complete the lesson outcome in a real Claude chat, Project, Artifact, Connector, Desktop, or Code surface.

  • ✓You can verify that claude confirms the desktop app has three tabs (Chat, Cowork, Code) and that the Code tab is Claude Code inside the same app, not a separate program.
  • ✓You can verify that claude explains the Code tab is the same Claude Code tool as the terminal, in a click-through window.
  • ✓You can verify that claude defines 'project folder' or 'codebase' and says why the Code tab needs one.
  • ✓You can verify that claude confirms it requires a plan with Claude Code access and notes the Windows Git for Windows step.

Key takeaways

The desktop app's Code tab is the click-through door into the Claude Code engine, and it lives inside the same Claude Desktop app you installed in Module 5 (alongside Chat and Cowork). It requires Claude Code access through your plan, points at a real project folder, and on Windows asks for Git for Windows first. A non-developer mostly recognizes it rather than runs it.

  1. 1Treat the Code tab as the third tab of the desktop app you already have, not a separate program to download.
  2. 2Remember it is one of the gentlest Claude Code surfaces: same tool, but a tab you click, not a terminal.
  3. 3Remember it is paid like every Claude Code surface, with no free version, and on Windows it wants Git for Windows on first run.
  4. 4As a non-developer, expect to recognize it and read its output, not run it day to day.

Created by potrace 1.16, written by Peter Selinger 2001-2019 Go deeper

  • Anthropic: Claude Code overview
  • Compare Claude tools and surfaces

Was this helpful?

Up nextClaude Code inside the editor: the VS Code and JetBrains add-ons→
← Back to Claude Fundamentals