What Your Child Needs to Start Coding with Claude (A Setup Checklist)

What Does a Child Actually Need to Start Coding with Claude?

To start coding with Claude, a child needs surprisingly little hardware but a great deal of the right structure. A modern laptop, a parent-supervised Anthropic account, a properly configured CLAUDE.md guardrails file, and a guided learning environment are the core requirements. The technical bar is low; the pedagogical bar is where most families stumble without expert help.

Picture this: it's a Saturday morning, and a parent sits down with their kid to "just try out that AI coding thing" they read about online. Forty minutes later, the child has copy-pasted three blocks of code they don't understand, Claude has generated a working app the child can't explain, and the parent is quietly wondering whether any real learning just happened. The setup worked. The learning didn't.

That gap, between having access to Claude and actually learning to direct it like a professional developer, is exactly what this checklist is designed to close. Whether your family is exploring this independently or considering a structured program like workshops/claude-code-for-kids" target="_blank">the Claude Code Camp for Teens & Kids, this guide walks through every prerequisite, tool, and safety configuration your young learner needs before writing their first prompt.

Why the Setup Phase Matters More Than Most Parents Expect

The setup phase for Claude-based coding isn't just a technical formality, it's where the safety, learning quality, and long-term skill development are either locked in or left to chance. A misconfigured environment produces a child who learns to copy AI output rather than direct it. A well-configured environment, with proper guardrails and parental oversight, produces a child who is genuinely building computational thinking skills.

This distinction matters enormously. The official Claude Code documentation from Anthropic makes clear that Claude Code is a powerful agentic tool designed to operate with significant autonomy inside a developer's workflow. That autonomy is a feature for professional developers and a variable that requires careful management when young learners are involved.

The difference between a child who is directing AI to build versus one who is copying AI output comes down entirely to how the session is structured before anyone types a single prompt. Directing AI to build means the child understands the problem, breaks it into components, writes intentional prompts, evaluates Claude's output critically, and iterates with purpose. Copying AI output means the child pastes whatever Claude produces and moves on. The first develops real, transferable skills. The second develops dependency.

Setup is where you choose which of those two paths your child takes. And it is not a five-minute task.

The Three Failure Modes Families Hit Without Proper Setup

• The "magic box" problem: The child perceives Claude as a magic answer machine rather than a tool they are directing. This produces learned helplessness, not coding skill.
• The safety gap: Without a custom CLAUDE.md file and parental oversight, Claude can produce content, code patterns, or suggestions that are age-inappropriate for young learners, even unintentionally.
• The accountability vacuum: Without recorded sessions or a parent-present structure, there is no way to review what the child actually learned, what Claude produced, or whether the session was productive.

Every item on this checklist is designed to prevent one or more of these failure modes. Work through it in order.

Step 1: Confirm Your Hardware Meets the Minimum Requirements

Claude Code runs in a terminal environment and requires a modern operating system, a stable internet connection, and enough processing power to run Node.js or Python alongside a browser. Most laptops purchased within the last few years will qualify, but it is worth verifying before your first session to avoid frustrating mid-lesson interruptions.

Estimated time: 10-15 minutes

Operating System Requirements

Claude Code officially supports macOS, Linux, and Windows (via WSL2, the Windows Subsystem for Linux). For families on Windows, WSL2 adds one extra setup step, but it is well-documented and manageable. Chromebooks are generally not suitable without advanced developer mode configuration that most families will find impractical.

Check your OS version:

• macOS: Open the Apple menu and select "About This Mac." You need macOS Monterey (12) or later for reliable performance.
• Windows: Open Settings, go to System, then About. You need Windows 10 version 2004 or later to enable WSL2.
• Linux: Any modern Ubuntu (20.04+) or Debian distribution works without additional configuration.

Hardware Minimums

Component	Minimum	Recommended	Notes
RAM	8 GB	16 GB	Claude Code + browser + code editor can tax 8 GB machines
Storage	20 GB free	50 GB free	Node.js, Python, and project files accumulate quickly
Internet	10 Mbps	25+ Mbps	Claude API calls require consistent, low-latency connection
Display	13-inch screen	15-inch or external monitor	Dual-pane coding (terminal + editor) is much easier on larger screens
Processor	Intel Core i5 / Apple M1	Intel Core i7 / Apple M2+	Older i3 chips create noticeable lag during heavier builds

