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.

Use Codex for repo work you can prove

Codex can read, edit, run, review, steer, and operate across app, CLI, IDE, web, mobile, and computer-use surfaces. This track teaches the work loop: brief the task, bound the repo, approve by risk, prove the result, and hand off cleanly.

Start with the Codex surfacesLesson 1 takes about 16 minutes
18
Lessons
2-7
Levels
Free
Tier
⌘

What this track assumes

  • A repo you are allowed to inspect and edit
  • A Git branch or worktree where changes are safe
  • One proof command or route check you can run
  • A clear approval boundary for auth, billing, secrets, data, and deploy work
Open Codex docs

5 Modules | 18 Lessons | Build in order

Module 1
3 lessons

Levels 2-3 | 3 lessons

Surfaces and briefs

Start Codex in the right place with a task it can finish.

You choose between app, CLI, IDE, web, and mobile control, then write a bounded task brief and open the correct repo before Codex edits anything.

Proof:You finish with one task brief that names surface, repo, branch, file boundary, proof, and stop rule.
New Codex usersPeople moving from chat to repo workTeams setting a review habit
Start Module 1
Module 2
3 lessons

Levels 3-4 | 3 lessons

Repo guidance and account boundary

Give Codex stable rules without mixing account policy.

You write useful AGENTS.md guidance, place instructions in the right layer, and choose the sign-in path that matches the repo owner and policy.

Proof:You finish with an AGENTS.md draft, a rule-placement audit, and a sign-in decision.
Repo ownersTeam leadsAnyone working across personal and company code
Start Module 2
Module 3
3 lessons

Level 4 | 3 lessons

Sandbox and approvals

Let Codex work, but keep the boundary visible.

You read sandbox mode, classify approval prompts, and decide when network or secrets are allowed. The habit is narrow access plus proof.

Proof:You finish with one approval policy decision and one network and secret access plan.
Anyone approving commandsSecurity-conscious buildersTeams using cloud tasks
Start Module 3
Module 4
4 lessons

Level 5 | 4 lessons

Proof, review, mobile, and computer

Inspect the result before you accept the change.

You build the proof loop, review diffs before commit, use mobile remote control responsibly, and decide when Codex should use computer use or Chrome for GUI work.

Proof:You finish with route or command proof, staged-file decisions, and a GUI path decision.
People shipping UI changesMobile reviewersDesktop app builders
Start Module 4
Module 5
5 lessons

Levels 6-7 | 5 lessons

Extensions, goals, and handoff

Add power only when the task earns it.

You decide when MCP, skills, plugins, subagents, and Goal mode are worth the setup, then package a handoff that preserves branch state and proof.

Proof:You finish with an MCP gap test, a reusable-workflow decision, a subagent split, a /goal text, and a handoff packet.
Advanced Codex usersPeople running longer workTeams moving between local, IDE, and cloud
Start Module 5

The rule this track protects

Let Codex act when

The repo, branch, files, permissions, and proof are explicit enough for Codex to work without guessing.

Pause Codex when

The task crosses into secrets, auth, billing, production data, deploys, broad network access, or product decisions.

Start with one repo task you can review today

Lesson 1 picks the right Codex surface. Lesson 2 turns the work into a task brief. The rest of the track builds the proof and review loop that keeps Codex useful.

Start Codex Fundamentals