NuGet “CodexSDK” package ID is reserved — can OpenAI delegate/approve a community .NET SDK name?

[JKamsker]

Hi Codex team 👋

I’m the author of a community .NET implementation/wrapper for Codex SDK-style control over the local Codex CLI:

• Repo: https://github.com/JKamsker/JKToolKit.CodexSDK
• NuGet (current): https://www.nuget.org/packages/JKToolKit.CodexSDK

I’d like to publish it under a more discoverable package ID like CodexSDK (or similar), but nuget.org blocks publishing with:

Response status code does not indicate success: 409 (The package ID is reserved …)

From NuGet’s docs, this typically happens when an ID prefix is reserved, and publishing is rejected unless it originates from the owner(s) of that reserved prefix. If the prefix owner delegates a sub-prefix to another owner (or marks it “public”), publishing can be allowed. (Docs mention delegation/public-prefix scenarios.)

Questions:

1. Does OpenAI control the reserved NuGet prefix that’s blocking CodexSDK / Codex*?
2. If yes: would you be willing to delegate the specific sub-prefix needed (e.g. CodexSDK* or another recommended naming pattern) to my NuGet account (), or advise what official naming you prefer?
3. Separately: from a naming/branding standpoint, is it acceptable for a community project to use “CodexSDK” in the package/repo name if it’s clearly labeled Unofficial / not endorsed by OpenAI? If not, what naming convention do you recommend for community SDKs?

I’m happy to:

• add prominent “Unofficial” disclaimers in README/NuGet metadata,
• avoid OpenAI logos/wordmarks,
• rename if you prefer a different convention.

Thanks!