plugin-creator validator rejects supported .app.json required binding
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Start in codex-rs/skills/src/assets/samples/plugin-creator/scripts/validate_plugin.py and inspect how app binding fields are validated. Run the bundled plugin-creator validator with the reproduction manifest, then update the validator and manifest specification so an optional boolean required field is accepted and the reproduction passes.
Written by the indexing model from the issue text.
Description
Summary
The bundled plugin validator rejects the optional required field in an app binding, even though the Codex runtime accepts and enforces it.
Reproduction
Create a plugin with this app binding:
{
"apps": {
"sample-production": {
"id": "asdk_app_example",
"required": true
}
}
}
Run the bundled plugin-creator validator. It reports that the .app.json app field required is not accepted.
The relevant validator currently appears at:
codex-rs/skills/src/assets/samples/plugin-creator/scripts/validate_plugin.py
Expected behavior
The validator and plugin manifest specification should accept an optional boolean required field on app bindings, matching the runtime behavior.
Why this matters
Private production connectors can use a required app binding to fail closed instead of silently starting with the wrong or missing connector. The current mismatch creates a false validation failure for a runtime-supported safety configuration.
Actual behavior
The validator only permits id and category on the app entry and rejects required.
- Dominant language
- Rust
- Stars
- 127k
- Forks
- 19.9k
- Avg merge
- 1m
- Merged PRs (30d)
- 996
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
bug CLI exec tool-calls
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug extension session
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
CLI documentation sandbox
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
CLI enhancement TUI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug CLI tool-calls windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
openai/codex#49760 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
canonical/opentelemetry-collector-operator#409 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100