Topic 2 · Meeting 2 · setup together + shared demonstration
Set up, then tell the agent to save your progress.
Start here even if Git, GitHub, and the agent are new to you. Work on setup for 25 minutes, then help direct one instructor demonstration for 17 minutes.
Today’s result: one reviewed study-guide file, one next-step note, and one new Git checkpoint sent to GitHub on the instructor’s machine. Your own installation may still need help.
- 1. Set up accounts and tools25 minutes · complete what you can
- 2. Direct the shared demonstration17 minutes · save, commit, push, verify
- 3. Explain your evidenceDuring the class closing check
You do not need access to the instructor’s private repository. Students propose the instructions, check the permissions, and inspect the projected result. The instructor operates the account. Use your own notes to record what works on your device and where you need help.
1. Set up together 25 minutes
Follow the steps your device and account support. This is time to attempt setup, not a promise that every installation will finish. After 25 minutes, everyone joins the shared demonstration.
First 8 minutes · accounts
Sign into GitHub and check agent access
- Use your existing GitHub account, or create one and follow email verification. GitHub is separate from the agent account.
- Open the agent setup workshop’s access note before installing. Use the course’s supported account route; an account for a chat website does not by itself prove agent access.
- If verification, access, cost, or a device restriction blocks you, note the stage and ask for help. No purchase is required for this class activity.
Next 12 minutes · tools
Open the agent and check Git separately
A terminal is a window where you type instructions to the computer. Follow the linked workshop’s steps for your operating system, using a new disposable practice folder. Use one approved agent route; do not install several agents for this exercise.
- Follow the agent installation and sign-in steps. A version number shows the program launches; a successful bounded request gives more evidence that the session works.
- In the terminal, enter
git --version. If Git is missing, use the official installation guide with help. Installing an agent does not guarantee Git is installed. - Keep passwords, tokens, and recovery codes out of prompts and projected screens. Stop if you would need to bypass device restrictions.
Last 5 minutes · check what actually works
Try one request, or identify your blocker
If ready, use the synthetic file and read-only prompt on Agent Setup Readiness. If blocked, use its supplied transcript and explain the evidence and boundary.
In your own notes, record: GitHub access; agent working or blocked; Git available or missing; your next setup step. Git identity, authentication for pushing, and your own practice repository may still need a later guided setup. A browser login alone does not configure local Git authentication.
2. Direct one shared demonstration 17 minutes
Use the instructor’s prepared project. Students take three roles: caller proposes the prompt, scope checker checks what is allowed, and evidence checker points to the result. Rotate the speaker at each step.
Instructor starting point: use the prepared project folder with its starter README, working agent, Git identity, and GitHub authentication. Cloning made this working copy before class. If starting from a new folder instead, check that the destination does not exist before approving a clone. If the live environment fails, label any saved example as a demonstration of an earlier run.
Minutes 0–3 · find the project
Confirm where the agent will work
The instructor opens the prepared project in the agent. Ask:
Show the current project folder, its top-level files, and the GitHub repository connected to it. You may use read-only Git checks. Do not edit, commit, or push. Stop if this is not the approved practice project.
Check: the folder and repository are the intended practice locations. The online repository and the local folder are different places.
Minutes 3–7 · save
Give the agent the reviewed text, then inspect the files
Use the guide from the Meeting 1 study-guide exercise, or the short starter below. Paste the reviewed text after this prompt in the agent; do not ask it to invent missing course details.
In this practice project only, save the reviewed text I provide as study-guide.txt. Create next-steps.txt with what is finished, one next task, and the instructor-source URL. Show both files. Do not commit or push yet.
Check: open both actual files. Do they contain the approved guide and a clear next step?
No guide ready? Use this short practice text
This is a starter for the Git demonstration, not a completed one-page assignment. Read it before using it.
Topic 2 practice notes
An agent can use tool observations to decide its next move.
A tool performs an operation and returns a result.
A skill supplies reusable steps, their order, and when to stop.
Finding a problem does not by itself grant permission to edit.
Source: https://monmouthaiteaching.com/learnai/week-02-agent-foundations.html
Next step: improve one explanation and check its source.
Source sections: Screen 4, Screen 6, and Screen 13.
Minutes 7–12 · commit
Review selected changes and approve one checkpoint
Before the agent acts: predict whether this step will put the guide on GitHub.
Show the exact changes you intend to include. Wait for my approval. Then stage only study-guide.txt and next-steps.txt and commit with the message “Add Topic 2 study guide.” Show the local commit. Do not push.
Staging selects the changes for the checkpoint. The instructor reviews and approves; the agent runs Git. Find the commit message and its short ID in the history.
Check: the new checkpoint is local. GitHub does not have this new commit yet. The starter README may already have its own earlier commit.
Minutes 12–17 · push and verify
Check the destination, approve the push, and look online
Show the exact GitHub destination and the commits you intend to send. Wait for my approval. Then push to that practice repository, report success or the actual error, and give me the browser link.
The instructor approves the destination. After the agent reports success, refresh the GitHub page and locate study-guide.txt, next-steps.txt, and the matching commit ID.
Check: the browser shows the files and checkpoint. A final agent message alone is insufficient. If the push fails, say so; a saved example is not a successful live push.
3. Explain one checkpoint
- What does Save change? Where does Commit record the checkpoint? What does Push send?
- What did you do on your own device, and what did you observe on the instructor’s device?
- What is your next setup step, or the next task written in the project note?
Next guided practice: finish access setup, create or open your own approved private project, and do your first individual save/commit/push cycle. The second revision and fresh-copy retrieval come later. Today’s shared route does not require two student checkpoints.
This page does not run an agent, save project files, or submit work. Use the prompts in the agent and follow the existing LMS directions for any submission.