9 min · +150 XP
Your first session
How to talk to Claude Code, answer its questions, stop it and come back.
By the end of this lesson
You will have asked Claude Code for a small web page, opened it and changed it.
Claude Code is installed and you're logged in. Let's start with the real thing: you'll build your first web page. Then we'll go over what you saw on screen: the keys, the permission questions and how to come back tomorrow.
Your first small build
Build a hello page
0/6“Make a one-page web page called index.html that says Hello and shows today's date, on a calm dark background. When it is ready, open it in my browser.”
Claude writes the file, asks permission if needed, and opens the page.
“Make the text bigger and use a warm colour, then reload the page in my browser.”
Claude edits the same file. Look at the browser to check the change.
The simplest way is to ask, as in the cards above: "open index.html in my browser". You can also find the folder in Finder (Mac) or File Explorer (Windows) and double-click index.html. After each change, reload the page: Cmd+R on a Mac, Ctrl+R or F5 on Windows and Linux.
claude "task" starts a session with a first prompt. Inside a session, a line starting with ! runs a shell command and adds its output to the conversation, and @ autocompletes file paths to point Claude at a file. Shift+Tab switches the permission mode.
The screen and the keys
Above the input box you see the version, the current model and your folder. You type your request in the box, in any language. A line under the box shows short hints.
Keys you need
- 1Enter sends your message.
- 2Ctrl+J starts a new line without sending. Shift+Enter does the same in most modern terminals.
- 3Esc stops Claude while it is working. Then you can tell it what to do differently.
- 4The up arrow brings back your earlier messages.
- 5Typing / shows the list of commands. /help shows help, /exit leaves Claude Code.
When Claude asks for permission
Depending on the permission mode, Claude asks before it runs a command or edits a file. In recent versions sessions usually start in auto mode, where a second model checks each action, so you may see fewer questions. Modes have their own lesson later.
Answering a permission question
- 1Read what Claude wants to do. The command or the file is shown in the question.
- 2Move between the answers with the up and down arrow keys, then press Enter.
- 3"Yes" allows this one action.
- 4"Yes, and don't ask again" allows the same kind of action without asking again. For a command it is saved for this project; for file edits it lasts until the session ends.
- 5"No" refuses. Then type what Claude should do instead. Esc cancels the question.
An imitation of a Claude Code session in your project folder. Type each request and press Enter.
1Ask for a page: type make a one-page hello web page in this folder
Leave and come back
Ways back into your work
- 1/exit (or Ctrl+D twice on an empty line) leaves Claude Code. You are back in the normal terminal.
- 2claude --continue (short: claude -c) opens the most recent conversation in the current folder.
- 3claude --resume (short: claude -r) shows a list of earlier conversations to choose from.
- 4Closing the window is also fine. Your files stay in the folder.
/powerup
Type this inside Claude Code. It opens short interactive lessons with animated demos of Claude Code features.
Claude has started doing something you did not intend. What do you press?
What does "Yes, and don't ask again" mean in a permission question?
Facts checked against the official Claude Code docs October 24, 2026 · source
Author
Evgenii Arsentev
PhD · Chief Executive Officer, digital health