Paths/Codex Engineer/Working in a Codebase / Orientation
Search the Way a Maintainer Would
Searching by the name of a function finds the call site, not the definition. Write the search strategy that finds the code that decides the behaviour.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/codex/repo/search.md exists○
- The document states the order of the search○
- The document states how to find the callers of a function○
02Walkthrough
1 of 4 revealed- 01
Create the repo directory
The search notes are per repository.
mkdir -p ~/codex/repo - 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