Subagents I tend to use with OpenAI Codex.
- Agent notes maintainer: maintains
.agents/notes.mdwhen the parent agent decides a repo lesson should be recorded, including duplicate detection, counters, promotion, and stale-note pruning. - iOS/macOS test runner: validation-only runner for Apple-platform repos that chooses relevant build/test commands, keeps noisy logs out of the parent thread, and reports concise results.
Codex custom agents are standalone TOML files. Per the OpenAI Codex subagents docs, each custom agent must define:
namedescriptiondeveloper_instructions
Optional settings such as nickname_candidates, model, model_reasoning_effort, sandbox_mode, mcp_servers, and skills.config can also be included. If omitted, they inherit from the parent Codex session.
Install these as personal Codex agents:
mkdir -p ~/.codex/agents
cp agent-notes-maintainer/agent_notes_maintainer.toml ~/.codex/agents/
cp ios-macos-test-runner/ios-macos-test-runner.toml ~/.codex/agents/Or install one into a specific project:
mkdir -p .codex/agents
cp /path/to/subagents/ios-macos-test-runner/ios-macos-test-runner.toml .codex/agents/Ask Codex to spawn the custom agent by name, for example:
Spawn agent_notes_mantainer to record this repo lesson: <lesson>
Spawn test_runner to validate the current changes and report concise results.
These agents currently include some repo-specific assumptions from my own workflows. Treat them as practical examples and adapt the instructions before using them in unrelated repositories.
MIT