Codex Current Maintainer
Use this skill to keep Codex Nomad Surface aligned with current OpenAI Codex behavior while preserving the project's design constraints.
Sources
Check sources in this order:
SPEC.md for product design constraints.AGENTS.md for repository working rules.- Official OpenAI developer docs through the
openaiDeveloperDocs MCP server.
If OpenAI docs are unavailable, say so and avoid speculative broad changes.
Workflow
- Identify the exact maintenance question or drift risk.
- Fetch the relevant current OpenAI docs before changing behavior or docs that
depend on Codex config, Codex App Server RPC, OpenAI APIs, model behavior,
approval behavior, sandbox behavior, or Prompt Form guidance.
- Compare docs against the local implementation and project specification.
- Make the smallest useful change.
- Validate with focused checks.
- Summarize changed files, docs consulted, verification, and remaining uncertainty.
If a behavior is not documented in official OpenAI docs, verify it through local
execution or direct observation when practical, and label the result as observed
behavior rather than documented behavior.
Focus Areas
- Codex App Server WebSocket RPC usage.
- Codex config keys and runtime override behavior.
- Model, reasoning, verbosity, approval, and sandbox controls.
- Prompt Form protocol and embedded form rendering.
- Prompt Form as a response-body protocol, separate from interactive tools such
as
request_user_input.
- Generative UI compatibility with project scope, especially A2UI,
Open-JSON-UI, AG-UI, and whether Streamlit can support relevant patterns.
Guardrails
- Do not hardcode fast-changing Codex model or option lists when discovery is available.
- Prefer session, chat, or turn scoped runtime overrides over writing Codex config files.
- If a docs change implies a large redesign, report the mismatch first instead of rewriting broadly.
- Report before broad changes to RPC contracts, UI protocols, authentication,
authorization, or multi-module runtime behavior.
Source: tanaga9/codex-nomad-surface — distributed by TomeVault.
1---2name: codex-current-maintainer3description: Maintain Codex Nomad Surface against current OpenAI Codex behavior and official documentation. Use when asked to audit, update, or self-maintain this repository for Codex App Server, Codex config, AGENTS.md, Prompt Form, Generative UI, Streamlit compatibility, Skills, Automations, model/runtime controls, or related OpenAI developer documentation changes. Use when this capability is needed.4---56# Codex Current Maintainer78Use this skill to keep Codex Nomad Surface aligned with current OpenAI Codex behavior while preserving the project's design constraints.910## Sources1112Check sources in this order:13141. `SPEC.md` for product design constraints.152. `AGENTS.md` for repository working rules.163. Official OpenAI developer docs through the `openaiDeveloperDocs` MCP server.1718If OpenAI docs are unavailable, say so and avoid speculative broad changes.1920## Workflow21221. Identify the exact maintenance question or drift risk.232. Fetch the relevant current OpenAI docs before changing behavior or docs that24 depend on Codex config, Codex App Server RPC, OpenAI APIs, model behavior,25 approval behavior, sandbox behavior, or Prompt Form guidance.263. Compare docs against the local implementation and project specification.274. Make the smallest useful change.285. Validate with focused checks.296. Summarize changed files, docs consulted, verification, and remaining uncertainty.3031If a behavior is not documented in official OpenAI docs, verify it through local32execution or direct observation when practical, and label the result as observed33behavior rather than documented behavior.3435## Focus Areas3637- Codex App Server WebSocket RPC usage.38- Codex config keys and runtime override behavior.39- Model, reasoning, verbosity, approval, and sandbox controls.40- Prompt Form protocol and embedded form rendering.41- Prompt Form as a response-body protocol, separate from interactive tools such42 as `request_user_input`.43- Generative UI compatibility with project scope, especially A2UI,44 Open-JSON-UI, AG-UI, and whether Streamlit can support relevant patterns.4546## Guardrails4748- Do not hardcode fast-changing Codex model or option lists when discovery is available.49- Prefer session, chat, or turn scoped runtime overrides over writing Codex config files.50- If a docs change implies a large redesign, report the mismatch first instead of rewriting broadly.51- Report before broad changes to RPC contracts, UI protocols, authentication,52 authorization, or multi-module runtime behavior.5354---55> Source: [tanaga9/codex-nomad-surface](https://github.com/tanaga9/codex-nomad-surface) — distributed by [TomeVault](https://tomevault.io).56<!-- tomevault:4.0:skill_md:2026-05-23 -->
tomevault-io