Codex Subagent Configuration Builder
Prepare a focused custom agent TOML file, capability reductions and a handoff brief. Review and download locally.
Define the bounded task
Review your files
Suggested project path:
How to use the result
- Choose a narrow question and allowed scope. Keep credentials and unrelated private files outside it.
- Build the file, read the instructions and review capability reductions. Model settings are omitted so the parent configuration is inherited.
- Download the reviewed file and compare it with the schema supported by your installed Codex release. The current official custom-agent documentation uses one standalone TOML per agent.
- Place a reviewed file under the suggested project directory only when you choose to use it. This site does not install files, edit your configuration or start agents.
- Choose appropriate parent permissions and supply the handoff brief. Inspect the returned evidence before further action.
Permissions and compatibility
A custom agent inherits the parent permissions, provider and MCP configuration. A “do not edit” instruction does not create a read-only sandbox. Supported capability keys can reduce available features; they do not expand parent access. This generator omits sandbox, approval, provider and MCP overrides.
The form validates its name and required fields and emits escaped TOML strings. Generated examples are syntax-checked; no live agent is started by this tool. User edits, an older client, managed restrictions or unavailable features can still require changes. Read the current configuration reference. Documentation checked October 15, 2026.
A practical example
For a small bug fix, ask the reviewer to inspect the supplied patch and relevant callers, then return concrete findings with file references. Keep implementation in a separate decision. Disable shell execution if static reading is sufficient; if tests are required, decide the parent permissions and necessary capabilities deliberately before using the file.
Start with one useful specialist rather than a large team of overlapping roles. Independent tasks can benefit from delegation, while agents editing the same files need coordination. The builder organizes instructions; it cannot establish that an agent will always follow them.
Related preparation
Frequently asked questions
Does this install or start an agent?
No. It creates editable text and a local download. You decide whether and where to use the reviewed file.
Is this a separate sandbox?
No. Parent permissions still apply. Written instructions do not establish technical isolation.
Does it change the model?
No. Model and reasoning fields are omitted to inherit the parent configuration.
Made by AI Craft Pad
Original implementation, version 1.0. Free, no account or API key required. About the publisher · Contact or report an issue.