Pro tip: If your family's primary laptop falls below these specs, consider whether a session on a school-issued device or a grandparent's newer machine might be a better starting point while you assess long-term investment. The Claude Code Camp for Teens & Kids can advise on cost-effective hardware options during onboarding.

Common Mistake to Avoid

Do not assume that because a laptop runs the claude.ai website in a browser, it can run Claude Code in the terminal. Claude.ai (the chat interface) and Claude Code (the agentic coding tool) are different products with different resource demands. Verify against the specs above.

Step 2: Install the Core Software Stack

Claude Code requires three foundational software components before your child types their first prompt: Node.js, npm (which installs with Node), and the Claude Code package itself. Each installation takes only a few minutes, but the order matters and skipping steps creates errors that can derail an entire first session.

Estimated time: 20-30 minutes

Install Node.js and npm

Node.js is the JavaScript runtime environment that Claude Code depends on. Navigate to nodejs.org and download the LTS (Long Term Support) version, not the "Current" version. The LTS release is more stable and better suited to a learning environment where you do not want unexpected breaking changes.

During installation:

1. Accept the default installation path (do not customize it unless you have a specific reason).
2. When prompted, check the box that says "Automatically install the necessary tools", this installs additional build tools that prevent common errors later.
3. After installation completes, open your terminal (Terminal on Mac/Linux, Command Prompt or WSL2 terminal on Windows) and type: node --version
4. If Node installed correctly, you will see a version number (something like v20.x.x). If you see an error, restart your computer and try again before proceeding.

Install Claude Code

With Node and npm confirmed, install Claude Code globally with a single terminal command:

npm install -g @anthropic-ai/claude-code

The "-g" flag installs Claude Code globally, meaning it is accessible from any project directory on the machine. This is the correct approach for a learning environment where your child will create multiple projects over time.

After installation, verify it worked:

claude --version

You should see the current Claude Code version number. If you see "command not found," the most common cause is a PATH configuration issue, which the Claude Code documentation covers in its troubleshooting section.

Install a Code Editor

Claude Code operates in the terminal, but your child will also want a visual code editor to read and understand the files Claude creates. Visual Studio Code (VS Code) is the standard recommendation for young learners: it is free, widely supported, and has excellent syntax highlighting for every language your child is likely to encounter. Download it from code.visualstudio.com.

Install these VS Code extensions after setup:

