● Claude training · Page 2 · Screen by screen · 30 Oct 2026

Claude, screen by screen.

21 screens in the order the trainer shows them. Left: what is on screen. Right: the clicks to copy. Each screen has a small ▶ timestamp link if you want to see it. Everything runs in the Claude desktop app.

▶ Original video: Vaibhav Sisinty, 32 min Use Claude the new way: 14 features from deep research to six sessions at once
Intro

The tab you have never opened

▶ 0:00
On screen

He opens with a finished research report and points at the Code tab. The name sounds like a black terminal for engineers. Today it lives inside the Claude desktop app and looks like the normal chat box.

Do it yourself
  1. Download the Claude desktop app (Mac or Windows). Everything in the video runs there, not in the browser.
  2. Find the Code tab next to Chat. Do not worry about the name. You will not write code.
01

A full research report from one prompt

Code tab · Pro+▶ 0:55
On screen

In the Code tab he opens Artifacts, starts a new doc and types one line: do deep research on cryptocurrency, run five parallel sub-agents. Claude writes itself a to-do list first, then a doc opens and fills up while the research runs. A Background tasks panel shows five helpers, how many are done and which model each uses.

Do it yourself
  1. Code tab → Artifacts → New doc.
  2. Type: Do deep research on [topic]. Run five parallel sub-agents.
  3. Watch the to-do list, then open Background tasks to peek at any helper.
  4. Edit the doc like a Google Doc: tables, images, checklists, wider page.
  5. Share: private, anyone with the link, or invite a viewer or editor. Export to Word, PDF, Markdown or Google Docs.
Proof

Three things normal people built

▶ 3:41
On screen

Three real builds from Reddit and X. One man replaced the ad-filled Samsung TV home screen with a clock and only his apps. Another wired a USB lamp to Claude hooks so it lights up when Claude needs him. A third rebuilt a slow Plex app for his LG TV. None of them are engineers. They described what they wanted.

Do it yourself
  1. Write down one daily annoyance that no company will fix for you. That is your first Code tab job.
Chat

The chat box you already know

Free plan▶ 5:12
On screen

Back in the normal chat. He shows the model picker and effort level in the box, the permission picker next to it, dictation, voice mode, and Search, which looks through chats, artifacts, sessions, projects and scheduled tasks at once.

Do it yourself
  1. Big model + high effort for hard work. Turn both down for quick questions.
  2. Use dictation or voice mode when a problem is easier to say than type.
  3. Use Search to find anything you made with Claude.
02

Projects: one background per job

Chat▶ 6:13
On screen

He opens a project used for his community resources. Every chat inside shares the same instructions, files and folder. He then makes a new one called test.

Do it yourself
  1. Projects → New project.
  2. Give it a name and say what it is for.
  3. Add instructions and files: the brief, brand guide, notes.
  4. Create. Every new chat inside it already knows the client.
03

Artifacts: your own little workspace

Free plan▶ 7:16
On screen

The Artifacts page shows every doc, deck, design and dashboard Claude made, as tiles you can share by link. It works the same in chat and in the Code tab.

Do it yourself
  1. Open Artifacts in the sidebar.
  2. Pick up last week's file and keep going.
  3. Send any artifact to family, friends or your team as a link.
04

Scheduled tasks: the 8 AM brief

Paid plan▶ 7:50
On screen

A morning brief appears at 8 AM with the day's calendar and important emails. Nobody typed anything. To set it up he clicks Scheduled → New task → Create with Claude and types one sentence. Claude asks him to connect Gmail and Calendar and asks two questions.

Do it yourself
  1. Scheduled → New task → Create with Claude.
  2. Type: Set up a scheduled task that gives me a morning brief each day at 8 AM. Keep it short and scannable.
  3. Connect Gmail and Calendar when asked. Answer its questions.
  4. Run now to test it. Pause, edit or delete any time.
  5. Or start from a template: daily briefing, inbox triage, meeting prep, weekly review, content ideas.
05

Skills: teach a job once

Chat▶ 9:45
On screen

He opens Discover with 57 categories of ready-made skills (Engineering alone has over 1,200). Under Customize he switches on built-in skills. Then Add → upload, create with Claude, or record your screen. On a Mac Claude watches the recording and turns it into a skill.

