# Codex Agent Guidelines

This document supplements `AGENTS.md` with Codex-specific working notes. Always treat `AGENTS.md` as the source of truth and keep this file aligned with future updates.

## Core Expectations

- Obtain explicit approval from the project owner before attempting any code change or file edit.
- Follow every checklist item in `AGENTS.md`, including framework principles, testing strategy, and tooling conventions.
- Keep documentation edits consistent with project tone (PSR-12 code examples, ASCII character set, precise terminology).

## Workflow Notes

- Prefer small, reviewable steps and clearly report what changed, including file paths and line references.
- When a task involves multiple steps, draft a lightweight plan unless the work is trivial.
- Record unanswered questions or ambiguities in the final message so the owner can respond quickly.

## Tooling Reminders

- Use `bash -lc` shell invocations with explicit `workdir` as required by the Codex CLI harness.
- Rely on `rg` for searches; fall back to alternatives only if `rg` is unavailable.
- Do not run container or network commands without explicit permission when sandboxed.

## Documentation Maintenance

- Update this file whenever Codex-specific guidance changes so it remains synchronized with the rest of the ecosystem docs (e.g., keep parity with `docs/claude/` where it makes sense).
- Coordinate with the project owner before introducing new sections or workflows that impact other agents.