Learn Everything

Paths/Codex Engineer/Prompting Codex Well / Iterating

Challengeadvancedubuntu:24.04Ask AI

Read a Failed Run

A run that failed still produced information. Write the postmortem for the run itself, not just for the code.

Validator

⏱ 0:00

IDLE — checks run live as you type commands; submit when done

01Requirements

live checks
  • File ~/codex/prompts/failed-run.md exists○
  • The document states what to capture from a failed run○
  • The document states how the failure gets turned into a better request○

02Walkthrough

1 of 4 revealed
  1. 01

    Create the prompts directory

    The postmortem template lives with the other prompt material.

    mkdir -p ~/codex/prompts
  2. 3 locked · each failed submit reveals one

03Stuck?

0 of 3 revealed

Take a hint without losing the lab — each one points at the thing to look at, not at the answer.

04AI Tutor

guides, never solves

Tell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?

04Notebook

saved locally in this browser

learner@lab — ubuntu:24.04

↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list

← Previous lab

Iterate a Request Instead of Restarting

Prompting Codex Well

Next lab →

Write the Settings File

Claude Code Essentials