codex - 💡(How to fix) Fix JSON Schema: `permissions` does not allow "<name>" key

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

This produces a diagnostic error (using Tombi LSP):

Code Example

#:schema https://developers.openai.com/codex/config-schema.json

---

[permissions.custom]
extends = ":workspace"

---

In strict mode, `permissions` does not allow "custom" key. Please add `"additionalProperties": true` to the location where it is defined in https://developers.openai.com/codex/config-schema.json, or add `#:tombi schema.strict = false` as a document comment directive at the top of your document, or set `schema.strict = false` in your `tombi.toml`. [table-strict-additional-keys]

---

"PermissionsToml": {
      "additionalProperties": {
        "$ref": "#/definitions/PermissionProfileToml"
      },
    },
    "FilesystemPermissionsToml": {
      "additionalProperties": true,
    },
RAW_BUFFERClick to expand / collapse

What is the type of issue?

Documentation is incorrect

What is the issue?

When I use Codex config.toml schema:

#:schema https://developers.openai.com/codex/config-schema.json

With permissions block:

[permissions.custom]
extends = ":workspace"

This produces a diagnostic error (using Tombi LSP):

In strict mode, `permissions` does not allow "custom" key. Please add `"additionalProperties": true` to the location where it is defined in https://developers.openai.com/codex/config-schema.json, or add `#:tombi schema.strict = false` as a document comment directive at the top of your document, or set `schema.strict = false` in your `tombi.toml`. [table-strict-additional-keys]

As a consequence, LSP features doesn't work for permissions.* (i.e., completion and diagnostics).

Fix Proposal

Update config.schema.json adding additional properties support for permissions:

    "PermissionsToml": {
      "additionalProperties": {
        "$ref": "#/definitions/PermissionProfileToml"
      },
    },
    "FilesystemPermissionsToml": {
      "additionalProperties": true,
    },

Tested these updates locally and they work for my config.toml.

Where did you find it?

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING