Setup card — read before L03 and finish before L05
Verified documentation date:8 November 2026. Production host:macOS; Claude Code 2.1.319,Codex CLI 0.166.0,Git 2.50.1,GitHub CLI 2.97.0. These are observed versions, not versions every learner must install. Exact Windows and teaching-account rehearsal is pending before enrollment.
1. Separate the products
Claude Code Terminal, Claude web chat, Claude Desktop and Cowork are different surfaces. This course's command demonstrations use Claude Code Terminal and Codex CLI; the Codex app may help with review, but do not assume its worktree behavior is identical. A chat subscription or browser login alone does not prove local access or sufficient allowance.
Use the current official Claude Code quickstart and Codex CLI guide for your operating system. Follow their supported install/sign-in route. Read what an installer changes before accepting. Do not paste an old third-party installer or a permission-bypass flag to make a lesson work. If your organization manages installations, use its support route.
After installation, these read-only checks identify the tools:
claude --version
codex --version
git --version
Record the exact outputs and date in PROJECT-RECORD. Missing command means software/path setup is incomplete, not that your course project is broken. Check the current account/usage screen for availability; no exact subscription price or entitlement is guaranteed here. Do not share credentials in the record.
2. Make a new private project home
In GitHub's website, create a NEW repository in an account where you have authority. Choose Private, name it workshop-launch-practice, and add a README so it has an initial commit. Do not connect deployment automation, public Pages, payment tools or unrelated apps. Confirm the visibility after creation. If that name exists already, choose another new name rather than overwriting it. This is your practice repository, not the course provider's source repository.
On that repository page copy its HTTPS clone URL. In a new parent folder, use the following command with the copied URL substituted for the capitalized text. Do not type the example token unchanged:
git clone "COPIED_PRIVATE_REPOSITORY_HTTPS_URL"
Open the created project folder in Terminal (on Mac, you can type cd then drag the folder into Terminal and press Enter). Verify:
pwd
git status --short --branch
git remote -v
The path must be your new folder; origin must be the new private repository. Do not post remote output if someone has embedded a token in it. If authentication fails, use the official GitHub authentication guide. A browser login does not prove shell access. GitHub Desktop is an optional documented clone route; use its current official instructions and verify the same path/remote. That GUI route was not tested in this production session.
If you are practicing entirely offline, create a new empty folder and run git init -b main there, then create a README and first named-file commit. This rehearses local versioning only. It does not satisfy remote GitHub handoff until you connect and verify a private remote. Never initialize inside an unrelated existing project.
3. Copy only the learner starter
Copy the contents of project-starter into your new workspace, preserving the supplied brief/data. Copy the templates you need, including PROJECT-RECORD and HANDOFF. Keep producer/assessor files outside the workspace. Read staged and unstaged changes before committing:
git status --short
git diff
git diff --cached
If unrelated changes exist, stop and preserve them. For the four known starter files, after inspecting their content:
git add -- PROJECT-BRIEF.md interest.csv budget-inputs.json TEST-CASES.md
git diff --cached --stat
git diff --cached
git commit -m "Add synthetic workshop brief and inputs"
If Git requests an identity, configure an approved name and privacy-preserving email for THIS repository using the official account guidance; do not guess someone else's identity. Do not change organization settings. Make a practice branch before new course work. L05 teaches the next checkpoint, and L12 teaches review/integration. Pushing is a separate action: confirm the private remote and approved scope before a named-branch push.
4. Start each agent in the same confirmed workspace, one writer at a time
Launch claude or codex from the verified folder. Begin with a read-only task naming the brief. Verify the current model/account/permission status without recording secrets. Read the actual prompt before approval. A request to edit a file is different from permission to send, spend or publish. Preserve any failure and use L10's classification.
Only after these checks should the learner perform the L05–L08 tasks. Later worktrees are new separate folders with explicit bases; do not point concurrent writers at this initial folder.
Evidence limits
Version/help commands, a clone of the private curriculum repository, local Git checkpoints/worktrees/conflicts and public Docs MCP protocol calls were tested during production. No new learner repository was created through the website, no Windows installation was executed, and no Claude model action was run because current allowance was not established. The producer must rehearse the final teaching route; your own successful task receipts remain required.
Sources: official Claude/Codex guides above; GitHub create a new repository; GitHub flow. Course-specific folder conventions are ours.