Codex + Claude Code: AI Coding Agents Masterclass for Teens
Don't just learn to code — learn to direct the two most powerful AI coding agents on Earth, and build real apps in 24 classes.
Ready to Master Codex & Claude Code for Teens — AI Coding Agents Masterclass (24 Classes)?
Choose your plan and start your journey into the future of technology today.
International Students (Outside India)
Also available in EUR, GBP, CAD, AUD, SGD & AED. Contact us for details.
Program Overview
This is the most complete teen-friendly course on the two AI coding agents every developer is talking about in 2026: OpenAI Codex and Anthropic Claude Code. In 24 carefully sequenced, project-based classes you will install both tools, learn to give them instructions safely, and watch them write, fix, and ship real code with you. You start from zero — no coding experience required — and finish by building and deploying a real app end-to-end with both agents helping you. Every class has live commands, worked examples, a hands-on project, practice, and a checkpoint. You learn the current tools as they exist today: Claude Code v2.1.x running on Anthropic's Opus 4.7 model, and the OpenAI Codex CLI running on GPT-5.3-Codex and GPT-5.5.
What Makes This Program Different
- Two agents, one course — most courses teach one tool; you graduate fluent in BOTH Codex and Claude Code and know when to use which.
- 100% hands-on — you run real commands from Class 2. No watching, all building.
- Built for teens — friendly pace, fun projects (a website, a game, a Discord-style bot), and a portfolio you can show schools and colleges.
- Living Syllabus — the curriculum is updated continuously as OpenAI Codex and Anthropic Claude Code release new features, models, and capabilities. You always learn the latest.
- Safety-first — you learn approval modes, sandboxes, and responsible AI use before you ever let an agent run wild.
- Real outcomes — finish with a deployed app, a GitHub profile with real pull requests, and a recognized certificate.
Your Learning Journey
Career Progression
Detailed Course Curriculum
Explore the complete week-by-week breakdown of what you'll learn in this comprehensive program.
📚 Topics Covered
- What 'agentic coding' means: an AI that can read your files, write code, run commands, and fix its own mistakes — not just autocomplete
- Meet OpenAI Codex: an AI software-engineering agent that lives in your terminal, your editor, the cloud, and ChatGPT
- Meet Anthropic Claude Code: an agentic coding tool that runs in the terminal, VS Code/JetBrains, desktop, web, and mobile
- How an agent loop works: you give a goal → it plans → it edits/runs → it checks → it reports back
- Codex vs Claude Code at a glance: both are excellent; Codex leans into cloud parallel tasks + ChatGPT, Claude Code leans into deep terminal control + subagents
- The 2026 models you'll use: Claude Code on Opus 4.7; Codex on GPT-5.3-Codex and GPT-5.5
- Why learning to DIRECT an agent is now as important as writing code yourself
🚀 Projects
- Make a one-page 'Codex vs Claude Code' comparison sheet in your own words, listing 3 things each is great at
💪 Practice
Watch each tool's homepage demo and write down 5 things you saw an agent do that surprised you.
🎯 Assessment
Explain, in 3 sentences a friend could understand, what an AI coding agent is and how it differs from a chatbot.
📚 Topics Covered
- Install on Windows (PowerShell): irm https://claude.ai/install.ps1 | iex — on Mac/Linux: curl -fsSL https://claude.ai/install.sh | bash
- Sign in with your plan: claude auth login (Claude Pro or Max works great for learners); check with claude auth status
- Start your first session: open a project folder and type claude
- Meet the REPL (the chat prompt) — type a request in plain English and press Enter
- Type / to see the slash-command menu; try /help and /status
- Understand the model: by default you're on Opus 4.7 (or Sonnet on some plans) — see it with /model
- Exit safely and resume later — your session is saved
🚀 Projects
- Install Claude Code, start a session in an empty folder, and ask it to create a hello.html page that says your name
💪 Practice
Ask Claude Code to explain what it just created, then ask it to change the background color.
🎯 Assessment
Share a screenshot of Claude Code running and your hello.html opening in a browser.
📚 Topics Covered
- What the Codex CLI is — an open-source AI coding agent in your terminal
- Install it: npm install -g @openai/codex (needs Node.js 18+). Careful — the plain 'codex' package is something else; always use the @openai/ scope
- Sign in two ways: 'Sign in with ChatGPT' (uses your ChatGPT Plus/Pro plan) OR an API key
- Start it: type codex to open the interactive TUI; run codex doctor to check everything is healthy
- Pick your model and thinking level with /model (low → medium → high → xhigh); defaults to GPT-5.3-Codex / GPT-5.5 in 2026
- Give your first instruction in plain English and watch Codex plan and edit
- Preview the AGENTS.md idea — a file that teaches Codex your project's rules (Class 10)
🚀 Projects
- Install Codex, run codex doctor, then have Codex add a new section to your hello.html from Class 2
💪 Practice
Ask Codex to explain a file line-by-line, then ask it to add helpful comments.
🎯 Assessment
Screenshot a successful Codex session that edited a file, and explain in one line what the approval prompt asked you.
📚 Topics Covered
- Why approval modes matter: you decide how much the agent can do without asking
- Claude Code modes (cycle with Shift+Tab): default (asks each time), acceptEdits (auto-accepts file edits), plan (read-only, proposes first), auto (a classifier auto-approves safe actions)
- Set a mode on launch: claude --permission-mode plan; manage rules with /permissions
- Codex modes: read-only (look but don't touch), workspace-write (the safe default — edit inside your project), danger-full-access (no guardrails)
- Switch Codex modes anytime with /approvals; the scary bypass flag --dangerously-bypass-approvals-and-sandbox (never use casually)
- Reading an approval prompt: what the agent wants to run and why, before you say yes
- Good habit: start in plan/read-only, review, then allow edits
🚀 Projects
- Run the same small task ('add a footer to hello.html') in plan mode first, review the plan, then approve and apply it
💪 Practice
Deliberately deny an action in each tool and read what changes.
🎯 Assessment
List each approval mode for both tools and say in one line when you'd use it.
📚 Topics Covered
- Pick a tiny starter project (a to-do list web page) and open it in your terminal
- Give a clear goal: 'Add a button that clears all completed to-dos'
- Let Claude Code plan it, show you a diff, and apply the change after you approve
- Repeat the same goal with Codex and compare how each one approached it
- Reading a diff: green = added lines, red = removed lines — how to check the change is what you wanted
- Asking for a fix: 'That button is the wrong color, make it red' — iterating with the agent
- Saving your work: ask the agent to run the app so you can see it work
🚀 Projects
- Add two new features to the to-do app — one with Claude Code, one with Codex — and note which felt easier
💪 Practice
Intentionally introduce a bug, then ask the agent to find and fix it.
🎯 Assessment
Submit a short reflection comparing how Claude Code and Codex handled the same feature request.
📚 Topics Covered
- Claude Code essentials: /help, /clear (start fresh), /compact (shrink a long chat), /context (see what the agent remembers), /model
- Codex essentials: /model, /approvals, /review, /status, and the @ picker to mention files
- Why /clear and /compact matter: keeping the agent focused and fast
- Mentioning a file so the agent reads exactly what you mean (@-mentions)
- Checking your usage and limits with /usage (Claude) and /status (Codex)
- Getting unstuck: asking the agent 'what are you doing and why?'
- Keyboard tips that make you faster in each TUI
🚀 Projects
- Create a personal cheat-sheet of your 10 most-used slash commands across both tools
💪 Practice
Run a long conversation, then use /compact (Claude) and start a clean Codex session — notice the difference.
🎯 Assessment
Demonstrate using @-mention to point the agent at a specific file and ask a question about it.
📚 Topics Covered
- Claude Code Plan Mode: enter with /plan — the agent researches and proposes a plan WITHOUT editing
- Why plan first: catches misunderstandings before any code changes
- Goal Mode: /goal — the agent keeps working until a goal you define is actually met
- Codex /plan and /goal — the same idea on the Codex side (Goal mode is on by default in 2026)
- Writing a good goal: clear, checkable, one outcome ('the login form validates email and shows an error')
- Reviewing and editing the agent's plan before you approve it
- When to skip planning (tiny edits) vs always plan (anything touching multiple files)
🚀 Projects
- Use Plan Mode to design a 'dark mode toggle' for a web page, review the plan, then let the agent build it
💪 Practice
Give a vague goal on purpose and watch how planning surfaces the missing details.
🎯 Assessment
Write one strong, checkable goal statement and explain why it's better than a vague one.
📚 Topics Covered
- How agents edit: they read the file, propose precise changes, and show you a diff
- Reading multi-file changes — following a feature across several files
- Accepting, rejecting, or asking for tweaks on each change
- Claude Code /diff to see what changed; reviewing in VS Code with the extension
- Asking the agent to explain a change you don't understand
- Keeping changes small: one feature at a time is easier to review
- Spotting when an agent edited too much and reining it in
🚀 Projects
- Have an agent refactor a messy function and walk you through the diff line-by-line
💪 Practice
Reject a proposed change and ask for a different approach.
🎯 Assessment
Review a diff and correctly identify which lines were added, removed, and why.
📚 Topics Covered
- Letting the agent run your app: 'start the dev server and tell me the URL'
- Running tests through the agent and reading pass/fail output together
- Basic git with the agent: 'commit this with a clear message', 'show me what changed'
- Claude Code's Bash tool and Codex running commands inside the workspace sandbox
- Approving commands safely — reading the command before it runs
- Asking the agent to fix a failing test until it passes
- Good commit hygiene: small, frequent commits with clear messages
🚀 Projects
- Build a tiny feature, have the agent write a test for it, run the test, and commit when it passes
💪 Practice
Break a test on purpose and ask the agent to make it green again.
🎯 Assessment
Show a git history with at least 3 clear, agent-assisted commits.
📚 Topics Covered
- Why memory matters: tell the agent your project rules once, not every time
- Claude Code: run /init to auto-create a CLAUDE.md; it loads automatically each session
- What to put in CLAUDE.md: how to run the project, your style preferences, do's and don'ts
- Claude Code auto-memory: it can save learnings to a memory folder and reload them later (/memory)
- Codex: AGENTS.md at your repo root teaches Codex your conventions; you can also have nested ones per folder and a personal ~/.codex/AGENTS.md
- A 'Review guidelines' section in AGENTS.md so Codex reviews PRs your way
- Keeping memory short and useful (aim under ~200 lines)
🚀 Projects
- Write a CLAUDE.md and an AGENTS.md for your to-do app describing how to run it and your code style
💪 Practice
Add a rule like 'always use 2-space indentation' and watch the agent follow it.
🎯 Assessment
Submit a CLAUDE.md and AGENTS.md and explain one rule in each.
📚 Topics Covered
- Claude Code checkpointing: it saves code state before edits automatically
- Rewind with /rewind (or press Esc twice) — restore code, conversation, or both
- Limitation to know: rewind tracks edits made by the agent's file tools, not files deleted by shell commands
- Resuming: claude --continue (last chat) and claude --resume to pick a past session
- Codex: resume past sessions and search your local conversation history
- Branching a conversation to try a different approach without losing your place
- Building the safety habit: checkpoint, experiment, rewind if needed
🚀 Projects
- Make a risky change, dislike it, and use /rewind to go back cleanly
💪 Practice
Resume yesterday's session and continue where you left off.
🎯 Assessment
Demonstrate a rewind that restores code without losing your earlier conversation.
📚 Topics Covered
- What MCP (Model Context Protocol) is: a standard way to plug tools and data into your agent
- Claude Code: add a server with claude mcp add --transport http <name> <url>; manage with /mcp and claude mcp list
- Real examples: connect a docs server, a database, or a design tool so the agent can use it
- Codex MCP: configure servers under [mcp_servers.<name>] in ~/.codex/config.toml (stdio or HTTP)
- MCP scopes in Claude Code: local, project (shared via the repo), and user
- Safety with MCP: only connect servers you trust; agents warn about untrusted tools
- Seeing the new tools appear and asking the agent to use one
🚀 Projects
- Connect one MCP server to each agent and have the agent use it to fetch real information
💪 Practice
List the new tools an MCP server added and try one.
🎯 Assessment
Explain what MCP does and show one server connected in each tool.
📚 Topics Covered
- Claude Code Skills: reusable mini-instructions the agent can run; manage with /skills
- Create a custom slash command by adding a file in .claude/commands/ (e.g. /deploy)
- How skills load only when needed, keeping things fast
- Codex plugins, profiles, and the plugin marketplace for sharing setups
- Codex profiles: switch settings/models per project with codex --profile <name>
- When to make a skill vs just typing the instruction each time
- Sharing your skills/plugins with classmates
🚀 Projects
- Create a Claude Code custom command (like /newpage that scaffolds an HTML page) and a Codex profile for your project
💪 Practice
Run your custom command twice and tweak it to be more useful.
🎯 Assessment
Submit one working custom command/skill and explain what it automates.
📚 Topics Covered
- What a subagent is: a helper with its own context, tools, and job
- Claude Code built-in subagents: Explore (fast read-only search) and Plan (research before editing)
- Create your own: a Markdown file in .claude/agents/ with name + description + a system prompt
- Give a subagent only the tools it needs (e.g., a 'reviewer' that can only read)
- Manage and generate agents with /agents
- Why subagents keep the main chat clean and focused
- Example: a 'test-writer' subagent that writes tests while you keep building
🚀 Projects
- Create a 'code-reviewer' subagent and have it review your to-do app
💪 Practice
Compare answers from the Explore subagent vs asking the main agent directly.
🎯 Assessment
Submit a working subagent definition and a sample of its output.
📚 Topics Covered
- What hooks are: code that runs automatically at certain moments (events)
- Claude Code events you'll meet: PreToolUse, PostToolUse, SessionStart, UserPromptSubmit, Stop
- Where hooks live: settings JSON (.claude/settings.json) with a matcher + a command
- A simple, safe hook: auto-format code after every edit, or block a dangerous command
- Reading hook results as feedback to the agent
- Turning hooks on/off and viewing them with /hooks
- Automation mindset: let routine steps happen for you, every time
🚀 Projects
- Add a PostToolUse hook that runs a formatter after the agent edits a file
💪 Practice
Write a PreToolUse rule that blocks an obviously dangerous command and test it.
🎯 Assessment
Submit a working hook and explain which event triggers it and why.
📚 Topics Covered
- Claude Code models: Opus 4.7 (most capable), Sonnet (balanced), Haiku (fast/cheap); switch with /model
- Reasoning effort levels: low, medium, high, xhigh — more effort = deeper thinking (set with /effort)
- The 'ultrathink' trick: add it to a prompt for a one-off deeper think
- Codex models: GPT-5.3-Codex and GPT-5.5; pick model + thinking level with /model
- Big context: Opus 4.7 supports up to 1M tokens — great for large projects
- Choosing wisely: fast model for simple edits, top model + high effort for hard problems
- Cost & limits awareness for learners on student-friendly plans
🚀 Projects
- Solve the same tricky bug on a low effort setting and a high effort setting and compare results
💪 Practice
Switch models mid-task and note speed vs quality trade-offs.
🎯 Assessment
Recommend a model + effort level for three different tasks and justify each.
📚 Topics Covered
- Why images help: show the agent a design or a bug instead of describing it
- Drag-and-drop a screenshot into the prompt so the agent can see it
- Codex Appshots (Mac): capture an app window as context for the agent
- Ask the agent to recreate a UI from a picture of a design
- Debugging from a screenshot of an error message
- Combining text + image: 'make my page look like THIS image'
- Limits: current models read images, not audio/video
🚀 Projects
- Give the agent a screenshot of a website you like and have it build a similar layout
💪 Practice
Screenshot a broken page and ask the agent to diagnose it from the image.
🎯 Assessment
Show a before/after where an image guided the agent to the right result.
📚 Topics Covered
- What Codex Cloud is: agents that work on tasks in the background, in their own safe sandboxes
- Get started at chatgpt.com/codex and connect a GitHub account
- Run tasks in parallel: kick off several at once and let them cook
- Each finished task comes back as a pull request you can review
- Setting up a cloud environment: which repo, setup steps, and internet access
- Reviewing the agent's work before merging anything
- When cloud beats local: long jobs, or working on a repo you don't have on your laptop
🚀 Projects
- Delegate two small tasks to Codex Cloud at once and review both resulting pull requests
💪 Practice
Give a cloud task a clear scope and read the PR description it writes.
🎯 Assessment
Show two parallel cloud tasks and explain what each PR changed.
📚 Topics Covered
- Claude Code on the web at claude.ai/code for long-running and parallel tasks
- The desktop app: review diffs visually and run multiple sessions side-by-side
- Background agents: detach a session with /background and check it later
- Remote control & mobile: steer a session from your phone
- Pulling a web/remote session into your terminal to finish locally
- Choosing the right surface for the job
- Keeping all your sessions organized
🚀 Projects
- Start a task on the web, then continue it on the desktop app or in your terminal
💪 Practice
Send one agent to the background and keep working in the foreground.
🎯 Assessment
Demonstrate moving the same task across two surfaces (web ↔ terminal/desktop).
📚 Topics Covered
- Connecting GitHub so agents can open and review pull requests
- Codex code review: comment @codex review on a PR, or turn on automatic reviews for every PR
- Adding focus: @codex review for security issues
- Claude Code: /code-review on your branch, with --comment to post inline comments on GitHub
- Letting an agent fix review findings: @codex fix the issues
- GitHub Actions/CI: agents that review or triage automatically
- Reading a code review like a pro and acting on it
🚀 Projects
- Open a PR, get an AI code review from Codex and from Claude Code, and apply the fixes
💪 Practice
Write a tiny risky change and see what the reviewer flags.
🎯 Assessment
Show a PR with at least one AI review comment that you addressed.
📚 Topics Covered
- Why parallel: split a big job into pieces that run at the same time
- Git worktrees: isolated copies of your repo so agents don't collide (claude -w <name>)
- Claude Code /batch: break a large change into many units, each handled by its own background agent in its own worktree
- Agent teams: multiple coordinating sessions
- Codex Cloud parallelism revisited: many tasks, many PRs
- Keeping parallel work organized and reviewing each piece
- When NOT to parallelize (small, tightly-linked changes)
🚀 Projects
- Use /batch (or several Codex Cloud tasks) to apply the same small improvement across multiple files
💪 Practice
Create a git worktree and run an agent in it without touching your main branch.
🎯 Assessment
Explain a real change you split into parallel pieces and how you reviewed them.
📚 Topics Covered
- Headless mode: run an agent without the chat UI — Claude Code claude -p "task" and Codex codex exec
- Structured output: ask for clean JSON back (Codex --output-schema) to use in your own programs
- The Claude Agent SDK: build your own mini-agent in TypeScript or Python using Claude Code's engine
- The Codex SDK (TypeScript & Python): start a thread, run a prompt, resume it
- A simple automation: a script that asks the agent to do a chore and reports the result
- Piping: cat error.log | claude -p "explain this error"
- Where this leads: your own custom AI tools
🚀 Projects
- Write a tiny script that uses headless mode to summarize what changed in your project today
💪 Practice
Pipe a file into claude -p and read the structured answer.
🎯 Assessment
Submit a small working automation built with claude -p or codex exec.
📚 Topics Covered
- Permission rules: allow / ask / deny specific actions before any tool runs
- Claude Code Bash sandbox (/sandbox): OS-level isolation so commands can't roam your whole computer
- Codex sandboxes: Apple Seatbelt (Mac), bubblewrap (Linux), Windows Sandbox — and the three approval modes
- Protecting secrets: never let an agent read or commit passwords and API keys
- Prompt injection: why you must be careful with untrusted web content and MCP servers
- Reviewing before you run — the golden rule of agent safety
- Being a responsible AI developer: understand the code the agent writes; you're accountable for it
🚀 Projects
- Configure permission rules and a sandbox setting in each tool and test that a blocked action is actually blocked
💪 Practice
Add a deny rule for a dangerous command and confirm the agent respects it.
🎯 Assessment
Write a short 'safe AI coding checklist' you'll follow on every project.
📚 Topics Covered
- Choose your build: a personal website, a simple game, a quiz app, or a chat-style bot
- Plan it with Plan/Goal mode, write your CLAUDE.md and AGENTS.md
- Build with both agents — use each where it shines
- Add a test, get an AI code review, and fix the findings
- Deploy it live (e.g., a free static host) so you have a real URL
- Polish your GitHub: real commits, a clean README, your PRs
- Present your project and earn your Modern Age Coders AI Coding Agents certificate
🚀 Projects
- Ship a complete, deployed app built and reviewed with Codex and Claude Code, with a public URL and a clean GitHub repo
💪 Practice
Demo your app to the class and walk through how the agents helped you build it.
🎯 Assessment
Final capstone: a deployed app + GitHub repo + a short write-up; pass earns the certificate.
Projects You'll Build
Build a professional portfolio with 50+ projects real-world projects.
No project information available
Weekly Learning Structure
No weekly structure information available
Certification & Recognition
No certification information available
Technologies & Skills You'll Master
Comprehensive coverage of the entire modern web development stack.
No skills information available
Support & Resources
No support information available
Career Outcomes & Opportunities
Transform your career with industry-ready skills and job placement support.
Prerequisites
Who Is This Course For?
Career Paths After Completion
Salary Expectations
Course Guarantees
Common Questions About Codex & Claude Code for Teens — AI Coding Agents Masterclass (24 Classes)
Get answers to the most common questions about this comprehensive program
Still have questions? We're here to help!
Contact Us