Do it yourself
  1. Customize → Skills. Switch on the built-in ones you need.
  2. Discover: search your job before you write your own. Someone has probably done it.
  3. Add → Record screen. Do the boring task once (for example the daily Google Sheet update).
  4. Good skill ideas: client proposal format, weekly report, pre-invoice checklist.
06

Claude Design: your brand, set once

Free plan▶ 11:34
On screen

He shows a 5-slide deck on Claude's top slash commands, all in one style, made in the Design tab. If Design is not in the sidebar: More → Edit sidebar → drag it up → Done. Inside he builds a design system: colours, type, spacing, corner radius, components, accessibility and icons. Then asks for the deck on Opus 5.5 at medium effort. Every slide stays editable.

Do it yourself
  1. More → Edit sidebar → drag Design up → Done.
  2. Design → Design system: add your colours and fonts, or describe the feel you want.
  3. Ask: Five-slide presentation on [topic] using my brand.
  4. Click any text to change it, or leave a comment on a slide and let Claude fix it.
  5. Motion (video) is beta on Team and Enterprise only.
07

Connectors and plugins

Chat▶ 13:48
On screen

Customize → Connectors → Gmail → Add. A browser opens, he logs in and comes straight back connected. Then plugins: he copies the GitHub link of a design plugin, goes to Customize → Plugins → Create with Claude, pastes the link, picks Install and chooses both the Claude app and Claude Code.

Do it yourself
  1. Customize → Connectors → pick Gmail or Notion → Add → log in.
  2. Ask: Find the last three emails from [client] and tell me what they are waiting on.
  3. Plugins: copy a plugin's GitHub link. Do not download anything.
  4. Customize → Plugins → Create with Claude → paste the link → Install → choose app, Code, or both.
08

The Code tab, for non-coders

Code tab · Pro+▶ 15:45
On screen

Same chat box, but Claude works inside your files. He picks where it runs: Local (your computer and files) or Cloud (keeps going when the app is closed). Then he picks a folder. The folder is Claude's desk. Docs, slides and design work on the free plan. The Code tab needs Pro or above.

Do it yourself
  1. Code tab → choose Local or Cloud.
  2. Pick one folder per job so Claude stays focused.
  3. Explain what you want in plain English, or your own language.
Modes

Permission modes: who decides?

Code tab · Pro+▶ 17:22
On screen

He opens the permission menu. Manual asks before every edit, command or web visit. Accept edits changes files in your folder without asking. Plan looks around, writes a plan and changes nothing until you approve. Auto skips routine questions while a second model checks each action. Example: clean up the Downloads folder. In Plan mode it first lists 40 files, invoices to one folder, photos to another, old installers deleted. Bypass in settings asks nothing. Anthropic says use it only on a spare test machine.

Do it yourself
  1. Start every new job in Plan mode.
  2. Read the plan. Say yes or change it before a single file moves.
  3. Move to Auto once you trust the job.
  4. Leave Bypass off.
Deck

A 9-slide deck in your own brand

Code tab · Pro+▶ 19:08
On screen

In the Code tab he opens Artifacts, picks the design system made earlier and types: create a presentation on Claude Cowork vs Claude Code. Environment is set to This computer, pointed at one new folder in Downloads. He skips Fast mode because it costs about double from extra usage credits.

Do it yourself
  1. Code tab → Artifacts → choose your design system.
  2. Type: Create a presentation on [topic].
  3. Point the environment at one new folder for the job.
  4. Leave Fast mode off unless you are in a hurry.
09

Remote control from your phone

Code tab · Pro+▶ 20:18
On screen

He types /remote-control on the laptop, opens the Claude app on his phone, and the same session is there, still working. He sends the next instruction from a taxi in Bengaluru traffic.

Do it yourself
  1. Type /remote-control in the session on your computer.
  2. Open the Claude app on your phone. The session is there.
  3. Check progress and send the next instruction on your way home.
10

Context, browser and files

Code tab · Pro+▶ 20:48
On screen

The Context panel shows how full Claude's whiteboard is (up to a million tokens). When it fills, Claude squeezes older parts into a summary by itself. He also shows the connectors panel, a terminal and a git view (not needed), the built-in browser (separate from your Chrome, so none of your logins) and the Files pane with every file Claude made.

Do it yourself
  1. Open Context to see how much memory is used.
  2. Use the built-in browser to preview what Claude built. It asks before it clicks or types on a site.
  3. Open and edit files in the Files pane without going to Finder.
11

Side chat with /btw