• Prettier (code formatter, keeps output readable)
• ESLint (flags JavaScript errors before running code)
• Python (if your child's projects will use Python)
• Live Server (lets your child preview web projects instantly in a browser)

Step 3: Create and Configure the Parent-Supervised Anthropic Account

There are no child accounts on Claude, all accounts require an adult, and the parent's account should be used for every session, with the parent present. This is a non-negotiable safety requirement, not a workaround. The account you create now is the account that governs every Claude interaction your child has.

Estimated time: 15-20 minutes

Account Creation

1. Navigate to console.anthropic.com and create an account using a parent email address (not the child's email).
2. Verify the email address when the confirmation message arrives.
3. Navigate to the API Keys section and generate a new API key. Name it something specific like "Family Learning Key" so you can identify it easily.
4. Copy the API key immediately and store it in a secure location (a password manager is ideal). Anthropic shows the full key only once.

Set Usage Limits

Before your child uses Claude Code for the first time, configure spending limits in the Anthropic console:

• Navigate to Settings > Limits in the Anthropic console.
• Set a monthly spend limit that matches your family's budget. For casual learning, a modest limit provides ample usage for multiple weekly sessions.
• Enable email notifications when usage reaches 80% of the limit, so you are never caught off-guard.

This step matters not just financially but pedagogically. When children know that prompts have a cost (even a small, abstract one), they tend to think more carefully before submitting them. That deliberation is itself a coding skill.

Configure the API Key in the Terminal

In your terminal, set the API key as an environment variable:

On Mac/Linux, open your shell profile file (~/.zshrc or ~/.bashrc) and add:

export ANTHROPIC_API_KEY="your-key-here"

On Windows (WSL2), the same command goes in your ~/.bashrc file.

After saving the file, run source ~/.zshrc (or the equivalent for your shell) to activate the variable without restarting the terminal.

Warning: Never paste the API key directly into a project file that might be shared, uploaded to GitHub, or sent to anyone. The environment variable approach keeps it secure. If you ever suspect a key has been exposed, return to the Anthropic console and rotate it immediately.

Step 4: Build Your CLAUDE.md Guardrails File

The CLAUDE.md file is the single most important safety and pedagogical tool in the entire Claude Code setup for kids, and most families who set up Claude Code independently skip it entirely. This file sits in your project directory and gives Claude explicit instructions about how to behave in every session, what to explain, what to avoid, what tone to use, and how to handle sensitive or confusing requests.

Estimated time: 30-45 minutes (do this thoughtfully, not quickly)

What CLAUDE.md Does

Claude Code reads the CLAUDE.md file at the start of every session and treats its contents as persistent instructions. For a young learner's environment, this means you can tell Claude to:

• Always explain its code in plain language before presenting it
• Never produce code that connects to external APIs without explicitly noting what data would be shared
• Avoid adult content, violence, or mature themes in any generated stories, games, or app concepts
• Ask clarifying questions before beginning a task, rather than making assumptions
• Flag when a request is beyond the learner's current level and suggest a simpler starting point
• Celebrate progress and frame errors as learning opportunities

A Starter CLAUDE.md Template for Young Learners

Create a file called CLAUDE.md in your project folder and customize the following template:

Learning Environment Rules

This coding session is for a young learner. Please follow these guidelines in every response:

1. Before writing any code, explain what you are about to do in simple, plain language a student can understand.

2. After writing code, explain what each significant section does. Use comments inside the code as well.

3. Keep all project themes appropriate for young learners. Avoid violence, adult content, horror, or mature themes.

4. When the student's request is unclear, ask one clarifying question before proceeding. Do not make assumptions.

5. If the student asks you to simply "do it for them" without engaging, gently prompt them to describe what they want first.

6. When errors occur, explain what went wrong before suggesting the fix. Frame errors as normal and useful parts of coding.

7. Never connect to external services, APIs, or databases without first listing exactly what data would be sent or received.

8. Keep responses concise and scannable. Use numbered steps and bullet points rather than long paragraphs.

This template is a starting point. The families who get the most value from CLAUDE.md spend time customizing it based on their child's specific interests, learning style, and current skill level. If your child is building games, add a note about preferred game themes. If they are visual learners, instruct Claude to include diagrams or pseudocode before actual code. The file is infinitely customizable.

Where to Put the CLAUDE.md File

Place the CLAUDE.md file in the root directory of each project your child works on. If you want global rules that apply across all projects, Claude Code also reads a CLAUDE.md from the parent directory of your project tree. For most families, a single CLAUDE.md in a dedicated "learning" folder that houses all child projects is the cleanest approach.

Pro tip from experienced instructors: Review and update the CLAUDE.md file monthly as your child's skills grow. What protects a complete beginner may feel overly restrictive for a more advanced learner six months in. The file should grow with your child.

Step 5: Set Up Your Session Recording and Review System

Recorded sessions are one of the most underrated tools in a young learner's coding setup, they let parents review what was built, let instructors give feedback on prompting quality, and give children a record of their own progress over time. The Claude Code Camp for Teens & Kids provides families with recordings of every supervised session as a standard feature. If you are setting up independently, you need to build this system yourself.

Estimated time: 15 minutes setup, ongoing maintenance

Terminal Session Recording

On Mac and Linux, the script command records everything that happens in a terminal session to a text file:

script ~/coding-sessions/session-$(date +%Y%m%d).txt

This creates a timestamped text file in a "coding-sessions" folder in your home directory. When the session ends, type exit to stop recording. The file will contain every command typed and every response received, a complete record of the session.

On Windows, tools like Windows Terminal have built-in logging options accessible through the terminal's settings JSON file.

Screen Recording for Visual Projects

For projects with visual output (web apps, games, interactive tools), a screen recording captures what the terminal log cannot: the visual result of the child's work. Both Mac (QuickTime) and Windows (Xbox Game Bar or the built-in Snipping Tool) have free screen recording built in. A simple workflow is to start a screen recording at the beginning of each session and stop it when done.

Store recordings in a labeled folder structure:

• Coding Sessions > [Child's Name] > [Project Name] > Session 01, Session 02...

This folder becomes a portfolio over time, and reviewing it periodically is one of the most motivating things a parent can do with a young learner. Seeing how much more sophisticated Session 10 looks compared to Session 01 is a powerful confidence builder.

The Parent Review Habit

Set aside 10 minutes after each session to review what was built. Ask your child to walk you through it. The questions that matter most are not "did it work?" but:

• What problem were you trying to solve?
• What did you tell Claude to do, and why?
• What did Claude produce that surprised you?
• What would you change if you did this again?

These questions develop metacognitive habits, the ability to think about one's own thinking, that transfer far beyond coding. They are also the questions that separate learners who are directing AI from learners who are copying it.

Step 6: Create Your Child's First Project Sandbox

Before the first real session, set up a dedicated project sandbox: a folder structure that is organized, version-controlled, and safe to experiment in without risk of breaking anything important. This removes a major source of anxiety for young learners and teaches professional development habits from day one.

Estimated time: 20 minutes

Create the Project Folder Structure

In your terminal, navigate to a sensible location (the Desktop or Documents folder works well for most families) and create this structure:

1. Create a parent folder: mkdir claude-learning
2. Navigate into it: cd claude-learning
3. Create your first project folder: mkdir project-01-hello-world
4. Copy your CLAUDE.md file into this project folder
5. Initialize a Git repository: git init

Why Git Matters Even for Beginners

Git is the version control system used by virtually every professional developer in the world. Introducing it from the first session, even in its simplest form, means your child builds the habit of saving progress checkpoints rather than working in a single file that can be accidentally overwritten.

For a young learner, the only Git commands they need in early sessions are:

• git add . (stage all changes)
• git commit -m "what I built today" (save a checkpoint with a description)
• git log (see the history of all checkpoints)

These three commands take about five minutes to learn and pay dividends for a lifetime of coding. They also create a natural "save your work" ritual that prevents the heartbreak of lost progress.

Install Python (Optional but Recommended)

Many beginner projects use Python because its syntax is close to plain English and Claude excels at explaining Python code clearly. If your child's interests lean toward data, game logic, or automation, install Python from python.org (download the latest stable version, not a beta release). After installation, confirm it works with:

python3 --version

If Python is installed, you will see a version number. If not, the most common fix is to add Python to your system PATH, a process the Python documentation covers step-by-step for each operating system.

Step 7: Run Your First Supervised Test Session

The first session should not be an ambitious project, it should be a deliberate test of every component in your setup, run with the parent sitting beside the child from start to finish. Think of it as a dress rehearsal: you are verifying that the hardware, software, account, guardrails, and recording system all work together before your child invests emotional energy in a project they care about.

Estimated time: 45-60 minutes

The Test Session Agenda

1. Start the terminal recording (using the script command from Step 5). Confirm the file is being created.
2. Navigate to the project sandbox created in Step 6.
3. Launch Claude Code by typing claude in the terminal. You should see the Claude Code welcome prompt.
4. Confirm CLAUDE.md is active by asking Claude: "What are your instructions for this session?" Claude should reference the guidelines you set in the CLAUDE.md file. If it does not, verify the file is in the correct directory.
5. Run a simple test prompt: "Please create a Python script that asks the user for their name and then prints a welcome message." Watch how Claude responds, does it explain the code before writing it? Does it follow the CLAUDE.md guidelines? If not, revisit Step 4.
6. Save a Git checkpoint after the first file is created.
7. Stop the recording and review the session file together.

What a Good First Session Response Looks Like

With a properly configured CLAUDE.md, Claude should respond to that test prompt by:

• First explaining in plain language what the script will do
• Then writing the code with inline comments
• Then offering to explain any part of the code in more detail
• Using an encouraging, age-appropriate tone

If Claude's first response is just a block of uncommented code with no explanation, your CLAUDE.md file is either not being read or needs stronger phrasing. Return to Step 4 and verify the file location, then strengthen the language in the instructions (using "You must always..." instead of "Please...") and retest.

The Parent Debrief After Session One

After the test session, ask your child: "What did Claude do that you told it to do?" and "What did Claude do that you did not expect?" These questions establish the mental model of Claude as a tool being directed, not an autonomous producer of results. This mental model is the foundation of genuine coding education, and it should be reinforced in every session from the first one onward.

Is the Claude Code Setup for Kids Something Families Can Manage Alone?

The technical setup is manageable for most tech-comfortable parents, but the pedagogical setup, the CLAUDE.md guardrails, the session structure, the prompting curriculum, is where independent setups most often fall short. The difference between a well-guided Claude Code session and an unstructured one is the difference between learning to code and learning to copy.

This is precisely why structured programs exist. The Claude Code Camp for Teens & Kids provides not just the technical setup guidance but the complete learning scaffold: a sequenced curriculum built around real projects, parent-present sessions with named instructors Isaac Rudansky the benefits of Claude Code without the trial-and-error of building the infrastructure from scratch, the camp handles every item on this checklist before the first lesson begins.

For families who choose the independent route, the checklist above covers the essential technical setup. What it cannot fully replace is the experience of a seasoned instructor who knows exactly when to let a child struggle productively with a prompt and when to intervene.

How Do You Know If Your Child Is Ready to Start?

Readiness for Claude Code is not about prior coding experience, it is about the ability to describe a problem in words and stay curious when the first attempt does not work. These are communication and resilience skills, not technical prerequisites.

Young learners who thrive with Claude Code tend to share a few characteristics:

• They can describe what they want to build before they start building. Even a vague description ("I want a game where you guess a number") is enough. What does not work is "I want something cool" with no further elaboration.
• They are comfortable with iteration. Claude's first output is rarely the final product. Learners who see refinement as part of the process, not a sign of failure, advance much faster than those who expect perfection on the first prompt.
• They can tolerate not understanding everything immediately. Claude Code sessions often surface concepts the child has not encountered before. Curiosity about those concepts, rather than anxiety about them, is the key predictor of progress.
• They have a parent who is engaged, not just present. The most successful young learners in any structured program have a parent who asks questions about the work, not just watches it happen.

There is no minimum technical knowledge required. Children who have never written a line of code can start with Claude Code if the setup is right and the guidance is strong. The checklist above is designed to make that possible.

The research backing this approach is compelling. The Anthropic Claude Code documentation describes a tool built for professional-grade agentic development, and the skills required to use it well (decomposing problems, writing precise specifications, evaluating outputs critically) map directly onto the computational thinking frameworks that educators and researchers have identified as foundational for the future workforce. Learning to direct AI purposefully is not a shortcut around coding skills. Done right, it is a direct path into them.

If your family is ready to move beyond the checklist and into a structured, expert-led experience, the Claude Code Camp for Teens & Kids is designed for exactly this moment. Every session is parent-supervised, every guardrail is pre-configured, and the curriculum is built around real projects that kids and teens actually want to build.

Frequently Asked Questions About Setting Up Claude Code for Kids

Does my child need to know how to code before starting with Claude Code?

No prior coding experience is required. Claude Code is designed to be accessible to complete beginners when the session is properly structured. The key prerequisite is not coding knowledge but the ability to describe a problem clearly, a communication skill, not a technical one. A well-configured CLAUDE.md file and a parent-present environment are more important than any prior experience.

Is Claude Code safe for young learners to use?

Claude Code is safe for young learners when used in a parent-supervised environment with a properly configured CLAUDE.md guardrails file. Without those guardrails, Claude Code is a professional tool designed for adult developers and can produce content or suggest patterns that are not appropriate for a learning environment. The safety is not in the tool itself, it is in the setup. Every item in this checklist contributes to a safe environment.

What does the CLAUDE.md file actually do, and is it really necessary?

The CLAUDE.md file is a persistent instruction document that Claude Code reads at the start of every session. It tells Claude how to behave in your specific environment, what tone to use, what topics to avoid, how to explain code, and how to handle unclear requests. For a young learner's setup, it is not just useful; it is essential. Without it, Claude defaults to professional developer behavior that assumes an adult audience with significant technical knowledge.

How much does it cost to run Claude Code sessions at home?

Claude Code operates on a pay-per-use API model through Anthropic's console. The cost depends on how many tokens (roughly, words) are sent and received in each session. For a typical learning session with moderate prompting, the cost is modest. Setting a monthly spend limit in the Anthropic console, as described in Step 3 of this guide, ensures costs never exceed your budget. The Anthropic console shows real-time usage so you always know where you stand.

Can my child use Claude Code on a tablet or phone?

No. Claude Code is a terminal-based tool that requires a full operating system with Node.js installed. It does not run on iOS or Android tablets or phones. A laptop or desktop computer is required. Chromebooks are also generally incompatible without advanced developer mode configuration.

What should my child build in their first sessions?

First sessions work best with small, completable projects: a script that tells a joke, a simple quiz game, a tool that converts temperatures. The goal is not to build something impressive but to complete the full cycle, describe the problem, write a prompt, review Claude's output, run the code, see it work. Completable projects build momentum. Ambitious projects that stall halfway through build frustration.

How is this different from just letting my child use the Claude.ai chat interface?

Claude.ai is a conversational chat interface. Claude Code is an agentic development environment that can read and write files, execute commands, and work across a codebase. The skills developed in Claude Code, writing precise specifications, managing a project directory, using version control, evaluating code output, are professional development skills. Claude.ai chat is useful for many things, but it does not develop the same transferable technical competencies.

How long should each Claude Code session be for kids and teens?

Focused sessions of 45 to 90 minutes tend to produce the best outcomes for young learners. Shorter sessions do not allow enough time to get into a meaningful coding flow. Longer sessions risk fatigue and the cognitive shortcuts that come with it, which often means the child starts asking Claude to "just do it" rather than engaging with the problem. The Claude Code Camp for Teens & Kids structures sessions within this range for exactly this reason.

What if my child gets frustrated when Claude's code does not work?

This is one of the most valuable learning moments in any coding session, and the CLAUDE.md file can be configured to help Claude handle it well. Instruct Claude to always explain what went wrong before suggesting a fix, and to frame errors as normal and informative. As a parent, resist the urge to immediately solve the problem. Ask your child what they think went wrong first. The debugging process, reading an error message, forming a hypothesis, testing it, is itself a core coding skill.

Do I need to be present for every session?

Yes, especially in early sessions. Parent presence is not just a safety measure, it is a pedagogical one. Children who know a parent is watching and interested tend to engage more thoughtfully with the work. They explain their thinking out loud, which deepens understanding. They are less likely to take shortcuts. As your child's skills develop and you are confident the setup is working well, you can transition to a nearby presence rather than direct side-by-side supervision, but never to fully unsupervised sessions.

Can siblings use the same setup?

Yes, but create separate project folders and separate CLAUDE.md files for each child, customized to their individual level and interests. Sharing a single project folder creates confusion and makes it harder to review each child's individual progress. The parent Anthropic account can serve the whole family, but each learner should have their own structured workspace.

Is there a difference between what girls and boys find engaging in Claude Code projects?

Project interest varies far more by individual personality than by any demographic category. Some learners gravitate toward game-building, others toward storytelling tools, data visualizations, or automation scripts. The best first-session strategy is to ask the child what problem they wish they could solve with a computer, and start there. Claude Code is flexible enough to serve almost any starting interest.

Key Takeaways

• Hardware first: Verify your laptop meets the minimum specs (8 GB RAM, 20 GB free storage, stable internet) before investing time in software setup. Chromebooks and tablets do not support Claude Code.
• Install in order: Node.js, then npm (which comes with Node), then Claude Code via npm. Verify each step with a version check before proceeding to the next.
• Use a parent account, always: There are no child accounts on Claude. The parent's Anthropic account, with usage limits configured, is the correct and safe setup for every young learner.
• CLAUDE.md is not optional: The guardrails file is the most important safety and pedagogical tool in the entire setup. Without it, Claude defaults to professional developer behavior that is not calibrated for young learners.
• Record every session: Terminal logs and screen recordings create a portfolio, enable parent review, and allow instructor feedback. Families in the Claude Code Camp for Teens & Kids receive recordings of every session automatically.
• Start small: The first session should be a setup test, not an ambitious project. Confirm every component works together before your child invests in a project they care about.
• The goal is directing, not copying: Every structural choice in this setup, from the CLAUDE.md instructions to the parent debrief questions, is designed to keep your child in the role of problem-solver directing a tool, not a passive recipient of AI output.
• Expert guidance changes outcomes: The technical setup is manageable independently, but the curriculum, prompting pedagogy, and session structure that make Claude Code genuinely educational are where expert instruction makes the decisive difference. The Claude Code Camp for Teens & Kids, led by instructors Isaac Rudansky