NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 2 · Verify your environment and boundariesLesson 1 of 2
Video lesson

L03 · Set up and verify the actual environment

IntermediateVideo lesson
6 min readIntermediate
Downloads & resources
Download this lesson's materials, ready to use.

Skill packs and prompts are provided in English so they work best with the AI tools. Use them as-is.

Set Up and Verify the Actual Environment

Learning time: about 28.9–50.2 active minutes. Choose ONE presentation: the text (about 5.2 minutes, estimated) OR the lesson video (3:55, measured). Then 25–45 minutes of practice and checking (estimated). Do not count both presentations. Setup delays and optional extra study are separate; learner timing has not yet been piloted.

Example prompt

Where you are: Module 2, lesson 3. You have a bounded project brief. Now make sure each assistant can reach the right project before asking either to change it.

What you will do

Open Claude Code and Codex against your practice folder, identify the actual environment and record one successful read-only check in each. You do not need to write software to do this. You do need to distinguish a conversation about a folder from access to that folder.

Teaching

There are three separate things on your screen: the application, its conversation and the files it can reach. Claude in an ordinary browser conversation is not automatically Claude Code in your local project. Codex can also run in different surfaces. This course's main route uses local Claude Code in Terminal and Codex with access to the same local project. Keep the surface names in your setup record.

A Terminal is a place to enter commands. A project folder is a location on your computer. A command may run in whichever folder Terminal currently points to. That is why we check the location before starting an assistant. Do not paste a command that still contains an example path.

If the tools are already installed, use these read-only checks:

sh
claude --version
codex --version

If a command is unavailable, stop that setup branch and use the current official installation page in Sources. Do not install a similarly named package from an advertisement or guessed link. The instructor's local preparation checked Claude Code 2.1.319 and Codex 0.166.0-alpha.5.1 through command-line help/version checks, and a read-only Codex session listed the working folder and read the brief. That does not certify your installation, login or a live model call. Record your actual versions instead of trying to match those numbers.

Open Terminal at your practice project. On macOS, pwd prints the current directory. Once you have confirmed it is the intended practice folder, claude starts Claude Code. In a separate Terminal at that same folder, codex starts Codex CLI. If using the Codex desktop surface, choose the project folder there and record that surface instead. Sign in using the application's offered account flow. Keep passwords, verification codes and tokens out of your chat and course evidence.

Do not run installation commands blindly when setup fails. A missing command, failed sign-in and inaccessible folder are different problems. Ask the assistant to identify the exact error without changing settings. An organization-managed account may require its administrator; a second subscription is not automatically the answer.

Worked example

Noura opens Claude Code in her Downloads folder. It says it cannot find the workshop brief. She could upload a copy, but that would leave two competing project versions. Instead, she stops, opens the correct practice folder and repeats the read-only check. Both assistants now name the same brief and can state its objective. No editing was needed.

Her record says: “Claude Code terminal: read confirmed; Codex CLI: read confirmed · intended brief file; no writes requested.” It does not say “fully connected” because no other tool has been tested.

Do it yourself

Use the setup section of learner/templates/PROJECT-RECORD.md, or a paper copy. Record operating system, application/surface, actual version where visible, project path, account route without personal secrets, permission mode and result.

Send this complete prompt separately to each assistant:

Example prompt

We are preparing a local Workshop Launch Kit for a fictional training coordinator. This is an access check only. Do not edit, install, send, publish or run paid tools. Identify the project directory you can actually access. Find learner/project-starter/PROJECT-BRIEF.md in the supplied course package (or the copied brief in our practice project), state its filename and summarize its stated deliverable and exclusions. If it is missing or unreadable, report that limitation without inventing its contents. Report what you directly inspected and what remains untested.

Compare the answers with the actual brief. A plausible summary is insufficient if the named file does not exist. Save the results without account identifiers or credentials.

If you cannot use Terminal, an instructor may support setup and let you complete this exercise through supported desktop project access. You must still show both tools accessing the intended project and record which route you used. Reading screenshots alone is preparation, not a pass for live access. Mark inaccessible components pending and continue the supplied-file exercises while access is resolved.

Feedback and retry

Pause here before reading.

Your check succeeds when both tools identify the intended location and an actual supplied file, accurately describe it and make no unauthorized changes. If one responds from memory, ask it to inspect the named file directly. If it cannot, retain “access not verified.”

Retry with a harmless existing README in the same folder. Ask each tool to name one heading exactly and explain its purpose. Confirm the heading yourself. Do not repair access by granting unrestricted computer access.

Check your understanding

Choose an answer and write one sentence explaining why before you read the answers.

  1. One assistant accurately describes your brief but says it cannot open local files. Has the local setup passed?
    • A. Yes: it described the brief correctly.
    • B. Yes, if the other assistant can open the files.
    • C. No: the description may come from chat context; the evidence needed is a successful inspection of the intended local project.

Answers

  1. C. No. The description may come from chat context. The required evidence is successful inspection of the intended local project. Record the limitation, not a false pass.

Summary

Keep the environment record. It prevents later confusion about which application, folder or account produced a result. Your next lesson sets the boundaries around what those tools may do.

Sources

  • Claude Code Quickstart, checked 8 November 2026.
  • Codex CLI, checked 8 November 2026.
  • The setup record and practice scenario are original course materials; commands above were checked against documentation, not executed for every learner environment.