Code tab · Pro+▶ 22:10
On screen

While the deck builds he opens a side chat with Cmd + ; on Mac (Ctrl + ; on Windows) and asks what it is covering. Answer in seconds: slides 1 to 4 done, 5 to 9 planned. The main job never stops and nothing from the side chat goes back into it.

Do it yourself
  1. Press Cmd + ; (Mac) or Ctrl + ; (Windows), or type /btw.
  2. Ask anything. The main job keeps running.
  3. Side chats close when you quit the app.
12

Mods: change how Claude looks

Code tab · Pro+▶ 23:16
On screen

Mods came out at the start of October. He opens a new session and types: create a mod that shows a progress bar and the estimated cost while a task runs, trigger it with /agent-info. Claude writes the mod and reloads the app. The bar now appears when a prompt ends with /agent-info and disappears when the job is done.

Do it yourself
  1. New session → Create a mod that shows a progress bar and estimated cost while a task runs. Trigger it with /agent-info.
  2. Other ideas: a timer per job, an alert when a long task ends, a to-do panel next to the chat.
  3. A mod runs with your permissions. Only use mods you made or trust.
Projects

Projects inside the Code tab

Code tab · Pro+▶ 24:51
On screen

Here a project starts from a folder. Every chat inside shares that folder and its files. He makes a section called Crypto, moves an old chat into it and adds a new one asking what Bitcoin is. Scheduled tasks and Customize work the same as in chat.

Do it yourself
  1. Pick a folder → start a chat. That is the project.
  2. One project per big piece of work: a client, your channel, your business.
  3. Make a section and move older chats into it.
13

Seven slash commands

Code tab · Pro+▶ 25:51
On screen

He types a slash and his own YouTube editing skill pops up. Then seven commands, least used first: /advisor (a stronger model gives a second opinion at key moments), /clear (fresh session, empty memory), /usage or /cost (what the session cost), /doctor (checks your setup and fixes it), /deep-research (research job on a topic), /btw (side chat) and /goal.

Do it yourself
  1. Type / to see your skills and commands.
  2. /clear when Claude mixes up two jobs.
  3. /usage before a big job. /doctor when something breaks.
  4. /goal All ten product descriptions written, each under 100 words. Claude keeps going until a second model confirms the goal is met.
14

Six Claude sessions at once

Code tab · Pro+▶ 28:14
On screen

Six sessions on one screen, each on one part of the same YouTube video: thumbnail, title, outline, visuals, editing. He typed one prompt in the main session asking it to start a thread for each part. The main session acts like a producer. Each nested session has its own memory, so nothing gets mixed up. Drag sessions across, or ⋯ → Open in split view, to watch all six.

Do it yourself
  1. In the main session ask: Spin up a separate session for each part of this job: [part 1], [part 2] ...
  2. ⋯ → Open in split view for each session.
  3. Talk only to the main session. It hands you one plan at the end.
  4. On Pro and Max a cloud version is coming to Projects through a waitlist.
Plan

Your plan for this week

▶ 30:52
On screen

He ends with three steps to stop using Claude like a search box.

Do it yourself
  1. Tomorrow: type your next question into the Code tab in Plan mode. On the free plan, make a doc or a deck in chat.
  2. This week: set up one scheduled task.
  3. Turn one repeat job into a skill.
  4. Give one big job a /goal.

FAQ

Do I need to code to use the Code tab?

No. You type what you want in plain English, the same as in chat. Claude does the work inside a folder you choose.

Which Claude features work on the free plan?

The video says docs, slides and Claude Design work on the free plan. The Code tab needs Pro or above, and scheduled tasks need a paid plan.

What is the safest permission mode?

Start in Plan mode. Claude writes a plan and changes nothing until you approve. Keep Bypass off unless you are on a spare test machine.

What is the difference between sub-agents and nested sessions?

Sub-agents are helpers inside one session working on one job. Nested sessions give each part of a big job a whole session with its own memory, run by one main session.

Which slash command should I learn first?

/goal. You give a finish line and Claude keeps going until a second model checks that the goal is met.

Next · cheat sheet99 Claude Commands99 copy-ready slash commands in 9 groups: email, writing, thinking, planning, meetings and more. Click a card to copy.
Want Claude training for your team?

Hands-on sessions in Dubai, Abu Dhabi and Saudi Arabia, using your own files.

Corporate Claude training →AI learning class →