AI Global Academy Join the waitlist

Courses / Bonus / Bonus

Bonus course

Bonus: the course with Codex or Qwen Code

The student can follow the whole course with OpenAI's Codex or with Qwen Code instead of Claude Code: the chosen agent is installed and signed in, reads the same project rules, asks before it changes files, and the student knows what to do in it at every point where a lesson relies on a Claude Code feature. The course prompts were written and checked with Claude Code and have not been tested in Codex or Qwen Code; this section says so wherever it matters.

  • 4lessons
  • 3.6 hof lessons
  • 1.7 hhomework
Start courseSee all lessons

Lessons

  1. 9.1

    Codex in your course project

    40 min + 20 home

    Codex works in the course project with the least possible setup and under the student's control.

    What the lesson covers
    Prerequisites
    Lesson 0.2 without the Claude Code install and sign-in (terminal, Git, Node.js, code editor and the four accounts are still needed); lesson 0.4 — the project folder is a Git repository on GitHub; a ChatGPT plan that includes the Codex CLI, or an OpenAI API key with billing.
    Covers
    • What Codex is and which form the bonus uses: the Codex CLI in the terminal; the desktop app and the editor extension as alternatives that share the same setup.
    • Installing the Codex CLI on macOS and Windows, signing in with ChatGPT, and which plans or billing include it.
    • Opening the existing project, the folder trust question, and the Read Only permission setting that makes Codex ask before every edit.
    • Project memory with one source: a short AGENTS.md that points Codex to CLAUDE.md, so both tools read the same rules.
    • First change, reviewing the diff, and letting Codex commit.
    Do along
    Install Codex, sign in, start it in the course project, switch to Read Only, add AGENTS.md, prove in a new session that Codex knows the project rules, then make one small change, review it, and commit and push.
    Done when
    codex --version prints a version, a new Codex session quotes a rule from CLAUDE.md without being told the file name, and the repository on GitHub shows a commit made through Codex that the student approved.
    Homework
    Make a second one-line change with a request the student writes themselves, add one rule of their own to CLAUDE.md and prove in a new session that Codex quotes it, and write a short start-of-session checklist and use it once.

    Open lesson 9.1 →

  2. 9.2

    The section 1 habits in Codex

    50 min + 30 home

    The student can do everything section 1 teaches using Codex, and knows which Claude Code features have no Codex equivalent.

    What the lesson covers
    Prerequisites
    Lesson 9.1 — Codex set up in the course project with AGENTS.md; a Chromium-based browser.
    Covers
    • What does not change: the four-part brief, reading a plan, reviewing a diff, asking for the cause before the fix, Git as the safety net.
    • Sessions and permissions: the Codex command for each Claude Code command used in sections 0 and 1.
    • Project memory in Codex: CLAUDE.md stays the source, why /init is skipped, and how to check what was loaded without /context.
    • Plan first with /plan; checking work with /diff and /review; fixing problems without a rewind command.
    • Extensions: where skills live in Codex, connecting the Playwright browser MCP server, and subagents.
    Do along
    On the practice page, run one full loop in Codex — plan with /plan, change the plan once, approve, review with /diff and /review — then connect the Playwright MCP server and have Codex open the page in a real browser, take a screenshot and describe it.
    Done when
    Codex reports on the page from a real browser session, and the student can name the Codex equivalent of plan mode, Manual mode, /context and /rewind (or say that there is none and what to do instead).
    Homework
    Repeat the plan, build and review loop on a second change for the student's own business, practise undoing an unwanted Codex edit with git restore, and have Codex check the page at phone width through the browser.

    Open lesson 9.2 →

  3. 9.3

    Following sections 2–8 with Codex

    75 min + 25 home

    The student can take any lesson in sections 2–8 and follow it with Codex.

    What the lesson covers
    Prerequisites
    Lesson 9.2; the checkpoint required by the course lesson chosen for the practice (lesson-1.6 for lesson 2.1).
    Covers
    • How to read a course lesson as a Codex user: prompts stay as written, on-screen steps are translated, checks are run more strictly.
    • The translation guide: every lesson in sections 2–8 that relies on a Claude Code feature, and what to do in Codex instead.
    • Three lessons that need more than a swap: 3.2 (the generated AGENTS.md), 4.7 (the security review) and 8.3 (the Claude API is still used inside the product).
    • The approval prompts Codex's sandbox causes: installing packages, running a local server, committing and pushing.
    • Keeping a short log of differences, because the prompts were not tested in Codex.
    Do along
    Run one real course lesson from start to finish with Codex — lesson 2.1 for students working in order, otherwise the next lesson on their path — and note every place where something had to be translated.
    Done when
    The chosen lesson's own "Done when" check passes with work done by Codex, and docs/codex-notes.md lists each difference the student met.
    Homework
    In docs/codex-notes.md, list the lessons still ahead that need a translation and what to do in each, write personal rules for Codex's approval prompts, and mark each recorded difference as one-off or recurring.

    Open lesson 9.3 →

  4. 9.4

    Qwen Code in your course project

    50 min + 25 home

    Qwen Code works in the course project under the student's control, and the student can use lessons 9.2 and 9.3 with Qwen Code.

    What the lesson covers
    Prerequisites
    Lesson 0.2 without the Claude Code install and sign-in; lesson 0.4 — the project folder is a Git repository on GitHub; a paid model provider for Qwen Code: an Alibaba Cloud Coding Plan, or an API key from a supported provider such as OpenRouter. The free Qwen OAuth sign-in was discontinued on 2026-04-15.
    Covers
    • What Qwen Code is: an open-source terminal agent that you connect to a model provider of your choice.
    • Installing it on macOS and Windows, and connecting a provider with /auth.
    • Approval modes: switching from the documented default, Auto, to Default, and saving that in .qwen/settings.json.
    • Project memory: Qwen Code reads AGENTS.md, so the same pointer to CLAUDE.md serves Claude Code, Codex and Qwen Code.
    • The command sheet: the Qwen Code command for each Claude Code feature the course uses, beside the Codex one.
    Do along
    Install Qwen Code, connect a provider, switch to Default and save it in the project, add or reuse AGENTS.md, prove in a new session that Qwen Code knows the project rules, then make one small change, review it with /diff and git diff, and commit and push.
    Done when
    qwen --version prints a version, /approval-mode shows Default, a new Qwen Code session quotes a rule from CLAUDE.md without being told the file name, and GitHub shows the commit made through Qwen Code with .qwen/settings.json.
    Homework
    Run the plan loop with /plan on a change for the student's own business, undo an unwanted edit once with /restore and once with git restore, and connect the Playwright MCP server with qwen mcp add and have Qwen Code describe the page.

    Open lesson 9.4 →