justin/ai-workflow-course
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(labs): update learner working-dir path to ~/ai-workflow-course after repo rename

Browse Source 
The repo was renamed to ai-workflow-course, so the course's working-directory
convention should match. Replace ~/workflow-course (and /home/you/...,
/ABSOLUTE/PATH/TO/...) with ~/ai-workflow-course throughout modules/ and capstone/
(20 files, incl. the MCP config example). Safe replacement — already-correct
ai-workflow-course references are untouched.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TfzV5QvtPDz8LJS3Pu5VLT
This commit is contained in:
Claude (agent)
2026-06-22 18:54:08 -04:00
parent 3c1c94fb1a
commit a7907c1ff8
20 changed files with 52 additions and 52 deletions
Download Patch File Download Diff File Expand all files Collapse all files
modules/07-worktrees-running-agents-in-parallel/README.md
+16 -16
View File
@@ -94,17 +94,17 @@ The branch was never the problem. The single working directory is. You need two
repository, each with its own checked-out branch.** One repo, many checkouts.
```bash
cd ~/workflow-course/tasks-app # your existing repo from Module 2
cd ~/ai-workflow-course/tasks-app # your existing repo from Module 2
git worktree add ../tasks-app-remaining -b feature/remaining
```
That command creates a brand-new folder, `~/workflow-course/tasks-app-remaining`, containing a full
That command creates a brand-new folder, `~/ai-workflow-course/tasks-app-remaining`, containing a full
checkout of your project on a new branch `feature/remaining`. Your original folder is untouched,
still on its own branch. You now have two real directories you can `cd` into, edit, and run
independently:
```
~/workflow-course/
~/ai-workflow-course/
tasks-app/ ← the "main" worktree, on (say) main
tasks-app-remaining/ ← a "linked" worktree, on feature/remaining
```
@@ -150,9 +150,9 @@ git worktree prune # forget worktrees whose folders were
```bash
$ git worktree list
/home/you/workflow-course/tasks-app a1b2c3d [main]
/home/you/workflow-course/tasks-app-remaining d4e5f6a [feature/remaining]
/home/you/workflow-course/tasks-app-wipe 7g8h9i0 [feature/wipe]
/home/you/ai-workflow-course/tasks-app a1b2c3d [main]
/home/you/ai-workflow-course/tasks-app-remaining d4e5f6a [feature/remaining]
/home/you/ai-workflow-course/tasks-app-wipe 7g8h9i0 [feature/wipe]
```
Three folders, one repo, three branches checked out simultaneously. No stashing, no switching, no
@@ -241,7 +241,7 @@ branch edit the usage line. (The `sed … > tmp && mv` is just a portable, copy-
the edit an agent would make.) In your `tasks-app`:
```bash
cd ~/workflow-course/tasks-app
cd ~/ai-workflow-course/tasks-app
# Agent A's branch: add `wipe` to the usage line and commit it.
git switch -c feature/wipe
@@ -301,17 +301,17 @@ git worktree list # should show main + feature/wipe + feature/remaining
This is the part to actually *do simultaneously*, not one then the other.
1. Open `~/workflow-course/tasks-app-wipe` in one editor/AI session. Give it the prompt in
1. Open `~/ai-workflow-course/tasks-app-wipe` in one editor/AI session. Give it the prompt in
`lab/agent-a-prompt.md` — *add a `wipe` command that removes all tasks.*
2. Open `~/workflow-course/tasks-app-remaining` in a **second** editor/AI session. Give it the prompt
2. Open `~/ai-workflow-course/tasks-app-remaining` in a **second** editor/AI session. Give it the prompt
in `lab/agent-b-prompt.md` — *add a `remaining` command that prints the number of pending tasks.*
3. Let both work at the same time. While they run, prove the isolation from a third terminal — but
use commands that **already exist**. (`wipe` and `remaining` don't yet; the agents are still
writing them.) Give each worktree its own task and list it:
```bash
cd ~/workflow-course/tasks-app-wipe && python cli.py add "from worktree A" && python cli.py list
cd ~/workflow-course/tasks-app-remaining && python cli.py add "from worktree B" && python cli.py list
cd ~/ai-workflow-course/tasks-app-wipe && python cli.py add "from worktree A" && python cli.py list
cd ~/ai-workflow-course/tasks-app-remaining && python cli.py add "from worktree B" && python cli.py list
```
Each `list` shows only its own task — worktree A never sees "from worktree B" and vice versa. Each
@@ -322,8 +322,8 @@ This is the part to actually *do simultaneously*, not one then the other.
4. In each worktree, commit the agent's work on its own branch:
```bash
cd ~/workflow-course/tasks-app-wipe && git add . && git commit -m "Add wipe command"
cd ~/workflow-course/tasks-app-remaining && git add . && git commit -m "Add remaining command"
cd ~/ai-workflow-course/tasks-app-wipe && git add . && git commit -m "Add wipe command"
cd ~/ai-workflow-course/tasks-app-remaining && git add . && git commit -m "Add remaining command"
```
Two agents, two commits, two branches — neither ever saw the other's files.
@@ -331,8 +331,8 @@ This is the part to actually *do simultaneously*, not one then the other.
5. *Now* the new commands exist — run each in its own worktree to watch it work:
```bash
cd ~/workflow-course/tasks-app-wipe && python cli.py wipe # agent A's new command
cd ~/workflow-course/tasks-app-remaining && python cli.py remaining # agent B's new command
cd ~/ai-workflow-course/tasks-app-wipe && python cli.py wipe # agent A's new command
cd ~/ai-workflow-course/tasks-app-remaining && python cli.py remaining # agent B's new command
```
`remaining` counts a single pending task — the one you added to worktree B in step 3 — because B's
@@ -343,7 +343,7 @@ This is the part to actually *do simultaneously*, not one then the other.
Bring both features home to `main` in your original worktree:
```bash
cd ~/workflow-course/tasks-app
cd ~/ai-workflow-course/tasks-app
git switch main
git merge feature/wipe
git merge feature/remaining