Paths/Codex Engineer/Planning with Codex / Scoping the Change
Set the Boundaries of a Change
The smaller the change, the shorter the review and the fewer the regressions. Write the scoping rules your team applies to every agent task.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/codex/scoping.md exists○
- The document states the size limit for one task○
- The document states the boundaries the agent may not cross○
02Walkthrough
1 of 4 revealed- 01
Create the codex directory
The scoping rules apply to every task, so they are written once.
mkdir -p ~/codex - 3 locked · each failed submit reveals one
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list