Paths/Codex Engineer/Automation & Adoption / In the Pipeline
Bound What Automation May Touch
An unattended agent needs hard limits. Write the configuration that says when it may run, where it may work and who approves it.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/ci/codex-automation.yaml exists○
- The config states the schedule○
- The config lists the allowed paths○
- The config states the approval rule○
02Walkthrough
1 of 4 revealed- 01
Create the ci directory
The automation configuration sits next to the workflow it configures.
mkdir -p ~/ci - 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