Checkpoints
The repo ships the two endpoints of the workshop as ready-to-run folders, and can rebuild any checkpoint in between on demand. If your own copy gets into a bad state, you don’t have to debug it under time pressure: jump to a known-good copy, bring your .env, and keep going.
| Folder | Code as of the end of |
|---|---|
support-escalation/ | Chapter 0 (the insecure v1; this is your working copy) |
mcp-server/ | Chapters 6 and 7 (the finished, fully secured server) |
Those two are checked into the repo. The in-between checkpoints — Chapters 2, 4, and 5 — aren’t shipped as folders; you generate the one you need from a git tag when you need it. (Chapters 1 and 3 don’t change code: Chapter 1 is console setup and Chapter 3 is your agent’s config, so there’s no separate checkpoint for them.)
Reset your working copy (Chapter 0)
Section titled “Reset your working copy (Chapter 0)”support-escalation/ is both checkpoint 0 and the copy you’ve been editing, so there’s no pristine sibling to jump into. To reset it to its original state:
git checkout -- support-escalationThat restores the tracked files; your .env and node_modules are untracked and survive.
Jump to an in-between checkpoint (Chapters 2, 4, 5)
Section titled “Jump to an in-between checkpoint (Chapters 2, 4, 5)”From the repo root, materialize the checkpoint for the chapter you’re stuck in. It lands in _recovery/ (which git ignores, so it never disturbs your working copy):
scripts/generate-checkpoints.sh 4 # the chapter you're stuck in (or a tag like cp-2)cp support-escalation/.env _recovery/vault-datastore/ # bring your environment values alongcd _recovery/vault-datastorenpm installnpm run devThe script prints the exact next commands for whichever checkpoint you asked for. The server comes up on the same port, so your agent connection carries over.
Jump to the finished server (Chapters 6–7)
Section titled “Jump to the finished server (Chapters 6–7)”Use the mcp-server/ folder directly — it’s the completed server. Copy your .env into it, npm install, and npm run dev.
Grab an instructor if you’d rather get your own code unstuck. That’s often the faster fix, and the bug is usually the lesson.