Codex Manual

Common Workflows

Codex works best when the task has a clear goal, scope, constraints, and verification step.

Understand a project:

Do not edit files. Explain the repository structure, main modules, start commands, test commands, and important config files.

Fix a bug:

The issue is: clicking Save does not show a success message. First locate the cause, do not edit yet, then propose a fix and verification plan.

Review code:

Review the current uncommitted changes. Prioritize bugs, regressions, security risks, and missing tests. Do not edit files.

Long task format:

Goal: migrate the old payment callback flow.
Scope: only api/handler/payment* and related tests.
Constraints: do not change database schema or external fields.
Verification: run payment tests and report remaining risk.